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