q13d0313h3_55b375c5d22e_c6fc0bcabd40
Firefox — inferred from the User-Agent on its requests.
What this fingerprint encodes
q13d0313h3
handshake shape, human-readable
55b375c5d22e
truncated hash of the cipher list
c6fc0bcabd40
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_CHACHA20_POLY1305_SHA256 -
TLS_AES_256_GCM_SHA384
Extensions 13
-
encrypted_client_hello -
supported_versions -
server_name -
quic_transport_parameters -
signature_algorithms -
34 (0x0022) -
status_request -
compress_certificate -
supported_groups -
key_share -
application_layer_protocol_negotiation -
psk_key_exchange_modes -
record_size_limit
Named groups 5
-
SecP256r1MLKEM768 -
x25519 -
secp256r1 -
secp384r1 -
secp521r1
Raw JA3 string
771,4865-4867-4866,65037-43-0-57-13-34-5-27-10-51-16-45-28,4588-29-23-24-25,Seen in live traffic
- Connections
- 5
- First seen
- 2026-09-14 15:49 UTC
- Last seen
- 2026-10-22 10:35 UTC
- Transport
- QUIC
- JA3 hashes absorbed
- 5
The same client, 5 different JA3s
This one JA4 covers 5 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 5 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
9e0da737aef14932f1730c001336330854844bf5884ac8adfc421690aced361216942382da54c033b8fc40adeb96262fd8a66593f67258a047a3f6fb326d8d9a35fc19da7a9c64a136d1bd7074fb9c34
User-Agents seen on this fingerprint
Mozilla/5.0 (X11; Linux x86_64; rv:155.0) Gecko/20100101 Firefox/155.018×
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.