TLS_SHA384_SHA384

What each component means

A cipher suite names the algorithms a client and server agree on in one handshake. TLS_SHA384_SHA384 combines HMAC-SHA384 integrity protection without any encryption, plus the SHA384 hash. Each part is explained below with its known weaknesses; for the bigger picture see how cipher suites work.

TLS 1.3 suites only describe the symmetric part. The TLS 1.3 specification (RFC 9846) says its suites specify only the symmetric ciphers and cannot be used with TLS 1.2. Key exchange is negotiated separately through the supported_groups and key_share extensions (for example X25519, P-256 or the hybrid X25519MLKEM768) and is always ephemeral (EC)DHE unless a client resumes in the PSK-only psk_ke mode, so a full handshake always has forward secrecy. The certificate signature algorithm (for example RSA-PSS, ECDSA or Ed25519) is negotiated with signature_algorithms. In TLS_SHA384_SHA384, SHA384 is the hash behind the HKDF key schedule and the handshake transcript hash.

Encryption: none. TLS_SHA384_SHA384 is one of the two integrity-only TLS 1.3 suites of RFC 9150 (2022): records are authenticated with HMAC-SHA384 but sent in clear, for IoT and industrial settings that need integrity without confidentiality. The RFC itself states that the approach is not endorsed by the IETF and has no IETF consensus.

Why this rating

ssl.sh rating: Insecure. The reasons:

• No encryption (NULL cipher): traffic is sent in clear text.

How ssl.sh rates cipher suites

Which TLS libraries support it

Support for TLS_SHA384_SHA384 as read from each library's own source code or official documentation on 2026-11-10. “Enabled by default” means the library negotiates it with no configuration; “off by default” means it is implemented but has to be switched on.

None of the 9 libraries tracked here enables it by default. Also implemented by: OpenSSL 3.5.

NSS shows the library's own defaults; Firefox switches every NSS suite off at start-up and re-enables only those with a security.ssl3.* or security.tls13.* preference. Java defaults are derived from the jdk.tls.disabledAlgorithms value Oracle documents for JDK 21, which later updates may extend. The OpenSSL and GnuTLS rows only show whether the suite is implemented.

History and standards status

TLS_SHA384_SHA384 (0xC0,0xB5) is registered in the IANA TLS Cipher Suites registry with RFC 9150, “TLS 1.3 Authentication and Integrity-Only Cipher Suites” (April 2022, Informational) as its specification. The registry marks it D (discouraged), a value introduced by RFC 9847 (2025).

Enable or disable it in Nginx and Apache

OpenSSL 3.5 doesn't implement this suite, so stock Nginx and Apache httpd builds can't offer it and you don't need to disable it.

How to test whether a server accepts it

OpenSSL 3.5 cannot offer TLS_SHA384_SHA384, so openssl s_client can't test it directly; use a scanner that implements the suite itself.

nmap's ssl-enum-ciphers script connects repeatedly, trying one suite at a time, and lists every suite the server accepts with a grade from A to F. Look for TLS_SHA384_SHA384 in its output:

nmap --script ssl-enum-ciphers -p 443 example.com

If your nmap build doesn't print a TLS 1.3 section, rely on the openssl command instead.

To decode a name or hex code, use the cipher suite lookup; the SSL checker shows which protocol versions a live server accepts and the cipher suite it negotiates.