PQ Crypta Logo

JA4 t12i300300_1d37bd780c83_d410c4c61a4f

API client — observed in live traffic

API client

t12i300300_1d37bd780c83_d410c4c61a4f

curl — inferred from the User-Agent on its requests.

What this fingerprint encodes

JA4_a t12i300300 handshake shape, human-readable
JA4_b 1d37bd780c83 truncated hash of the cipher list
JA4_c d410c4c61a4f truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
no server name (IP literal)
Cipher suites offered
30
Extensions offered
3
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 30

Extensions 3

Raw JA3 string
771,4866-4867-4865-49196-49200-159-52393-52392-52394-49195-49199-158-49188-49192-107-49187-49191-103-49162-49172-57-49161-49171-51-157-156-61-60-53-47,65281-0-24878,,

Seen in live traffic

Connections
4
First seen
2026-11-17 04:10 UTC
Last seen
2026-11-17 04:13 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