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

Scanner

t11d8007h2_1f3a8b8a208a_f21fe9b79f04

Legacy TLS client — inferred from the JA4 handshake shape.

What this fingerprint encodes

JA4_a t11d8007h2 handshake shape, human-readable
JA4_b 1f3a8b8a208a truncated hash of the cipher list
JA4_c f21fe9b79f04 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.1
Server name
server name sent
Cipher suites offered
80
Extensions offered
7
ALPN
h2

Same tool, different options

These 2 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.1

Cipher suites 80

Extensions 7

Named groups 7

Raw JA3 string
770,49172-49162-49186-49185-49184-57-56-55-54-136-135-134-133-49167-49157-53-132-49171-49161-49183-49182-49181-51-50-128-129-130-131-49-48-154-153-152-151-69-68-67-66-49166-49156-47-150-65-7-49169-49159-102-49164-49154-5-4-49170-49160-49180-49179-49178-22-19-16-13-49165-49155-10-99-21-18-15-12-98-9-101-100-20-17-14-11-8-6-3-255,0-10-13-23-5-18-16,29-30-23-24-25-256-257,

Seen in live traffic

Connections
1
First seen
2026-08-25 07:49 UTC
Last seen
2026-08-25 07:49 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.