PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t13d050600_13f69f63e3fe_83fe30743d85

Unclassified — observed in live traffic

Unclassified

t13d050600_13f69f63e3fe_83fe30743d85

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

What this fingerprint encodes

JA4_a t13d050600 handshake shape, human-readable
JA4_b 13f69f63e3fe truncated hash of the cipher list
JA4_c 83fe30743d85 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.3
Server name
server name sent
Cipher suites offered
5
Extensions offered
6
ALPN
none offered

Same tool, different options

These 2 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 5

Extensions 6

Named groups 48

Raw JA3 string
771,198-199-4865-4868-4869,10-0-13-43-51-65281,15-16-17-18-19-20-21-22-23-24-25-1-2-3-4-5-6-7-8-9-10-11-12-13-14-29-30-41-26-27-28-31-32-33-256-257-258-259-260-512-513-514-4585-4586-4587-4588-4589-4590,

Seen in live traffic

Connections
8
First seen
2026-09-17 13:53 UTC
Last seen
2026-09-17 14:19 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.