PQ CRYPTA PLATFORM

🏠 Main

📰 News

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

Seen in live traffic

Connections
6
First seen
2026-09-06 23:30 UTC
Last seen
2026-09-21 14:43 UTC
Transport
TCP
JA3 hashes absorbed
6

The same client, 6 different JA3s

This one JA4 covers 6 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 6 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.