PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t13i711000_8f28d1f76561_8e6e362c5eac

Scanner — observed in live traffic

Scanner

t13i711000_8f28d1f76561_8e6e362c5eac

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

What this fingerprint encodes

JA4_a t13i711000 handshake shape, human-readable
JA4_b 8f28d1f76561 truncated hash of the cipher list
JA4_c 8e6e362c5eac truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.3
Server name
no server name (IP literal)
Cipher suites offered
71
Extensions offered
10
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 71

Extensions 10

Named groups 8

Point formats 3

Raw JA3 string
771,4866-4867-4865-51-57-53-47-49196-49200-163-159-52393-52392-52394-49325-49311-49245-49249-49239-49235-49195-49199-162-158-49324-49310-49244-49248-49238-49234-49188-49192-107-106-49267-49271-196-195-49187-49191-103-64-49266-49270-190-189-49162-49172-56-136-135-49161-49171-50-154-153-69-68-157-49309-49233-156-49308-49232-61-192-60-186-132-150-65,65281-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
1
First seen
2026-09-26 03:19 UTC
Last seen
2026-09-26 03:19 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.