PQ CRYPTA PLATFORM

🏠 Main

📰 News

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t12d600400_f78222e0ad5a_c54f48fd7c65

Scanner — observed in live traffic

Scanner

t12d600400_f78222e0ad5a_c54f48fd7c65

Shares its JA4_c (c54f48fd7c65) with 14 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 t12d600400 handshake shape, human-readable
JA4_b f78222e0ad5a truncated hash of the cipher list
JA4_c c54f48fd7c65 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
server name sent
Cipher suites offered
60
Extensions offered
4
ALPN
none offered

Same tool, different options

These 20 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 60

Extensions 4

Named groups 5

Point formats 1

Raw JA3 string
771,49250-49231-49251-49272-49292-49273-49293-49163-49164-91-92-87-49175-90-49176-49177-89-49173-49174-88-79-82-81-80-83-86-85-84-129-131-128-130-49410-49408-49411-49413-49409-49412-49414-41-38-42-39-43-40-35-31-34-30-37-33-36-32-0-49322-49323-139-140-174-49316,11-0-10-13,23-24-25-29-256,0

Seen in live traffic

Connections
5
First seen
2026-10-03 09:38 UTC
Last seen
2026-10-24 09:41 UTC
Transport
TCP
JA3 hashes absorbed
3

The same client, 3 different JA3s

This one JA4 covers 3 distinct JA3 hashes. A JA3 hashes the cipher and extension lists in the order they arrived, so a client that shuffles them — which Chrome and its derivatives do on purpose — produces a new JA3 almost every connection and fragments into what looks like 3 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.

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.