PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 Fingerprint Directory

What this edge classifies traffic against, plus what it actually sees — decoded and named, not just listed

Unclassified

t13d490700_bd868743f55c_566b5f938b58

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

What this fingerprint encodes

JA4_a t13d490700 handshake shape, human-readable
JA4_b bd868743f55c truncated hash of the cipher list
JA4_c 566b5f938b58 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.3
Server name
server name sent
Cipher suites offered
49
Extensions offered
7
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 49

Extensions 7

Named groups 15

Point formats 1

Raw JA3 string
771,4865-4866-4867-49196-49195-52393-49200-52392-157-49198-49202-159-52394-163-49199-156-49197-49201-158-162-49188-49192-61-49190-49194-107-106-49162-49172-53-49157-49167-57-56-49187-49191-60-49189-49193-103-64-49161-49171-47-49156-49166-51-50-255,0-5-10-11-13-43-51,23-24-25-9-10-11-12-13-14-22-256-257-258-259-260,0

Seen in live traffic

Connections
1
First seen
2026-08-23 18:31 UTC
Last seen
2026-08-23 18: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.