PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t10d130300_48b83dc3bfb9_6bf8f498b543

Scanner — observed in live traffic

Scanner

t10d130300_48b83dc3bfb9_6bf8f498b543

Legacy TLS client — inferred from the JA4 handshake shape.

What this fingerprint encodes

JA4_a t10d130300 handshake shape, human-readable
JA4_b 48b83dc3bfb9 truncated hash of the cipher list
JA4_c 6bf8f498b543 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.0
Server name
server name sent
Cipher suites offered
13
Extensions offered
3
ALPN
none offered

Same tool, different options

These 15 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 13

Extensions 3

Named groups 28

Point formats 1

Raw JA3 string
769,255-49162-49172-57-56-49157-49167-49161-49171-51-50-49156-49166,0-10-11,14-13-25-28-11-12-27-24-9-10-26-22-23-8-6-7-20-21-4-5-18-19-1-2-3-15-16-17,0

Seen in live traffic

Connections
4
First seen
2026-08-26 02:15 UTC
Last seen
2026-08-26 02:15 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.