q13d0310h3_55b375c5d22e_85bcee6495dd
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
85bcee6495dd
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
-
supported_versions -
signature_algorithms -
compress_certificate -
application_settings -
server_name -
psk_key_exchange_modes -
supported_groups -
application_layer_protocol_negotiation -
key_share -
quic_transport_parameters
Named groups 3
-
x25519 -
secp256r1 -
secp384r1
Raw JA3 string
771,4865-4866-4867,43-13-27-17513-0-45-10-16-51-57,29-23-24,Seen in live traffic
- Connections
- 1
- First seen
- 2026-08-24 14:11 UTC
- Last seen
- 2026-08-24 14:11 UTC
- Transport
- QUIC
User-Agents seen on this fingerprint
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.361×
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.