PQ CRYPTA PLATFORM

🏠 Main

📰 News

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t12d340200_280581216cf5_e2a7de7a8184

Scanner — observed in live traffic

Scanner

t12d340200_280581216cf5_e2a7de7a8184

Shares its JA4_c (e2a7de7a8184) with 1 fingerprint classified as scanner, and nothing else in that family disagrees — the same tool under different cipher options. Inferred from the family, not observed directly.

What this fingerprint encodes

JA4_a t12d340200 handshake shape, human-readable
JA4_b 280581216cf5 truncated hash of the cipher list
JA4_c e2a7de7a8184 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
server name sent
Cipher suites offered
34
Extensions offered
2
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 34

Extensions 2

Raw JA3 string
771,4-5-10-13-16-19-22-47-48-49-50-51-53-54-55-56-57-60-61-62-63-64-65-68-69-102-103-104-105-106-107-132-135-255,0-13,,

Seen in live traffic

Connections
73
First seen
2026-08-23 18:30 UTC
Last seen
2026-10-16 02:50 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.