q13d0311h3_55b375c5d22e_35002cbdedc5
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
35002cbdedc5
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 -
status_request -
application_layer_protocol_negotiation -
signature_algorithms -
extended_master_secret -
server_name -
psk_key_exchange_modes -
supported_groups -
key_share -
quic_transport_parameters -
ec_point_formats
Named groups 3
-
x25519 -
secp256r1 -
secp384r1
Point formats 1
-
uncompressed
Raw JA3 string
771,4866-4865-4867,43-5-16-13-23-0-45-10-51-57-11,29-23-24,0Seen in live traffic
- Connections
- 5952
- First seen
- 2026-08-23 04:19 UTC
- Last seen
- 2026-10-08 19:06 UTC
- Transport
- QUIC
- JA3 hashes absorbed
- 5609
The same client, 5609 different JA3s
This one JA4 covers 5609 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 5609 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
1bf919c8e7b9b90450520b212c6912782d07bfcb9c8b5d8aca3a9600e781c2b593ee95fe6b9d8c001c72ffb9d949d1ff3a1446c1ae7a746e042c1aef8a32f9db3be722153dc5095756fe8c16d0fa7da958ae2af42be784b11b153012567c7aaac6621e6bc205703968acdf8b0cd125a45068653c3390d5b2f0a392204ad1c66488c2747d9e87e9d232ed3a68044cec8d1d65c0c61ef0b291ccb987fad4ee94bccea24a9ecf25363dcb78e974f8cd0daf41ad7e2b758c22ba5804e2778ba62ca2- … and 5597 more
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.