q13d0313h3_55b375c5d22e_eb028bd37c08
Chrome — inferred from the User-Agent on its requests.
What this fingerprint encodes
q13d0313h3
handshake shape, human-readable
55b375c5d22e
truncated hash of the cipher list
eb028bd37c08
truncated hash of extensions + signature algorithms
- Transport
- QUIC
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 3
- Extensions offered
- 13
- 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 13
-
4832 (0x12e0) -
quic_transport_parameters -
supported_versions -
signature_algorithms -
server_name -
application_layer_protocol_negotiation -
supported_groups -
51764 (0xca34) -
17613 (0x44cd) -
key_share -
compress_certificate -
encrypted_client_hello -
psk_key_exchange_modes
Named groups 4
-
SecP256r1MLKEM768 -
x25519 -
secp256r1 -
secp384r1
Raw JA3 string
771,4865-4866-4867,4832-57-43-13-0-16-10-51764-17613-51-27-65037-45,4588-29-23-24,Seen in live traffic
- Connections
- 3
- First seen
- 2026-10-15 04:17 UTC
- Last seen
- 2026-10-15 04:17 UTC
- Transport
- QUIC
- JA3 hashes absorbed
- 3
The same client, 3 different JA3s
This one JA4 covers 3 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 3 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
27c3301b5c80043e6250e18fd6eac6da07d6c11f1db4d7538f25901f349469071e7828adf863201a81062ab670bf27c1
User-Agents seen on this fingerprint
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/158.0.0.0 Safari/537.3689×
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.