PQ CRYPTA PLATFORM

🏠 Main

📰 News

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t12d9911h9_557c97cf69ca_6f77ef117592

Scanner — observed in live traffic

Scanner

t12d9911h9_557c97cf69ca_6f77ef117592

Shares its JA4_c (6f77ef117592) with 3 fingerprints classified as scanner, and nothing else in that family disagrees — the same tool under different cipher options. Inferred from the family, not observed directly.

What this fingerprint encodes

JA4_a t12d9911h9 handshake shape, human-readable
JA4_b 557c97cf69ca truncated hash of the cipher list
JA4_c 6f77ef117592 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
h9

Same tool, different options

These 7 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 228

Extensions 11

Named groups 4

Point formats 1

Raw JA3 string
771,1-2-3-4-5-6-7-8-9-10-11-12-13-14-15-16-17-18-19-20-21-22-23-24-25-26-27-30-31-32-33-34-35-36-37-38-39-40-41-42-43-44-45-46-47-48-49-50-51-52-53-54-55-56-57-58-59-60-61-62-63-64-65-66-67-68-69-70-96-97-98-99-100-101-102-103-104-105-106-107-108-109-128-129-130-132-133-134-135-136-137-138-139-140-141-150-151-152-153-154-155-156-157-158-159-160-161-162-163-164-165-166-167-186-187-188-189-190-191-192-196-49153-49154-49155-49156-49157-49158-49159-49160-49161-49162-49163-49164-49165-49166-49167-49168-49169-49170-49171-49172-49173-49174-49175-49176-49177-49178-49179-49180-49181-49182-49183-49184-49185-49186-49187-49188-49189-49190-49191-49192-49193-49194-49195-49196-49197-49198-49199-49200-49201-49202-49203-49204-49205-49206-49207-49208-49209-49210-49211-49248-49249-49266-49267-49268-49269-49270-49271-49272-49273-49300-49301-49302-49303-49304-49305-49306-49307-49308-49309-49310-49311-49312-49313-49314-49315-49316-49317-49318-49319-49320-49321-49322-49323-49324-49325-49326-49327-52243-52244-52245-52392-52393-52394-65280-65281-65282-65283,0-23-1-65281-10-11-35-16-13-51-45,29-23-24-25,0

Seen in live traffic

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