Cipher suite
What is Cipher suite?
A cipher suite is the specific combination of cryptographic algorithms a client and server negotiate for a TLS connection; RFC 8446 simplified TLS 1.3's naming to just an AEAD cipher plus a hash. AdminKit's SSL check tool shows the TLS version and cipher suite a live site actually negotiates.
By AdminKit team, Netbase JSC · Updated
A cipher suite is the specific combination of cryptographic algorithms a client and server agree to use for a TLS connection. TLS 1.3, defined in RFC 8446, simplified this: a cipher suite now names only an AEAD algorithm for protecting record data, such as AES-128-GCM, paired with a hash function used with HKDF for key derivation and handshake authentication, such as SHA-256, written together as TLS_AES_128_GCM_SHA256 — one of the identifiers listed in IANA’s TLS Cipher Suites registry. This replaces TLS 1.2’s longer names, which bundled a key-exchange and authentication method into the same string, since TLS 1.3 negotiates those separately. Server software reflects that split: the openssl-ciphers documentation sets TLS 1.3 cipher suites through a separate -ciphersuites option, apart from the cipher list used for TLS 1.2 and below. During the TLS handshake, a client’s ClientHello lists every cipher suite it supports, and the server’s ServerHello picks one from that list; a server limited to outdated suites with known weaknesses exposes every connection to that weakness even when its certificate itself is completely valid — NIST’s own TLS implementation guidelines set out which cipher suites a server should still be configured to support.
Reading a TLS 1.3 cipher suite name:
- TLS_AES_128_GCM_SHA256 names an AEAD cipher (AES-128-GCM) plus a hash for key derivation (SHA-256).
- Key exchange and authentication are negotiated separately in TLS 1.3, unlike TLS 1.2’s longer suite names.
- IANA’s registry marks each suite “Recommended” or not, since older suites can be functional but weak.
Cipher suite negotiation is one of several checks AdminKit’s machine protocols cluster covers alongside certificate validation. A weak cipher suite is a different failure mode from a broken certificate chain: a handshake can negotiate strong cryptography even when the certificate itself doesn’t validate, and vice versa.
Frequently asked questions
What does a TLS 1.3 cipher suite name specify?
Only an AEAD algorithm for protecting record data, such as AES-128-GCM, paired with a hash function used with HKDF for key derivation, such as SHA-256.
How is this different from a TLS 1.2 cipher suite name?
TLS 1.2's longer names bundled a key-exchange and authentication method into the same string; TLS 1.3 negotiates those separately, so the suite name itself only covers the AEAD cipher and hash.
Who picks the cipher suite used for a connection?
The server -- a client's ClientHello lists every cipher suite it supports, and the server's ServerHello picks one from that list.
Where are valid TLS cipher suite identifiers registered?
IANA's TLS Cipher Suites registry, which also marks each suite 'Recommended' or not, since older suites can be functional but weak.