Free TLS Cipher Suite Reference

The tool includes 25+ cipher suites spanning TLS 1.0 through TLS 1.3 with security classifications.

Perfect Forward Secrecy (PFS) means each session uses a unique key, so past sessions remain secure even if the server key is compromised.

Yes, completely free.

Absolutely. The TLS Cipher Suite Reference processes everything client-side in your browser. No data is uploaded to or stored on any server. Your content remains private on your device at all times.

Yes, the TLS Cipher Suite Reference is fully responsive and works on smartphones and tablets. You can use it on any device with a modern web browser -- no app download required.

No account or registration is needed. Simply open the TLS Cipher Suite Reference in your browser and start using it immediately. There are no sign-up walls or usage restrictions.

Simply enter your input in the provided field, adjust any settings to your preference, and the tool will process it instantly. You can then copy the result to your clipboard or download it.

The TLS Cipher Suite Reference works in all modern browsers including Chrome, Firefox, Safari, Edge, and Opera. For the best experience, use the latest version of your preferred browser.

A TLS 1.2 cipher suite name encodes four choices in a fixed order. The key exchange comes first (ECDHE), describing how the client and server agree on a shared secret without sending it in the clear. The authentication algorithm follows (RSA), proving the server's identity with its certificate. After the word WITH comes the bulk encryption that actually protects your data (AES-256-GCM), and finally the hash used for message integrity and key derivation (SHA-384). So TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 means ephemeral elliptic-curve Diffie-Hellman key exchange, RSA authentication, 256-bit AES in GCM mode, and SHA-384. TLS 1.3 names are shorter, like TLS_AES_256_GCM_SHA384, because key exchange and authentication are negotiated separately from the cipher. Paste any suite name into this reference's search box to see each component broken out alongside its security rating and forward-secrecy status.

The key-exchange algorithm decides how the client and server establish the shared secret that encrypts a session. Static RSA encrypts that secret with the server's long-term public key, so anyone who later steals the matching private key can decrypt every recorded session. ECDHE (and DHE) instead generate a fresh, ephemeral key pair for each handshake using elliptic-curve Diffie-Hellman, then discard it. Because the long-term key only signs the exchange rather than encrypting the secret, a future key compromise cannot unlock past traffic. That property is Perfect Forward Secrecy, and it is why ECDHE suites are rated Recommended here while static-RSA suites top out at Secure. This reference flags each suite's key exchange and PFS support so you can prioritize ephemeral, forward-secret options in your server's cipher order.

TLS 1.0 and 1.1 were formally deprecated in 2021 by RFC 8996 and should be disabled on every server. They rely on outdated CBC-mode ciphers paired with SHA-1 or MD5, and they support broken primitives like RC4, DES, and export-grade 40-bit crypto. TLS 1.0 is exploitable through the BEAST and POODLE attacks, which let an attacker recover plaintext from an encrypted session. Neither version offers the AEAD encryption that modern protocols require, and leaving them enabled is one of the most common findings in an SSL scan. Major browsers dropped support years ago, so keeping them on adds risk without serving real users. In this reference, every TLS 1.0 and 1.1 suite is rated Insecure; filter by version to confirm which legacy suites your configuration should drop.

GCM and CBC are two ways a block cipher like AES encrypts your data, and the choice strongly affects security. CBC (Cipher Block Chaining) only encrypts; it needs a separate MAC for integrity, and that combination has produced a string of padding-oracle attacks such as POODLE and Lucky 13, especially with SHA-1. GCM (Galois/Counter Mode) is an AEAD mode: it encrypts and authenticates in a single step, eliminating padding entirely and resisting those attacks. That is why modern best practice favors AES-GCM and ChaCha20-Poly1305, and why TLS 1.3 dropped CBC suites completely. In this reference, GCM-based suites carry Recommended or Secure ratings while CBC suites with older hashes are marked Weak or Insecure. Filter by security rating to see exactly which CBC suites to phase out of your server.

The reference table itself is static data built into the page, so it shows how cipher suites are rated in general but cannot see your actual server. To test a live site, enter a domain in the Check Your Site box and press the button; the tool opens the Qualys SSL Labs Server Test in a new tab for that domain. SSL Labs then connects to your server, lists every cipher suite and TLS version it actually negotiates, checks for known vulnerabilities, and assigns an overall letter grade from A+ down to F. That scan runs on SSL Labs' infrastructure, not on this site, and nothing you type is uploaded here. Use this table to decide which suites you want, then run the SSL Labs check to confirm your real-world configuration matches your intent.