q13d0310h3_55b375c5d22e_cd85d2d88918
Chrome — inferred from the User-Agent on its requests.
What this fingerprint encodes
q13d0310h3
handshake shape, human-readable
55b375c5d22e
truncated hash of the cipher list
cd85d2d88918
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_128_GCM_SHA256 -
TLS_AES_256_GCM_SHA384 -
TLS_CHACHA20_POLY1305_SHA256
Extensions 10
-
key_share -
supported_versions -
compress_certificate -
signature_algorithms -
server_name -
psk_key_exchange_modes -
supported_groups -
application_settings -
quic_transport_parameters -
application_layer_protocol_negotiation
Named groups 3
-
x25519 -
secp256r1 -
secp384r1
Raw JA3 string
771,4865-4866-4867,51-43-27-13-0-45-10-17513-57-16,29-23-24,
Seen in live traffic
- Connections
- 132
- First seen
- 2026-08-24 14:10 UTC
- Last seen
- 2026-11-11 02:45 UTC
- Transport
- QUIC
- JA3 hashes absorbed
- 77
The same client, 77 different JA3s
This one JA4 covers 77 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 77 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
1b362e62bc7ab84a658a49961ab529b30e2261aa81aadb49dd3b2f89f59b9dd394eb98bbb5f15dba1b6a8df69ed0bceb751b55e1d2cb548465632482b74b0b30367d82e3426fdf31ab6e88f613a5b40248981341d1da63154f66898c30e8f3e84e54b42426ce19cf17f1e6a661449c72557bdc6af8c97d31f567bc9b6bfa93a7559828ba7cd3fd73f04039f31886e2b1590649c699e7f284e9e43ac57b167fa559c4ee2a3058799c8f41e5f6df63e8ac5e010e3fd5395d565f6c363570ce20dd- … and 65 more
User-Agents seen on this fingerprint
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.84 Safari/537.36594×Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36556×Mozilla/5.0 (iPhone; CPU iPhone OS 14_4 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.4 Mobile/15E148 Safari/604.1354×Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36 OPR/92.0.0.0265×Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.3649×Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36 Edg/92.0.902.6722×Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.2 Safari/605.1.1518×Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.3617×Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.3611×Mozilla/5.0 (Linux; Android 7.1.1; F8331) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Mobile Safari/537.364×
A User-Agent is self-declared and trivially forged, so this names an observation rather than proving an identity. It is still the strongest signal available: the fingerprint comes off the TLS handshake and the User-Agent off the request that followed, and one client build keeping a stable JA4 while changing what it calls itself is a finding in its own right.
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.