b2KIT

Cipher Suite Reference

Browse and search TLS cipher suites with security ratings, protocol compatibility, and recommendation status.

Tested tool guide Tested browser tools Checked August 16, 2026

What Cipher Suite Reference does and how it behaves

Cipher Suite Reference is a searchable catalog for identifying TLS cipher suites and comparing their security rating, supported protocol versions, and recommendation status. Search by a suite identifier, such as a standardized TLS name, to narrow the catalog to relevant entries. The important distinction is that this is a reference lookup, not a connection test. It does not contact a hostname, inspect a server configuration, or prove that a browser and server will successfully negotiate the listed suite.

How the result is produced

1

Suite lookup

Enter a cipher suite identifier or a recognizable portion of one to find matching catalog entries. Each result associates the suite name with reference information such as its security rating, protocol compatibility, and recommendation status. This is useful when translating a suite name from configuration, documentation, or a TLS diagnostic report into a readable assessment.

2

Protocol interpretation

Read protocol compatibility separately from the security rating. A suite can be defined for particular TLS versions without being suitable for a current deployment policy. TLS 1.3 suite names also describe fewer negotiation components than earlier suite names: authentication and key exchange are selected independently rather than encoded into names such as TLS_AES_128_GCM_SHA256.

Good uses

  • Checking whether a cipher suite copied from a web server configuration is associated with an obsolete or current TLS version.
  • Comparing similarly named suites before editing an application, proxy, or load balancer cipher policy.
  • Interpreting cipher suite identifiers found in a TLS scan, handshake trace, audit report, or vendor compatibility document.

Limits and checks

  • A catalog match does not show whether any specific server enables, prefers, or successfully negotiates that suite.
  • Recommendation status is a summary, not a substitute for the security policy, compliance profile, client population, or platform requirements governing a deployment.
  • Cipher suite selection is only part of TLS security. Protocol versions, certificates, key sizes, signature algorithms, extensions, and endpoint configuration can change the overall result.

Common questions

Can I enter a domain name to see which cipher suites its server supports?

No. This tool searches cipher suite reference data rather than connecting to a remote TLS service. Obtain the negotiated or supported suite names from a server scanner, browser diagnostic, command-line client, or handshake trace, then use those identifiers here to review their ratings, protocol compatibility, and recommendation status.

Why does a TLS 1.3 cipher suite name omit RSA, ECDHE, or certificate authentication?

TLS 1.3 cipher suite names identify the authenticated-encryption algorithm and the hash used with HKDF. Key exchange and authentication are negotiated through separate TLS mechanisms, so they are not embedded in the suite name. Consequently, a TLS 1.3 suite entry does not by itself identify the certificate type or complete handshake configuration.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools