PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t13i270800_fa4239e4ca25_97f8aa674fd9

Scanner — observed in live traffic

Scanner

t13i270800_fa4239e4ca25_97f8aa674fd9

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

What this fingerprint encodes

JA4_a t13i270800 handshake shape, human-readable
JA4_b fa4239e4ca25 truncated hash of the cipher list
JA4_c 97f8aa674fd9 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.3
Server name
no server name (IP literal)
Cipher suites offered
27
Extensions offered
8
ALPN
none offered

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 27

Extensions 8

Named groups 4

Point formats 1

Raw JA3 string
771,49199-49200-49195-49196-52392-52393-49171-49161-49172-49162-156-157-47-53-49170-10-50-19-56-64-102-106-162-163-4865-4867-4866,5-10-11-13-65281-18-43-51,29-23-24-25,0

Seen in live traffic

Connections
1
First seen
2026-09-13 02:45 UTC
Last seen
2026-09-13 02:45 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.