PQ CRYPTA PLATFORM

🏠 Main

📰 News

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t12d320400_992cb694dc73_1ea9011b3dfa

Scanner — observed in live traffic

Scanner

t12d320400_992cb694dc73_1ea9011b3dfa

Shares its JA4_c (1ea9011b3dfa) 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 t12d320400 handshake shape, human-readable
JA4_b 992cb694dc73 truncated hash of the cipher list
JA4_c 1ea9011b3dfa truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
server name sent
Cipher suites offered
32
Extensions offered
4
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 32

Extensions 4

Named groups 26

Point formats 1

Raw JA3 string
771,136-150-156-157-158-159-255-49154-49155-49156-49157-49159-49160-49161-49162-49164-49165-49166-49167-49169-49170-49171-49172-49187-49188-49191-49195-49196-49199-49200-49201-49202,0-11-10-13,14-13-25-11-12-24-9-10-22-23-8-6-7-20-21-4-5-18-19-1-2-3-15-16-17-29,0

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.