PQ Crypta Logo

JA4 t12i200800_0bf03fa604e3_c3f51f8b1329

Scanner — observed in live traffic

Scanner

t12i200800_0bf03fa604e3_c3f51f8b1329

Probe (no SNI, no ALPN) — inferred from the JA4 handshake shape.

What this fingerprint encodes

JA4_a t12i200800 handshake shape, human-readable
JA4_b 0bf03fa604e3 truncated hash of the cipher list
JA4_c c3f51f8b1329 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
no server name (IP literal)
Cipher suites offered
20
Extensions offered
8
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 20

Extensions 8

Named groups 3

Point formats 1

Raw JA3 string
771,49162-49172-57-107-53-61-49159-49161-49187-49169-49171-49191-51-103-50-5-4-47-60-10,61184-65281-10-11-35-13172-30031-5,23-24-25,0

Seen in live traffic

Connections
2
First seen
2026-11-11 02:22 UTC
Last seen
2026-11-11 06:23 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.

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions