q13d0313h3_55b375c5d22e_244a1882a899
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
244a1882a899
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 -
server_name -
supported_versions -
signature_algorithms -
supported_groups -
34 (0x0022) -
status_request -
psk_key_exchange_modes -
application_layer_protocol_negotiation -
key_share -
record_size_limit -
quic_transport_parameters -
pre_shared_key
Named groups 4
-
x25519 -
secp256r1 -
secp384r1 -
secp521r1
Raw JA3 string
771,4865-4867-4866,65037-0-43-13-10-34-5-45-16-51-28-57-41,29-23-24-25,Seen in live traffic
- Connections
- 4
- First seen
- 2026-10-03 08:49 UTC
- Last seen
- 2026-10-05 18:24 UTC
- Transport
- QUIC
- JA3 hashes absorbed
- 4
The same client, 4 different JA3s
This one JA4 covers 4 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 4 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
f36f8df68fc24c75118a34de3a5338d2579c3942fcd7158810ed68c7aa3e857da91db7c6ad94f1040c29f115892447be01392c383c796c97b7158cb65dfca163
User-Agents seen on this fingerprint
Mozilla/5.0 (X11; Linux x86_64; rv:140.0) Gecko/20100101 Firefox/140.0807×
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.