PQ CRYPTA PLATFORM

🏠 Main

📰 News

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t12d320800_b415a99ff5d8_3ebdebe9c84d

Unclassified — observed in live traffic

Unclassified

t12d320800_b415a99ff5d8_3ebdebe9c84d

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

What this fingerprint encodes

JA4_a t12d320800 handshake shape, human-readable
JA4_b b415a99ff5d8 truncated hash of the cipher list
JA4_c 3ebdebe9c84d truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
server name sent
Cipher suites offered
32
Extensions offered
8
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 32

Extensions 8

Named groups 5

Point formats 3

Raw JA3 string
771,49196-163-52393-49327-49325-49245-49239-49195-162-49326-49324-49244-49238-49188-106-49267-195-49187-64-49266-189-49162-56-135-49161-50-153-68-49159-49160-19-255,0-11-10-35-5-22-23-13,29-23-30-25-24,0-1-2

Seen in live traffic

Connections
1
First seen
2026-10-06 20:46 UTC
Last seen
2026-10-06 20:46 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.