JA4 q13d0311h3_55b375c5d22e_35002cbdedc5

q13d0311h3_55b375c5d22e_35002cbdedc5

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

11

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_256_GCM_SHA384
• TLS_AES_128_GCM_SHA256
• TLS_CHACHA20_POLY1305_SHA256

Extensions 11

• signature_algorithms
• status_request
• server_name
• quic_transport_parameters
• supported_groups
• extended_master_secret
• key_share
• application_layer_protocol_negotiation
• ec_point_formats
• supported_versions
• psk_key_exchange_modes

Named groups 3

• x25519
• secp256r1
• secp384r1

Point formats 1

• uncompressed

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

Seen in live traffic

Connections

588

First seen

2026-08-22 23:53 UTC

Last seen

2026-08-26 01:40 UTC

Transport

QUIC

JA3 hashes absorbed

585

The same client, 585 different JA3s

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

• f47c523120e1639ed7682f70ed43c3b7
• 41bbf3be121c007f7930c8ba551fedc6
• 890638222512dfa869c6afeedcf99b44
• 9f896408848256ef9afd154d8729fa73
• 0a5b4d993287759ba9ca09c9589d09d2
• 95cdf1aa1616ee4507da2b9c97d132de
• d787519beb483df536357567a3d5b041
• 152582ff49f6f50a8af2ddc5734539d9
• d618f53b465aba98a38d7138a8547de8
• 99a3373aa5350bb6d1416a93f6c39e83
• aa0f493fe1c8cb58e04744cb8f1720cb
• b518ebe84f53ef2dc924b287e9d3ae9d
• … and 573 more

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.