PQ Crypta Logo

JA4 t13d031100_55b375c5d22e_e19b3a8c6eed

Unclassified — observed in live traffic

Unclassified

t13d031100_55b375c5d22e_e19b3a8c6eed

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

What this fingerprint encodes

JA4_a t13d031100 handshake shape, human-readable
JA4_b 55b375c5d22e truncated hash of the cipher list
JA4_c e19b3a8c6eed truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.3
Server name
server name sent
Cipher suites offered
3
Extensions offered
11
ALPN
none offered

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

Extensions 11

Named groups 1

Point formats 3

Raw JA3 string
771,4866-4867-4865,0-11-10-35-22-23-13-43-45-51-27,29,0-1-2

Seen in live traffic

Connections
2
First seen
2026-11-22 13:22 UTC
Last seen
2026-11-22 13:22 UTC
Transport
TCP
JA3 hashes absorbed
2

The same client, 2 different JA3s

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

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.

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions