q13d0310h3_55b375c5d22e_6bd95d438927
Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.
What this fingerprint encodes
q13d0310h3
handshake shape, human-readable
55b375c5d22e
truncated hash of the cipher list
6bd95d438927
truncated hash of extensions + signature algorithms
- Transport
- QUIC
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 3
- Extensions offered
- 10
- 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 10
-
quic_transport_parameters -
server_name -
psk_key_exchange_modes -
supported_groups -
supported_versions -
key_share -
application_layer_protocol_negotiation -
status_request -
signature_algorithms -
encrypted_client_hello
Named groups 4
-
SecP256r1MLKEM768 -
x25519 -
secp256r1 -
secp384r1
Raw JA3 string
771,4866-4865-4867,57-0-45-10-43-51-16-5-13-65037,4588-29-23-24,
Seen in live traffic
- Connections
- 10020
- First seen
- 2026-10-06 19:58 UTC
- Last seen
- 2026-11-12 01:23 UTC
- Transport
- QUIC
- JA3 hashes absorbed
- 8804
The same client, 8804 different JA3s
This one JA4 covers 8804 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 8804 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
2bf08c928ba140c251828486fb40ea7c29edeb21b951f621170899a6747d7d1100285cbb9a2509e13e0ac3f0303dcec402c3bc074a0c6457147e2286e497995e4cba4ddd0401ec141f0c3292dd16172a59cca9cd8f5c530d4cc46b34cd9b4faa67be3e931ee02137a67d38cfb8ddceb213d7d4c8993f393def7d1056d51e364e8f55c36ad75d633ecaa55dc8320baa6ae19ec072c7993219dcccec4ccb31fc73070893cc3a04d1f94d7c06f4cb63d66e6645aabd31c66d5fddca2ee9b361d48c- … and 8792 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.