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

t13d081300_b8c177e1861e_6c16df1bb63e

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

What this fingerprint encodes

JA4_a t13d081300 handshake shape, human-readable
JA4_b b8c177e1861e truncated hash of the cipher list
JA4_c 6c16df1bb63e truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.3
Server name
server name sent
Cipher suites offered
8
Extensions offered
13
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 8

Extensions 13

Named groups 10

Point formats 1

Raw JA3 string
771,49196-49195-49199-49200-49171-49172-4865-4866,0-5-10-11-17-23-35-13-43-45-50-51-65281,29-23-24-25-30-256-257-258-259-260,0

Seen in live traffic

Connections
2
First seen
2026-08-24 00:09 UTC
Last seen
2026-08-24 00:09 UTC
Transport
TCP

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.