JA4 q13d0312h3_55b375c5d22e_f60bf7ff48f5

q13d0312h3_55b375c5d22e_f60bf7ff48f5

Edge — 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

12

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 12

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

Named groups 4

• SecP256r1MLKEM768
• x25519
• secp256r1
• secp384r1

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

Seen in live traffic

Connections

367

First seen

2026-08-22 23:52 UTC

Last seen

2026-08-26 01:35 UTC

Transport

QUIC

JA3 hashes absorbed

367

The same client, 367 different JA3s

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

• 251104094c0ce3e99cdcf61db1fa224c
• d6a9f9b140005ef57dd28628f84ab0a2
• c6f0405f3d39f50c7bd4cb50bbf2b8a9
• a5f0089848f35ea88fe41acb715a11bc
• c589784b379d74d4c754f08a18f0e58d
• 681f800c6af3238121db3a596d43032b
• 56585498daa1f73385f1b335446814d1
• c61358aec731659919899ec279a06980
• 73e1e60bd565e452c1db9d3597a6589e
• f8c2c2e74792c5c3438a8cd760b035b0
• 6d4bf11eef7ee31e305061a020a4d7aa
• 9a592b224b064e5090358e37f987593f
• … and 355 more

User-Agents seen on this fingerprint

• Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/151.0.0.0 Safari/537.36 Edg/151.0.0.0 7697×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/151.0.0.0 Safari/537.36 539×
• Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/143.0.7499.4 Safari/537.36 264×
• Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36 200×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 89×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.7444.175 Safari/537.36 17×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.7444.163 Safari/537.36 16×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.7390.0 Safari/537.36 15×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.7444.162 Safari/537.36 14×
• Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/150.0.0.0 Mobile Safari/537.36 8×
• Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/151.0.0.0 Safari/537.36 6×
• Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36 3×
• Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36 1×
• RootEvidence/1.0 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.