PQ CRYPTA PLATFORM

🏠 Main

📰 News

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t12d9911h2_42b77b2c6fe0_7c7e8cb9a282

Unclassified — observed in live traffic

Unclassified

t12d9911h2_42b77b2c6fe0_7c7e8cb9a282

Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.

What this fingerprint encodes

JA4_a t12d9911h2 handshake shape, human-readable
JA4_b 42b77b2c6fe0 truncated hash of the cipher list
JA4_c 7c7e8cb9a282 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
server name sent
Cipher suites offered
99
Extensions offered
11
ALPN
h2

Same tool, different options

These 1 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 101

Extensions 11

Named groups 5

Point formats 3

Raw JA3 string
771,49153-49154-49155-49156-49157-11-49163-12-49164-13-49165-14-49166-15-49167-16-49173-49174-23-49175-24-49176-25-49177-26-27-49189-49190-49193-49194-49197-49198-48-49-49201-49202-52-54-55-58-62-49214-63-49215-49216-49217-66-67-70-49222-49223-49226-49227-49230-49231-49236-49237-49240-49241-49242-49243-49246-49247-49250-49251-104-105-108-109-49268-49269-49272-49273-49278-49279-49282-49283-49284-133-49285-134-49288-137-49289-49292-49293-151-152-155-160-161-164-165-166-167-187-188-191-193-194-197,65281-18-5-0-23-35-13-11-10-16-21,29-23-30-25-24,0-1-2

Seen in live traffic

Connections
2
First seen
2026-10-21 01:14 UTC
Last seen
2026-10-21 01:14 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.