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

unclassified

t13i1714h2_5b57614c22b0_d27576f0e476

Seen in live traffic; not in the curated database.

What this fingerprint encodes

JA4_a t13i1714h2 handshake shape, human-readable
JA4_b 5b57614c22b0 truncated hash of the cipher list
JA4_c d27576f0e476 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.3
Server name
no server name (IP literal)
Cipher suites offered
17
Extensions offered
14
ALPN
h2

Same tool, different options

These 1 other fingerprints share this one's JA4_c — the extension and signature-algorithm hash. A client that keeps its extension set constant while varying its cipher list produces exactly this pattern, which is what a scanner iterating cipher suites looks like. A JA3 cannot show you this: its single MD5 collapses ciphers and extensions together, so every variation looks like an unrelated client.

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 17

Extensions 14

Named groups 6

Point formats 1

Raw JA3 string
771,4865-4867-4866-49195-49199-52393-52392-49196-49200-49162-49161-49171-49172-156-157-47-53,23-65281-10-11-35-16-5-34-51-43-13-45-28-65037,29-23-24-25-256-257,0

Seen in live traffic

Connections
1
First seen
2026-08-23 06:29 UTC
Last seen
2026-08-23 06:29 UTC
Transport
TCP

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.