t13d0309h2_55b375c5d22e_1b8ac57cf182
Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.
What this fingerprint encodes
JA4_a
t13d0309h2
handshake shape, human-readable
JA4_b
55b375c5d22e
truncated hash of the cipher list
JA4_c
1b8ac57cf182
truncated hash of extensions + signature algorithms
- Transport
- TCP
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 3
- Extensions offered
- 9
- ALPN
- h2
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 3
-
TLS_CHACHA20_POLY1305_SHA256 -
TLS_AES_128_GCM_SHA256 -
TLS_AES_256_GCM_SHA384
Extensions 9
-
server_name -
signed_certificate_timestamp -
encrypted_client_hello -
status_request -
supported_groups -
signature_algorithms -
application_layer_protocol_negotiation -
supported_versions -
key_share
Named groups 5
-
X25519Kyber768Draft00 -
x25519 -
secp256r1 -
secp384r1 -
secp521r1
Raw JA3 string
771,4867-4865-4866,0-18-65037-5-10-13-16-43-51,25497-29-23-24-25,Seen in live traffic
- Connections
- 1
- First seen
- 2026-10-24 09:53 UTC
- Last seen
- 2026-10-24 09:53 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.