t13d0113h2_58070c528ac8_b415277f4867
Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.
What this fingerprint encodes
JA4_a
t13d0113h2
handshake shape, human-readable
JA4_b
58070c528ac8
truncated hash of the cipher list
JA4_c
b415277f4867
truncated hash of extensions + signature algorithms
- Transport
- TCP
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 1
- Extensions offered
- 13
- ALPN
- h2
The hello it was computed from
Recovered because the proxy now stores the pre-hash JA3 string alongside the digest. Every number below came out of this client's ClientHello; anything we cannot name in the IANA registry is shown as its raw value rather than guessed at.
- Version
- TLS 1.2
Cipher suites 1
-
TLS_CHACHA20_POLY1305_SHA256
Extensions 13
-
renegotiation_info -
signed_certificate_timestamp -
status_request -
server_name -
extended_master_secret -
session_ticket -
signature_algorithms -
ec_point_formats -
supported_groups -
application_layer_protocol_negotiation -
supported_versions -
key_share -
psk_key_exchange_modes
Named groups 6
-
SecP256r1MLKEM768 -
x25519 -
secp256r1 -
x448 -
secp521r1 -
secp384r1
Point formats 3
-
uncompressed -
ansiX962_compressed_prime -
ansiX962_compressed_char2
Raw JA3 string
771,4867,65281-18-5-0-23-35-13-11-10-16-43-51-45,4588-29-23-30-25-24,0-1-2Seen in live traffic
- Connections
- 2
- First seen
- 2026-10-21 01:14 UTC
- Last seen
- 2026-10-21 01:14 UTC
- Transport
- TCP
This entry is an observation, not a policy decision. It is here because the edge saw it, not because anyone reviewed it, and it blocks nothing on its own. Only the curated tier drives classification and banning.