PQ CRYPTA PLATFORM

🏠 Main

🏠 Home
⏰ Q-Day Countdown
3
Y
77
D
13
H
16
M
31
S
961
MS

📰 News

📰 News
🗞️ Latest Headlines
Loading news...
Loading... • Just now

👤 Account

📝 Sign Up 🔑 Login 📊 Dashboard 💳 Billing 🛠️ Support Desk 🚪 Logout

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t13d1011h2_61a7ad8aa9b6_3a8073edd8ef

Browser — observed in live traffic

Browser

t13d1011h2_61a7ad8aa9b6_3a8073edd8ef

Chrome — inferred from the User-Agent on its requests.

What this fingerprint encodes

JA4_a t13d1011h2 handshake shape, human-readable
JA4_b 61a7ad8aa9b6 truncated hash of the cipher list
JA4_c 3a8073edd8ef truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.3
Server name
server name sent
Cipher suites offered
10
Extensions offered
11
ALPN
h2

Same tool, different options

These 4 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 10

Extensions 11

Named groups 3

Point formats 1

Raw JA3 string 
771,4866-4865-4867-49196-49195-52393-49200-49199-52392-255,23-35-10-11-13-0-45-43-51-5-16,29-23-24,0

Seen in live traffic

Connections
79
First seen
2026-08-31 01:41 UTC
Last seen
2026-10-14 23:48 UTC
Transport
TCP
JA3 hashes absorbed
73

The same client, 73 different JA3s

This one JA4 covers 73 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 73 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.

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.