PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 Fingerprint Directory

What this edge classifies traffic against, plus what it actually sees — decoded and named, not just listed

Browser

q13d0312h3_55b375c5d22e_35ab28bf858e

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

What this fingerprint encodes

JA4_a q13d0312h3 handshake shape, human-readable
JA4_b 55b375c5d22e truncated hash of the cipher list
JA4_c 35ab28bf858e truncated hash of extensions + signature algorithms
Transport
QUIC
TLS version
TLS 1.3
Server name
server name sent
Cipher suites offered
3
Extensions offered
12
ALPN
h3

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 3

Extensions 12

Named groups 5

Raw JA3 string
771,4866-4867-4865,0-10-16-5-13-18-51-45-43-57-27-41,4588-29-23-24-25,

Seen in live traffic

Connections
6
First seen
2026-08-23 12:39 UTC
Last seen
2026-08-23 15:24 UTC
Transport
QUIC

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.