PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 Fingerprint Directory

The database this edge classifies live traffic against — decoded, not just listed

Scanner

t11d6911ht_ea0618708e31_6f77ef117592

Legacy TLS client — inferred from the JA4 handshake shape.

What this fingerprint encodes

JA4_a t11d6911ht handshake shape, human-readable
JA4_b ea0618708e31 truncated hash of the cipher list
JA4_c 6f77ef117592 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.1
Server name
server name sent
Cipher suites offered
69
Extensions offered
11
ALPN
ht

Same tool, different options

These 3 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 69

Extensions 11

Named groups 4

Point formats 1

Raw JA3 string
770,22-51-103-49310-49314-158-57-107-49311-49315-159-69-190-136-196-154-49160-49161-49187-49324-49326-49195-49162-49188-49325-49327-49196-49266-49267-52393-4866-4865-52244-49159-49170-49171-49191-49199-49172-49192-49200-49248-49249-49270-49271-52392-4869-4868-4867-52243-49169-10-47-60-49308-49312-156-53-61-49309-49313-157-65-186-132-192-7-4-5,0-23-1-65281-10-11-35-16-13-51-45,29-23-24-25,0

Seen in live traffic

Connections
4
First seen
2026-08-22 23:53 UTC
Last seen
2026-08-23 03:17 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.