PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t12d0608h2_2be37fd24b6f_de864c534845

Unclassified — observed in live traffic

Unclassified

t12d0608h2_2be37fd24b6f_de864c534845

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

What this fingerprint encodes

JA4_a t12d0608h2 handshake shape, human-readable
JA4_b 2be37fd24b6f truncated hash of the cipher list
JA4_c de864c534845 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
server name sent
Cipher suites offered
6
Extensions offered
8
ALPN
h2

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 6

Extensions 8

Named groups 2

Point formats 1

Raw JA3 string
771,49195-49199-49196-49200-49171-49172,16-13-10-5-65281-11-35-0,23-24,0

Seen in live traffic

Connections
4
First seen
2026-08-27 18:36 UTC
Last seen
2026-08-27 18:36 UTC
Transport
TCP
JA3 hashes absorbed
4

The same client, 4 different JA3s

This one JA4 covers 4 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 4 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.