Transport Layer Security (TLS)
Why You Should Care About TLS
TLS protects data in transit between a client and server by providing encryption, authentication, and integrity. Without TLS, any data sent between a browser and web server travels in plaintext, meaning anyone on the same network - such as a public Wi-Fi hotspot - can read passwords, session tokens, and personal information.
The protocol versions your server accepts affect security and compatibility. TLS 1.0 and 1.1 are formally deprecated and no longer meet current public-web baselines. TLS 1.2 remains secure when configured with strong cipher suites, while TLS 1.3 removes many legacy choices and reduces the full handshake to one round trip.
Running outdated TLS versions exposes your users to downgrade attacks, where an attacker forces the connection to use a weaker protocol version that can be broken. Payment Card Industry (PCI) compliance requires TLS 1.2 or higher, so e-commerce sites on older versions face compliance violations.
Settings Overview
| Setting | Recommended Value |
|---|---|
| Minimum TLS version | TLS 1.2 |
| Preferred TLS version | TLS 1.3 |
| TLS 1.0 | Disable |
| TLS 1.1 | Disable |
| Cipher suites | AEAD only (AES-GCM, ChaCha20) |
| Key exchange | ECDHE preferred |
Checking Your Setup
Run an SSL/TLS checker against your domain to see which TLS versions your server supports. The results will show whether TLS 1.0 and 1.1 are still enabled (they should be disabled) and whether TLS 1.3 is supported. Check the cipher suites listed to confirm no weak algorithms are in use.
Check SSL Certificate