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

t13d521100_b262b3658495_6ecbdee5c734

Presented a User-Agent we cannot attribute to a known client.

What this fingerprint encodes

JA4_a t13d521100 handshake shape, human-readable
JA4_b b262b3658495 truncated hash of the cipher list
JA4_c 6ecbdee5c734 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.3
Server name
server name sent
Cipher suites offered
52
Extensions offered
11
ALPN
none offered

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

Cipher suites 52

Extensions 11

Named groups 8

Point formats 3

Raw JA3 string
771,4866-4867-4865-49199-49195-49200-49196-158-49191-103-49192-107-163-159-52393-52392-52394-49325-49311-49245-49249-49239-49235-162-49324-49310-49244-49248-49238-49234-49188-106-49187-64-49162-49172-57-56-49161-49171-51-50-157-49309-49233-156-49308-49232-61-60-53-47,65281-0-11-10-35-22-23-13-43-45-51,4588-29-23-30-24-25-256-257,0-1-2

Seen in live traffic

Connections
5
First seen
2026-08-23 15:49 UTC
Last seen
2026-08-23 15:50 UTC
Transport
TCP

User-Agents seen on this fingerprint

A User-Agent is self-declared and trivially forged, so this names an observation rather than proving an identity. It is still the strongest signal available: the fingerprint comes off the TLS handshake and the User-Agent off the request that followed, and one client build keeping a stable JA4 while changing what it calls itself is a finding in its own right.

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.