JA4 q13d0313h3_55b375c5d22e_6ca3580cd977

q13d0313h3_55b375c5d22e_6ca3580cd977

Chrome — 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_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256

Extensions 13

• encrypted_client_hello
• server_name
• signature_algorithms
• psk_key_exchange_modes
• key_share
• 51764 (0xca34)
• compress_certificate
• application_layer_protocol_negotiation
• supported_groups
• quic_transport_parameters
• 17613 (0x44cd)
• supported_versions
• pre_shared_key

Named groups 4

• SecP256r1MLKEM768
• x25519
• secp256r1
• secp384r1

771,4865-4866-4867,65037-0-13-45-51-51764-27-16-10-57-17613-43-41,4588-29-23-24,

Seen in live traffic

Connections

1306

First seen

2026-09-03 16:58 UTC

Last seen

2026-10-09 16:18 UTC

Transport

QUIC

JA3 hashes absorbed

1306

The same client, 1306 different JA3s

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

• d90dc3858eaccd11b3bac9125fd6dcc3
• 19f22a0540953a8707fd82d507bc2a71
• 8267cac4b8bcb14b0d1788f263fa4e3e
• 69375e1a8d1b1c93973389836546b883
• 864dde0f71c158aad32d6745a512d787
• 25283a3a94402295550e631131590fae
• 0c1577cc80bf21463300a20d1e9d666b
• c33a262b3671ceeed231ad49d19eaf01
• 320d453dfbef14bc80c8f825063cf4b7
• 424308a0d19583633b0cf89a15b23d62
• 25d9cd99870cc5e6b24a14e285626a1c
• edd7c4b31aa7d7821c5f053f76051769
• … and 1294 more

User-Agents seen on this fingerprint

• Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/152.0.0.0 Safari/537.36 11245×
• Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.0.0 Safari/537.36 2273×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/153.0.0.0 Safari/537.36 2196×
• Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/152.0.0.0 Safari/537.36 1506×
• Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/152.0.0.0 Safari/537.36 1417×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.0.0 Safari/537.36 1236×
• Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.0.0 Mobile Safari/537.36 484×
• Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/153.0.0.0 Mobile Safari/537.36 300×
• Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/152.0.0.0 Mobile Safari/537.36 294×
• Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/153.0.0.0 Safari/537.36 281×
• Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/153.0.0.0 Safari/537.36 98×
• Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/152.0.0.0 Safari/537.36 51×
• Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.0.0 Safari/537.36 3×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/155.0.0.0 Safari/537.36 1×
• Mozilla/5.0 (compatible; ev-crawler/1.0; +https://headline.com/web-crawler) 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.