PQ CRYPTA PLATFORM

🏠 Main

📰 News

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t10d620300_89149463b124_33a13ba74d1c

Scanner — observed in live traffic

Scanner

t10d620300_89149463b124_33a13ba74d1c

Legacy TLS client — inferred from the JA4 handshake shape.

What this fingerprint encodes

JA4_a t10d620300 handshake shape, human-readable
JA4_b 89149463b124 truncated hash of the cipher list
JA4_c 33a13ba74d1c truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.0
Server name
server name sent
Cipher suites offered
62
Extensions offered
3
ALPN
none offered

Same tool, different options

These 48 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 62

Extensions 3

Named groups 37

Point formats 3

Raw JA3 string
769,71-72-73-74-75-76-5816-5818-49153-49154-49155-49156-49157-49158-49159-49160-49161-49162-49187-49188-49189-49190-49195-49196-49197-49198-49224-49225-49226-49227-49244-49245-49246-49247-49266-49267-49268-49269-49286-49287-49288-49289-49324-49325-49326-49327-49411-49412-49413-49414-52244-52393-4865-4866-4867-4868-4869-58388-58389-198-199-255,0-10-11,1-2-3-4-5-6-7-8-9-10-11-12-13-14-15-16-17-18-19-20-21-22-23-24-25-26-27-28-29-30-256-257-258-259-260-65281-65282,0-1-2

Seen in live traffic

Connections
1
First seen
2026-10-20 22:31 UTC
Last seen
2026-10-20 22:31 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.