PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 Fingerprint Directory

The database this edge classifies live traffic against — decoded, not just listed

Browser

t12i150200_8daaf6152771_c899f8114fe8

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

What this fingerprint encodes

JA4_a t12i150200 handshake shape, human-readable
JA4_b 8daaf6152771 truncated hash of the cipher list
JA4_c c899f8114fe8 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
no server name (IP literal)
Cipher suites offered
15
Extensions offered
2
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 15

Extensions 2

Raw JA3 string
771,4865-4866-4867-49195-49199-49196-49200-52393-52392-49171-49172-156-157-47-53,65037-51,,

Seen in live traffic

Connections
1
First seen
2026-08-23 05:04 UTC
Last seen
2026-08-23 05:04 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.