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

Scanner

t13i100900_61a7ad8aa9b6_cb8fff09048f

Probe (no SNI, no ALPN) — inferred from the JA4 handshake shape.

What this fingerprint encodes

JA4_a t13i100900 handshake shape, human-readable
JA4_b 61a7ad8aa9b6 truncated hash of the cipher list
JA4_c cb8fff09048f truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.3
Server name
no server name (IP literal)
Cipher suites offered
10
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 10

Extensions 9

Named groups 3

Point formats 1

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

Seen in live traffic

Connections
1
First seen
2026-08-25 08:31 UTC
Last seen
2026-08-25 08:31 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.