t13d0912h2_f91f431d341e_011413bc0759
Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.
What this fingerprint encodes
t13d0912h2
handshake shape, human-readable
f91f431d341e
truncated hash of the cipher list
011413bc0759
truncated hash of extensions + signature algorithms
- Transport
- TCP
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 9
- Extensions offered
- 12
- ALPN
- h2
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 9
-
TLS_AES_256_GCM_SHA384 -
TLS_CHACHA20_POLY1305_SHA256 -
TLS_AES_128_GCM_SHA256 -
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 -
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 -
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 -
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 -
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 -
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Extensions 12
-
psk_key_exchange_modes -
ec_point_formats -
supported_versions -
compress_certificate -
server_name -
signature_algorithms -
key_share -
supported_groups -
status_request -
application_layer_protocol_negotiation -
extended_master_secret -
encrypted_client_hello
Named groups 3
-
SecP256r1MLKEM768 -
secp384r1 -
secp256r1
Point formats 1
-
uncompressed
Raw JA3 string
771,4866-4867-4865-49196-49195-52393-49200-49199-52392,45-11-43-27-0-13-51-10-5-16-23-65037,4588-24-23,0Seen in live traffic
- Connections
- 20
- First seen
- 2026-10-20 20:18 UTC
- Last seen
- 2026-10-20 21:22 UTC
- Transport
- TCP
- JA3 hashes absorbed
- 20
The same client, 20 different JA3s
This one JA4 covers 20 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 20 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
bae21de0b061ee513d2329a52bcc4abbc4f61c216885146cfd6195bbd48714ea05e690ebe944507bec4d256680b1bc4c0c5914c9ca831972f2dac25190f77a4dcf3ee7ec529f463641245f080ee950e6ced15cae69962efd9c86452bddfbcd8c9ebc1a250552516ad472bdac9322c19f26b0df96d86f472afc198481a18a84b20e9d0a927cabfe6730f1bfe435f6053c4e586088b5f7657ad4f975e11e89c94797bb8cb782c0d71c5e4d2ed52ad0157d50a26183b20111b649da729555f694ad- … and 8 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.