PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

PQ Crypta Logo

JA4 t12i990300_0df3f6915705_071c21b1fa59

Scanner — observed in live traffic

Scanner

t12i990300_0df3f6915705_071c21b1fa59

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

What this fingerprint encodes

JA4_a t12i990300 handshake shape, human-readable
JA4_b 0df3f6915705 truncated hash of the cipher list
JA4_c 071c21b1fa59 truncated hash of extensions + signature algorithms
Transport
TCP
TLS version
TLS 1.2
Server name
no server name (IP literal)
Cipher suites offered
99
Extensions offered
3
ALPN
none offered

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 399

Extensions 3

Named groups 6

Raw JA3 string
771,179-23-49190-31-55-114-143-49256-156-141-49232-49173-57-49230-49248-49186-129-17-74-48-49228-172-49408-49178-46-133-70-151-49157-49177-52-190-25-49162-78-49279-119-100-166-128-49320-146-47-63-49259-49309-49215-4866-49303-65279-66-49167-4865-37-185-97-149-49237-161-49411-173-174-7-49327-163-49174-14-72-4869-49305-49180-49203-49317-86-22-40-49270-49333-49218-49251-158-24-4868-26-49212-49195-5-43-138-64-81-53253-49318-65278-49209-49219-194-10-49322-49158-49254-45-52392-180-11-145-49191-187-130-49240-13-49245-176-39-49216-159-52397-102-49200-35-49299-41-49222-49202-196-175-49188-49153-30-49176-148-49183-49258-49278-150-51-21-83-6-49284-49262-49172-2-49160-181-49250-50-56-4871-49282-197-4870-91-53251-77-4867-53250-107-49236-49292-53249-75-52396-52395-52394-49288-49206-49239-60-27-116-52393-44-84-49164-49189-0-125-52243-79-193-49414-49280-49283-49412-49410-49241-191-168-49199-49332-49229-49170-49330-80-49329-49204-87-49326-49307-49269-49287-49313-73-49154-52244-49252-124-62-49319-49316-140-49217-54-136-49187-49225-36-49246-49311-15-68-49301-49310-49181-49308-49306-49304-188-49300-49298-20-38-32-49321-49296-49295-49242-53-49293-49263-49290-131-49289-49286-49210-49285-49243-49281-49413-71-4-49268-49276-49275-88-49273-49272-49198-49271-101-49325-49277-120-49267-49266-49197-49179-198-139-49264-49291-49261-103-147-49265-49255-49253-49257-34-49220-49249-49247-186-49244-8-49165-49169-49294-153-49213-49238-49235-9-49234-76-49161-49233-170-182-52398-49331-167-192-49226-49224-90-65-99-49223-152-49221-49156-82-169-49211-67-96-49196-49207-85-49205-49328-195-49208-49166-49193-49192-16-49323-134-49185-49184-49182-49175-49171-49168-49194-108-52245-49163-49159-49214-49155-49324-106-49201-42-49227-61-184-49409-126-189-49302-183-104-199-178-105-160-49274-121-164-162-177-33-89-18-155-12-154-49260-115-132-142-49315-49312-49314-135-165-58-3-29-144-137-98-92-171-49231-59-69-49-49297-109-19-1-28-157,10-15-13,23-24-25-29-256-4588,

Seen in live traffic

Connections
4
First seen
2026-09-06 23:30 UTC
Last seen
2026-09-07 11:57 UTC
Transport
TCP
JA3 hashes absorbed
4

The same client, 4 different JA3s

This one JA4 covers 4 distinct JA3 hashes. A JA3 hashes the cipher and extension lists in the order they arrived, so a client that shuffles them — which Chrome and its derivatives do on purpose — produces a new JA3 almost every connection and fragments into what looks like 4 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.

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.