PQ CRYPTA PLATFORM

🏠 Main

📰 News

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t12d191100_b83c0aa35c7d_702512ee992c

Unclassified — observed in live traffic

Unclassified

t12d191100_b83c0aa35c7d_702512ee992c

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

What this fingerprint encodes

JA4_a t12d191100 handshake shape, human-readable
JA4_b b83c0aa35c7d truncated hash of the cipher list
JA4_c 702512ee992c truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
server name sent
Cipher suites offered
19
Extensions offered
11
ALPN
none offered

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 19

Extensions 11

Named groups 5

Point formats 1

Raw JA3 string
771,49196-49195-52393-49188-49187-49198-49197-49190-49189-49162-49161-49157-49156-49160-49155-49159-49154-49158-49153,0-5-10-11-17-23-35-13-43-50-65281,29-23-24-25-30,0

Seen in live traffic

Connections
4
First seen
2026-10-21 01:14 UTC
Last seen
2026-10-21 01:14 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.