PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t13d090900_f91f431d341e_543460421724

Unclassified — observed in live traffic

Unclassified

t13d090900_f91f431d341e_543460421724

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

What this fingerprint encodes

JA4_a t13d090900 handshake shape, human-readable
JA4_b f91f431d341e truncated hash of the cipher list
JA4_c 543460421724 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.3
Server name
server name sent
Cipher suites offered
9
Extensions offered
9
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 9

Extensions 9

Named groups 3

Point formats 1

Raw JA3 string
771,4866-4867-4865-49196-49195-52393-49200-49199-52392,0-5-11-45-23-13-10-43-51,4588-24-23,0

Seen in live traffic

Connections
7
First seen
2026-08-22 23:50 UTC
Last seen
2026-08-26 01:14 UTC
Transport
TCP
JA3 hashes absorbed
7

The same client, 7 different JA3s

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