PQ CRYPTA PLATFORM

🏠 Main

📰 News

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t11d640300_67f0ca237a44_6bf8f498b543

Scanner — curated classification

Scanner

t11d640300_67f0ca237a44_6bf8f498b543

nmap ssl-enum-ciphers, JA4 (stable across runs; observed 2026-07-31)

What this fingerprint encodes

JA4_a t11d640300 handshake shape, human-readable
JA4_b 67f0ca237a44 truncated hash of the cipher list
JA4_c 6bf8f498b543 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.1
Server name
server name sent
Cipher suites offered
64
Extensions offered
3
ALPN
none offered

Same tool, different options

These 21 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 64

Extensions 3

Named groups 6

Point formats 1

Raw JA3 string
770,89-49173-49174-88-79-82-81-80-83-86-85-84-129-131-128-130-49410-49408-49409-41-38-42-39-43-40-35-31-34-30-37-33-36-32-0-49322-49323-139-140-174-49316-49320-168-141-175-49317-49321-169-49252-49258-49253-49259-49300-49294-49301-49295-52395-44-176-177-138-98-97-96-100,10-0-11,23-24-25-29-256-4588,0

Seen in live traffic

Connections
15
First seen
2026-09-06 15:54 UTC
Last seen
2026-09-08 04:38 UTC
Transport
TCP
JA3 hashes absorbed
4

The same client, 4 different JA3s

This one JA4 covers 4 distinct JA3 hashes. A JA3 hashes the cipher and extension lists in the order they arrived, so a client that shuffles them — which Chrome and its derivatives do on purpose — produces a new JA3 almost every connection and fragments into what looks like 4 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.