PQ CRYPTA PLATFORM

🏠 Main

📰 News

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t13d080900_42230c8c7b22_d08fc002a886

Unclassified — observed in live traffic

Unclassified

t13d080900_42230c8c7b22_d08fc002a886

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

What this fingerprint encodes

JA4_a t13d080900 handshake shape, human-readable
JA4_b 42230c8c7b22 truncated hash of the cipher list
JA4_c d08fc002a886 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.3
Server name
server name sent
Cipher suites offered
8
Extensions offered
9
ALPN
none offered

Same tool, different options

These 3 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 8

Extensions 9

Named groups 30

Point formats 1

Raw JA3 string
771,4865-4867-4868-4869-49332-49333-198-199,0-10-11-13-18-43-45-51-21,514-4589-4588-4587-513-512-4585-4586-4590-25497-25498-24-23-25-29-30-26-27-28-31-32-33-22-21-41-256-257-258-259-260,0

Seen in live traffic

Connections
3
First seen
2026-10-11 18:20 UTC
Last seen
2026-10-11 18:24 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.