PQ Crypta Logo

JA4 t13d531100_ed6c8d7875f9_ea55d4dd83c9

Unclassified — observed in live traffic

Unclassified

t13d531100_ed6c8d7875f9_ea55d4dd83c9

Presented a User-Agent we cannot attribute to a known client.

What this fingerprint encodes

JA4_a t13d531100 handshake shape, human-readable
JA4_b ed6c8d7875f9 truncated hash of the cipher list
JA4_c ea55d4dd83c9 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.3
Server name
server name sent
Cipher suites offered
53
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 53

Extensions 11

Named groups 10

Point formats 3

Raw JA3 string
771,4866-4867-4865-49199-49195-49200-49196-158-49191-103-49192-107-163-159-52393-52392-52394-49325-49311-49245-49249-49239-49235-162-49324-49310-49244-49248-49238-49234-49188-106-49187-64-49162-49172-57-56-49161-49171-51-50-157-49309-49233-156-49308-49232-61-60-53-47-255,0-11-10-35-22-23-13-43-45-51-27,29-23-30-25-24-256-257-258-259-260,0-1-2

Seen in live traffic

Connections
8
First seen
2026-11-20 14:27 UTC
Last seen
2026-11-20 14:27 UTC
Transport
TCP

User-Agents seen on this fingerprint

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.

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions