PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t12d630400_f4a33ce78bd4_3549fbaf615c

Scanner — observed in live traffic

Scanner

t12d630400_f4a33ce78bd4_3549fbaf615c

Shares its JA4_c (3549fbaf615c) with 6 fingerprints 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 t12d630400 handshake shape, human-readable
JA4_b f4a33ce78bd4 truncated hash of the cipher list
JA4_c 3549fbaf615c truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
server name sent
Cipher suites offered
63
Extensions offered
4
ALPN
none offered

Same tool, different options

These 12 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 63

Extensions 4

Named groups 6

Point formats 1

Raw JA3 string
771,29-28-65279-65278-99-101-17-114-19-115-50-64-162-116-56-106-163-49218-49238-49219-49239-68-189-49280-135-195-49281-18-102-153-143-144-178-49318-170-145-179-49319-171-49254-49260-49255-49261-49302-49296-49303-49297-52397-45-180-181-142-20-119-22-120-51-103-49310-49314-158-121-57,10-11-0-13,23-24-25-29-256-4588,0

Seen in live traffic

Connections
1
First seen
2026-08-27 08:59 UTC
Last seen
2026-08-27 08:59 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.