q13d0311h3_55b375c5d22e_387675cfb458
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
387675cfb458
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
-
status_request -
quic_transport_parameters -
supported_versions -
supported_groups -
extended_master_secret -
key_share -
psk_key_exchange_modes -
server_name -
ec_point_formats -
application_layer_protocol_negotiation -
signature_algorithms
Named groups 3
-
x25519 -
secp256r1 -
secp384r1
Point formats 1
-
uncompressed
Raw JA3 string
771,4866-4865-4867,5-57-43-10-23-51-45-0-11-16-13,29-23-24,0Seen in live traffic
- Connections
- 26
- First seen
- 2026-09-10 21:54 UTC
- Last seen
- 2026-10-15 03:41 UTC
- Transport
- QUIC
- JA3 hashes absorbed
- 24
The same client, 24 different JA3s
This one JA4 covers 24 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 24 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
e14087a696fc2b6201f7fb490d470f0a86caac92d72c255bd037061859fc6fc4d98dc5ff50f04e6aeab12a50cf221421b6fddd33977b15be12e8e4031d7b66389b1dfe1c163af77dd3d068392b2de8a69db4bb14a22ccd56a783cb888c13c998d95d8c8192d0906591aa4257a652e37cebdc1f0147ca491e5d7c58a1d02b2bf8c1cc192073cbd41029d24707b8b362dc54889a633b375e48678f5ca186485291b7f275a4e797febdc9d2a3b8994d9d3781f133e5498d3347a4e7840464816122- … and 12 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.