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 -
status_request -
supported_groups -
application_layer_protocol_negotiation -
supported_versions -
psk_key_exchange_modes -
key_share -
signature_algorithms -
encrypted_client_hello
Named groups 4
-
SecP256r1MLKEM768 -
x25519 -
secp256r1 -
secp384r1
Raw JA3 string
771,4866-4865-4867,57-0-5-10-16-43-45-51-13-65037,4588-29-23-24,
Seen in live traffic
- Connections
- 7
- First seen
- 2026-10-15 01:51 UTC
- Last seen
- 2026-10-15 03:52 UTC
- Transport
- QUIC
- JA3 hashes absorbed
- 7
The same client, 7 different JA3s
This one JA4 covers 7 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 7 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
d0c10c90e5cbad4ef62677f53683f9c681dc2752c817a0d672d1ab4c42e14563fb7dda63b363c25d3a829d6e7e847bd3e500300c0744849c8e0c5d0adbb4327646cfd85d8338fcf6b5b2303de66e7fc59cd18b56535cfcb2c3a8c61bebe2a7a6dfde5952199f3b8f8b2f51f3f44a3541
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.