q13d0310h3_55b375c5d22e_8732cbce638c
Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.
What this fingerprint encodes
q13d0310h3
handshake shape, human-readable
55b375c5d22e
truncated hash of the cipher list
8732cbce638c
truncated hash of extensions + signature algorithms
- Transport
- QUIC
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 3
- Extensions offered
- 10
- ALPN
- h3
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 3
-
TLS_AES_256_GCM_SHA384 -
TLS_AES_128_GCM_SHA256 -
TLS_CHACHA20_POLY1305_SHA256
Extensions 10
-
quic_transport_parameters -
server_name -
application_layer_protocol_negotiation -
supported_groups -
signature_algorithms -
supported_versions -
key_share -
status_request -
psk_key_exchange_modes -
encrypted_client_hello
Named groups 4
-
SecP256r1MLKEM768 -
x25519 -
secp256r1 -
secp384r1
Raw JA3 string
771,4866-4865-4867,57-0-16-10-13-43-51-5-45-65037,4588-29-23-24,Seen in live traffic
- Connections
- 90
- First seen
- 2026-10-06 19:58 UTC
- Last seen
- 2026-10-07 22:23 UTC
- Transport
- QUIC
- JA3 hashes absorbed
- 90
The same client, 90 different JA3s
This one JA4 covers 90 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 90 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
f25fd0d610c2b4c740c77653c60e24dae5f23adff548b28a1b10aef046c719a42ec0ccfb7b9bbf3c7b770a3d9673f8aee8a350a11c233c1fbe9199d1fac9512b03e9660c65da6ed2acb50699c8380ed751a4abbaedf051c5b69ba2ce1b684474cdf0736ce887ea5d2687b9b33af048a28b6a557c2a894057857f71e45d8f0dfb23b38beac5e92de17a92bb495c11f9a4a269dbf4fa62e7d7a4605ccae70a6538addc0538e9722974d13e15eddaffdf17aa5766c779a710f014e2d7bb1c586dbf- … and 78 more
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.