PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t12d210400_89c2427e67e4_b648b7f3bc8e

Unclassified — observed in live traffic

Unclassified

t12d210400_89c2427e67e4_b648b7f3bc8e

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

What this fingerprint encodes

JA4_a t12d210400 handshake shape, human-readable
JA4_b 89c2427e67e4 truncated hash of the cipher list
JA4_c b648b7f3bc8e truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
server name sent
Cipher suites offered
21
Extensions offered
4
ALPN
none offered

Same tool, different options

These 80 other fingerprints share this one's JA4_c — the extension and signature-algorithm hash. A client that keeps its extension set constant while varying its cipher list produces exactly this pattern, which is what a scanner iterating cipher suites looks like. A JA3 cannot show you this: its single MD5 collapses ciphers and extensions together, so every variation looks like an unrelated client.

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 21

Extensions 4

Raw JA3 string
771,157-61-53-132-156-60-47-150-65-7-5-4-10-9-8-6-3-59-2-1-255,0-35-13-15,,

Seen in live traffic

Connections
3
First seen
2026-08-27 10:11 UTC
Last seen
2026-08-27 10:11 UTC
Transport
TCP

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.