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