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