PQ CRYPTA PLATFORM

🏠 Main

📰 News

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t12d9910h2_4596048de690_06f2bdcf8b15

Unclassified — observed in live traffic

Unclassified

t12d9910h2_4596048de690_06f2bdcf8b15

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

What this fingerprint encodes

JA4_a t12d9910h2 handshake shape, human-readable
JA4_b 4596048de690 truncated hash of the cipher list
JA4_c 06f2bdcf8b15 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
server name sent
Cipher suites offered
99
Extensions offered
10
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 287

Extensions 10

Named groups 5

Point formats 3

Raw JA3 string
771,52243-52245-52392-52394-52395-52396-52397-52398-47-53-5-10-4-9-0-1-2-3-6-7-8-11-49163-12-49164-13-49165-14-49166-15-49167-16-49168-17-49169-18-49170-19-49171-20-49172-21-49173-22-49174-23-49175-24-49176-25-49177-26-49178-27-49179-49180-49181-30-49182-31-49183-32-49184-33-49185-34-49186-35-36-37-38-39-49191-40-49192-41-49193-42-49194-43-44-45-46-49199-48-49200-49-49201-50-49202-51-49203-52-49204-49205-54-49206-55-49207-56-49208-57-49209-58-49210-59-49211-60-49212-61-49213-62-49214-63-49215-64-49216-65-49217-66-49218-67-49219-68-49220-69-49221-70-49222-49223-49228-49229-49230-49231-49232-49233-49234-49235-49236-49237-49238-49239-49240-49241-49242-49243-49248-49249-49250-49251-49252-49253-49254-103-49255-104-49256-105-49257-106-49258-107-49259-108-49260-109-49261-49262-49263-49264-49265-49270-49271-49272-49273-49274-49275-49276-49277-49278-49279-49280-49281-49282-49283-132-49284-133-49285-134-135-136-137-138-49290-139-49291-140-49292-141-49293-142-49294-143-49295-144-49296-145-49297-146-49298-147-49299-148-49300-149-49301-150-49302-151-49303-152-49304-153-49305-154-49306-155-49307-156-49308-157-49309-158-49310-159-49311-160-49312-161-49313-162-49314-163-49315-164-49316-165-49317-166-49318-167-49319-168-49320-169-49321-170-49322-171-49323-172-173-174-175-176-177-178-179-180-181-182-183-184-185-186-187-188-189-190-191-192-193-194-195-196-197,65281-18-5-0-23-35-13-11-10-16,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.