t13d061100_db2546af4a66_e5728521abd4
Presented a User-Agent we cannot attribute to a known client.
What this fingerprint encodes
t13d061100
handshake shape, human-readable
db2546af4a66
truncated hash of the cipher list
e5728521abd4
truncated hash of extensions + signature algorithms
- Transport
- TCP
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 6
- Extensions offered
- 11
- ALPN
- none offered
Same tool, different options
These 11 other fingerprints share this one's JA4_c — the extension and signature-algorithm hash. A client that keeps its extension set constant while varying its cipher list produces exactly this pattern, which is what a scanner iterating cipher suites looks like. A JA3 cannot show you this: its single MD5 collapses ciphers and extensions together, so every variation looks like an unrelated client.
- t13i131000_f57a46bbacb6_e5728521abd4
- t13i191000_9dc949149365_e5728521abd4
- t13d141100_cbb2034c60b8_e5728521abd4
- t13d1412h1_cbb2034c60b8_e5728521abd4
- t13d191100_9dc949149365_e5728521abd4
- t13d1912h2_9dc949149365_e5728521abd4
- t13d251100_b78ed14e2fd0_e5728521abd4
- t13i141000_cbb2034c60b8_e5728521abd4
- t13i1911ht_9dc949149365_e5728521abd4
- t13i251000_b78ed14e2fd0_e5728521abd4
- t13i1411h2_cbb2034c60b8_e5728521abd4
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 6
-
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 -
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 -
TLS_RSA_WITH_AES_128_GCM_SHA256 -
TLS_AES_128_GCM_SHA256 -
TLS_AES_256_GCM_SHA384 -
TLS_CHACHA20_POLY1305_SHA256
Extensions 11
-
server_name -
ec_point_formats -
renegotiation_info -
extended_master_secret -
signed_certificate_timestamp -
status_request -
supported_groups -
signature_algorithms -
signature_algorithms_cert -
supported_versions -
key_share
Named groups 4
-
x25519 -
secp256r1 -
secp384r1 -
secp521r1
Point formats 1
-
uncompressed
Raw JA3 string
771,49195-49199-156-4865-4866-4867,0-11-65281-23-18-5-10-13-50-43-51,29-23-24-25,0Seen in live traffic
- Connections
- 3
- First seen
- 2026-09-14 02:53 UTC
- Last seen
- 2026-09-17 04:10 UTC
- Transport
- TCP
User-Agents seen on this fingerprint
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.363×
A User-Agent is self-declared and trivially forged, so this names an observation rather than proving an identity. It is still the strongest signal available: the fingerprint comes off the TLS handshake and the User-Agent off the request that followed, and one client build keeping a stable JA4 while changing what it calls itself is a finding in its own right.
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.