JA4 q13d0313h3_55b375c5d22e_824790d21c68

q13d0313h3_55b375c5d22e_824790d21c68

Firefox — inferred from the User-Agent on its requests.

What this fingerprint encodes

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
• quic_transport_parameters
• record_size_limit
• key_share
• application_layer_protocol_negotiation
• status_request
• psk_key_exchange_modes
• supported_groups
• 34 (0x0022)
• compress_certificate
• signature_algorithms

Named groups 5

• SecP256r1MLKEM768
• x25519
• secp256r1
• secp384r1
• secp521r1

771,4865-4867-4866,65037-0-43-57-28-51-16-5-45-10-34-27-13,4588-29-23-24-25,

Seen in live traffic

Connections

69

First seen

2026-09-03 13:23 UTC

Last seen

2026-10-06 11:13 UTC

Transport

QUIC

JA3 hashes absorbed

69

The same client, 69 different JA3s

This one JA4 covers 69 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 69 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.

• 1a1681c85bb37bf343e4762eeca0f13b
• a62620bb71b13899ddc32355910fbc5e
• 0f6bb16e172eeb4c660d7f55132004da
• 2a4954c0188a1f501cd9e79605ed76ef
• 268afc709512e3b0484c4cd54d9147b8
• 86cdcfd8a83217dc7624e1cf13f1ce13
• efabfc4ed86249058abcbacfaedcb6c9
• 705261c311893554bbc562542c2d62ad
• ca71bfa172031976fd0f136bca83a3a6
• a3925b32f0ae144aaa328d5599ad2ea6
• a8ea13e37957f472ef625ec2ba614b1a
• eeb141eb23be5ad23a8ebb5dbffce33e
• … and 57 more

User-Agents seen on this fingerprint

• Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:155.0) Gecko/20100101 Firefox/155.0 546×
• Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:155.0) Gecko/20100101 Firefox/155.0 267×
• Mozilla/5.0 (X11; Linux x86_64; rv:154.0) Gecko/20100101 Firefox/154.0 200×
• Mozilla/5.0 (X11; Linux x86_64; rv:153.0) Gecko/20100101 Firefox/153.0 89×
• Mozilla/5.0 (X11; Linux x86_64; rv:155.0) Gecko/20100101 Firefox/155.0 86×
• Mozilla/5.0 (Android 16; Mobile; rv:157.0) Gecko/157.0 Firefox/157.0 83×
• Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:153.0) Gecko/20100101 Firefox/153.0 74×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:152.0) Gecko/20100101 Firefox/152.0 51×
• Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:154.0) Gecko/20100101 Firefox/154.0 39×
• Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:155.0) Gecko/20100101 Firefox/155.0 38×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:157.0) Gecko/20100101 Firefox/157.0 38×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:154.0) Gecko/20100101 Firefox/154.0 37×
• Mozilla/5.0 (X11; Linux x86_64; rv:151.0) Gecko/20100101 Firefox/151.0 33×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.0.0 Safari/537.36 28×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:147.0) Gecko/20100101 Firefox/147.0 28×
• Mozilla/5.0 (X11; Linux x86_64; rv:157.0) Gecko/20100101 Firefox/157.0 24×
• Mozilla/5.0 (Android 14; Mobile; rv:154.0) Gecko/154.0 Firefox/154.0 24×
• Mozilla/5.0 (Android 15; Mobile; rv:154.0) Gecko/154.0 Firefox/154.0 23×
• Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:154.0) Gecko/20100101 Firefox/154.0 23×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0 23×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:153.0) Gecko/20100101 Firefox/153.0 18×
• Mozilla/5.0 (Android 16; Mobile; rv:155.0) Gecko/155.0 Firefox/155.0 2×
• Mozilla/5.0 (X11; Linux x86_64; rv:158.0) Gecko/20100101 /158.0a1 1×

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.