PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t13d301100_128a2ad15645_dd22a05640e6

Unclassified — observed in live traffic

Unclassified

t13d301100_128a2ad15645_dd22a05640e6

Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.

What this fingerprint encodes

JA4_a t13d301100 handshake shape, human-readable
JA4_b 128a2ad15645 truncated hash of the cipher list
JA4_c dd22a05640e6 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.3
Server name
server name sent
Cipher suites offered
30
Extensions offered
11
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 30

Extensions 11

Named groups 5

Point formats 3

Raw JA3 string
771,4866-4867-4865-49199-49195-49200-49196-158-162-49191-49187-49171-49161-49192-49188-49172-49162-103-51-64-107-56-57-156-157-60-61-47-53-255,0-11-10-35-5-22-23-13-43-45-51,29-23-30-25-24,0-1-2

Seen in live traffic

Connections
1
First seen
2026-09-29 02:31 UTC
Last seen
2026-09-29 02: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.