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