t13d091000_f91f431d341e_0e0b92dd4b31
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
0e0b92dd4b31
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_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 10
-
key_share -
ec_point_formats -
supported_versions -
signature_algorithms -
extended_master_secret -
server_name -
status_request -
supported_groups -
psk_key_exchange_modes -
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,51-11-43-13-23-0-5-10-45-65037,4588-29-23-24,0Seen in live traffic
- Connections
- 7
- First seen
- 2026-10-06 18:55 UTC
- Last seen
- 2026-10-06 19:29 UTC
- Transport
- TCP
- JA3 hashes absorbed
- 7
The same client, 7 different JA3s
This one JA4 covers 7 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 7 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
7e494e88d0adb040e70af7b5ad9a85993c4a41bd6bea04108e0ad451fd6b02589c42f65ed2a111c3ba6d87725cc9a91346a5ccd976e965289c17fdaa9712b00d3ee964538a1da05f4f8f89b297895ce21d84b3bb876380c346ed62a2d6b2f99c8fd3dab060e08967b41b766618a54019
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.