PQ CRYPTA PLATFORM

🏠 Main

📰 News

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t13i1411h2_cbb2034c60b8_e5728521abd4

Unclassified — observed in live traffic

Unclassified

t13i1411h2_cbb2034c60b8_e5728521abd4

Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.

What this fingerprint encodes

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

Same tool, different options

These 11 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 14

Extensions 11

Named groups 4

Point formats 1

Raw JA3 string
771,49195-49199-49196-49200-52393-52392-49161-49171-49162-49172-49170-4865-4866-4867,11-65281-23-18-5-10-13-50-16-43-51,29-23-24-25,0

Seen in live traffic

Connections
1
First seen
2026-10-12 05:56 UTC
Last seen
2026-10-12 05:56 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.