PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t12i640300_e31a90cd0803_99875426d20b

Scanner — observed in live traffic

Scanner

t12i640300_e31a90cd0803_99875426d20b

Probe (no SNI, no ALPN) — inferred from the JA4 handshake shape.

What this fingerprint encodes

JA4_a t12i640300 handshake shape, human-readable
JA4_b e31a90cd0803 truncated hash of the cipher list
JA4_c 99875426d20b truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
no server name (IP literal)
Cipher suites offered
64
Extensions offered
3
ALPN
none offered

Same tool, different options

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

Extensions 3

Named groups 6

Point formats 1

Raw JA3 string
771,109-167-49222-49242-49223-49243-70-191-49284-137-197-49285-26-24-155-49330-49328-49331-49329-49160-49161-49187-49324-49326-49195-49162-49188-49325-49327-49196-49224-49244-49225-49245-49266-49286-49267-49287-52393-52244-49158-49159-49204-49205-49207-53251-53253-53249-49206-49208-53250-49264-49265-49306-49307-52396-49209-49210-49211-49203-49170-49171-49191-49199,10-11-13,23-24-25-29-256-4588,0

Seen in live traffic

Connections
5
First seen
2026-08-27 08:43 UTC
Last seen
2026-08-27 08:50 UTC
Transport
TCP
JA3 hashes absorbed
2

The same client, 2 different JA3s

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

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.