PQ CRYPTA PLATFORM

🏠 Main

📰 News

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t10d140600_74fc3de17c53_950472255fe9

Scanner — observed in live traffic

Scanner

t10d140600_74fc3de17c53_950472255fe9

Legacy TLS client — inferred from the JA4 handshake shape.

What this fingerprint encodes

JA4_a t10d140600 handshake shape, human-readable
JA4_b 74fc3de17c53 truncated hash of the cipher list
JA4_c 950472255fe9 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.0
Server name
server name sent
Cipher suites offered
14
Extensions offered
6
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.0

Cipher suites 14

Extensions 6

Named groups 3

Point formats 1

Raw JA3 string
769,49162-49161-49172-49171-57-51-53-47-10-56-50-19-5-4,0-10-11-35-23-65281,29-23-24,0

Seen in live traffic

Connections
4
First seen
2026-09-04 04:59 UTC
Last seen
2026-09-17 14:03 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.