t13d041100_16476d049b0b_73702258a521
Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.
What this fingerprint encodes
JA4_a
t13d041100
handshake shape, human-readable
JA4_b
16476d049b0b
truncated hash of the cipher list
JA4_c
73702258a521
truncated hash of extensions + signature algorithms
- Transport
- TCP
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 4
- Extensions offered
- 11
- 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 4
-
TLS_AES_256_GCM_SHA384 -
TLS_CHACHA20_POLY1305_SHA256 -
TLS_AES_128_GCM_SHA256 -
TLS_EMPTY_RENEGOTIATION_INFO_SCSV
Extensions 11
-
server_name -
ec_point_formats -
supported_groups -
session_ticket -
status_request -
encrypt_then_mac -
extended_master_secret -
signature_algorithms -
supported_versions -
psk_key_exchange_modes -
key_share
Named groups 5
-
x25519 -
secp256r1 -
x448 -
secp521r1 -
secp384r1
Point formats 3
-
uncompressed -
ansiX962_compressed_prime -
ansiX962_compressed_char2
Raw JA3 string
771,4866-4867-4865-255,0-11-10-35-5-22-23-13-43-45-51,29-23-30-25-24,0-1-2Seen in live traffic
- Connections
- 1
- First seen
- 2026-08-23 18:31 UTC
- Last seen
- 2026-08-23 18:31 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.