JA4 q13d0310h3_55b375c5d22e_6da5d9173cfb

q13d0310h3_55b375c5d22e_6da5d9173cfb

Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.

What this fingerprint encodes

Transport

QUIC

TLS version

TLS 1.3

Server name

server name sent

Cipher suites offered

3

Extensions offered

10

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 10

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

Named groups 3

• x25519
• secp256r1
• secp384r1

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

Seen in live traffic

Connections

11

First seen

2026-09-13 03:06 UTC

Last seen

2026-09-13 03:49 UTC

Transport

QUIC

JA3 hashes absorbed

11

The same client, 11 different JA3s

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

• bfc03ebb14860d45c31fac28af7269e8
• 275c834bc7c0031d298aecfa910c79b1
• 69d67176b9e408cfb0aa49a6e81cbf52
• a43dbc8b1fa728fc6781aac91565525a
• bb3b67225f7a87185108b048e35eac8d
• 634a67cd8d11152117274a45e2daaa48
• d502d3f4859a5916daf9ca1f625ce3a8
• 1413848ee6f2fbf0486a84dd156b937f
• 4e26c7e2b29cb501ce86bc055d3eda11
• 48050d6543b1c707f7db5953f4b0d811
• dcc2d36031cfc8f1758dec50cf4dbba5

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.