q13d0311h3_55b375c5d22e_512ac2397e4d
Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.
What this fingerprint encodes
q13d0311h3
handshake shape, human-readable
55b375c5d22e
truncated hash of the cipher list
512ac2397e4d
truncated hash of extensions + signature algorithms
- Transport
- QUIC
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 3
- Extensions offered
- 11
- ALPN
- h3
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 3
-
TLS_AES_256_GCM_SHA384 -
TLS_AES_128_GCM_SHA256 -
TLS_CHACHA20_POLY1305_SHA256
Extensions 11
-
supported_versions -
psk_key_exchange_modes -
key_share -
status_request -
application_layer_protocol_negotiation -
supported_groups -
quic_transport_parameters -
signature_algorithms -
extended_master_secret -
server_name -
ec_point_formats
Named groups 4
-
SecP256r1MLKEM768 -
x25519 -
secp256r1 -
secp384r1
Point formats 1
-
uncompressed
Raw JA3 string
771,4866-4865-4867,43-45-51-5-16-10-57-13-23-0-11,4588-29-23-24,0
Seen in live traffic
- Connections
- 4
- First seen
- 2026-09-14 18:12 UTC
- Last seen
- 2026-09-14 18:12 UTC
- Transport
- QUIC
- JA3 hashes absorbed
- 4
The same client, 4 different JA3s
This one JA4 covers 4 distinct JA3 hashes. A JA3 hashes the cipher and extension lists in the order they arrived, so a client that shuffles them — which Chrome and its derivatives do on purpose — produces a new JA3 almost every connection and fragments into what looks like 4 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
02cc4cf10938f7cbd351ca53ed7feb08502bf5b39d2cf14bf0b3fa8a9d23d5a241cef7a8978b8e28193858ca3bd9ca11681b907e6c9604225330e665c113666a
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.