PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 Fingerprint Directory

The database this edge classifies live traffic against — decoded, not just listed

Browser

q13d0413h3_16476d049b0b_745ab6f97f32

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

What this fingerprint encodes

JA4_a q13d0413h3 handshake shape, human-readable
JA4_b 16476d049b0b truncated hash of the cipher list
JA4_c 745ab6f97f32 truncated hash of extensions + signature algorithms
Transport
QUIC
TLS version
TLS 1.3
Server name
server name sent
Cipher suites offered
4
Extensions offered
13
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 4

Extensions 13

Named groups 10

Point formats 3

Raw JA3 string
771,4866-4867-4865-255,0-11-10-16-22-23-49-13-43-45-51-57-21,29-23-30-25-24-256-257-258-259-260,0-1-2

Seen in live traffic

Connections
27
First seen
2026-08-22 23:52 UTC
Last seen
2026-08-23 04:05 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.