t13d1012h1_61a7ad8aa9b6_365e8e3f38a9
Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.
What this fingerprint encodes
t13d1012h1
handshake shape, human-readable
61a7ad8aa9b6
truncated hash of the cipher list
365e8e3f38a9
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
- 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 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
-
key_share -
supported_groups -
extended_master_secret -
application_layer_protocol_negotiation -
supported_versions -
ec_point_formats -
psk_key_exchange_modes -
status_request -
session_ticket -
signature_algorithms -
compress_certificate -
server_name
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,51-10-23-16-43-11-45-5-35-13-27-0,4588-29-23-24,0Seen in live traffic
- Connections
- 19
- First seen
- 2026-10-15 23:15 UTC
- Last seen
- 2026-10-15 23:58 UTC
- Transport
- TCP
- JA3 hashes absorbed
- 19
The same client, 19 different JA3s
This one JA4 covers 19 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 19 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
8daf88a973e3b85cc9bd690146f3ec6f7736ab79e969e241300cb075d9f1d7965f95aedbb6ba158c4d013e04b0f06a704d883f8ae8c16ab2264b773d65866e944ddb03807843b75908a734a9ce9fcf49ac4bef42f9011648f517b2390d3a2c7e9a522e4fe4cb8a295dbc14aae9f8f6d9184642f56f1b0fba5fa4fb4471b30d8cfdf7c3dd8176124b42d534cb203ae0ab2084e974d25bb706e74c0f4b72802645d882c4e767d992de50e4d18d94233df8f8e63cf6d6f24067c900eb69f852a9f1- … and 7 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.