PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t13i190500_9c2f387b437f_05020bd715f8

Scanner — observed in live traffic

Scanner

t13i190500_9c2f387b437f_05020bd715f8

Probe (no SNI, no ALPN) — inferred from the JA4 handshake shape.

What this fingerprint encodes

JA4_a t13i190500 handshake shape, human-readable
JA4_b 9c2f387b437f truncated hash of the cipher list
JA4_c 05020bd715f8 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.3
Server name
no server name (IP literal)
Cipher suites offered
19
Extensions offered
5
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 19

Extensions 5

Named groups 7

Point formats 1

Raw JA3 string
771,4871-4870-4869-4868-4865-4866-4867-49332-49333-199-198-49330-49328-49331-49329-49411-49413-49412-49414,10-43-11-13-51,23-24-25-29-256-4588-41,0

Seen in live traffic

Connections
5
First seen
2026-08-27 08:43 UTC
Last seen
2026-08-27 08:49 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.