t13d070600_c2f3549b8eb7_b3482a6e6e3b
Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.
What this fingerprint encodes
JA4_a
t13d070600
handshake shape, human-readable
JA4_b
c2f3549b8eb7
truncated hash of the cipher list
JA4_c
b3482a6e6e3b
truncated hash of extensions + signature algorithms
- Transport
- TCP
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 7
- Extensions offered
- 6
- 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 7
-
TLS_AES_128_GCM_SHA256 -
TLS_AES_256_GCM_SHA384 -
TLS_CHACHA20_POLY1305_SHA256 -
TLS_AES_128_CCM_SHA256 -
TLS_AES_128_CCM_8_SHA256 -
198 (0x00c6) -
199 (0x00c7)
Extensions 6
-
supported_groups -
server_name -
signature_algorithms -
supported_versions -
key_share -
renegotiation_info
Named groups 9
-
secp256r1 -
secp384r1 -
secp521r1 -
x25519 -
x448 -
31 (0x001f) -
32 (0x0020) -
33 (0x0021) -
41 (0x0029)
Raw JA3 string
771,4865-4866-4867-4868-4869-198-199,10-0-13-43-51-65281,23-24-25-29-30-31-32-33-41,Seen in live traffic
- Connections
- 27
- First seen
- 2026-09-17 13:53 UTC
- Last seen
- 2026-09-17 14:19 UTC
- Transport
- TCP
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.