PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t12d3805ht_10ed599f3404_4f2194e778ad

Unclassified — observed in live traffic

Unclassified

t12d3805ht_10ed599f3404_4f2194e778ad

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

What this fingerprint encodes

JA4_a t12d3805ht handshake shape, human-readable
JA4_b 10ed599f3404 truncated hash of the cipher list
JA4_c 4f2194e778ad truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
server name sent
Cipher suites offered
38
Extensions offered
5
ALPN
ht

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 38

Extensions 5

Named groups 3

Point formats 1

Raw JA3 string
771,52393-52392-52394-49200-49196-49192-49188-49172-49162-159-107-57-65413-196-136-129-157-61-53-192-132-49199-49195-49191-49187-49171-49161-158-103-51-190-69-156-60-47-186-65-255,0-11-10-13-16,29-23-24,0

Seen in live traffic

Connections
3
First seen
2026-08-27 17:26 UTC
Last seen
2026-08-27 18:22 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.