Disable TLS 1.0 and 1.1: why they're deprecated and who still needs them

By TechCompare · Updated · How we check

Turn off TLS 1.0 and 1.1. No current browser uses them, RFC 8996 says software must not, and PCI DSS has banned them for card payments since June 2018.

TLS 1.0 dates from 1999 and TLS 1.1 from 2006. The IETF deprecated both in RFC 8996 in March 2021, and every current browser has stopped using them. A server that still accepts them gains nothing from browsers. It only gives old or badly configured clients a weaker way in, and it fails most compliance scans.

Topic
TLS 1.0 and 1.1
Old TLS versions
Category
TLS and certificates
Versions, keys and certificate errors

How this is calculated

Both versions lean on MD5 and SHA-1 inside the handshake, and neither supports the AEAD ciphers like AES-GCM that modern TLS is built around. Their CBC ciphers were the target of BEAST and a long run of padding attacks. RFC 8996 lists these reasons and moves both versions to Historic status, which means they must not be used.

Keeping them on gains nothing with browsers and costs you in audits. PCI DSS required card processors to drop early TLS by June 30, 2018, and most security scanners flag a server that still accepts it. The clients that need it are old and rare: Android 4.4 and older, Internet Explorer 10 and older, old Java and .NET programs with default settings, and embedded devices that never got an update.

To turn them off, set the minimum version in your server or CDN. In nginx, the line is ssl_protocols TLSv1.2 TLSv1.3. In Apache, it's SSLProtocol -all +TLSv1.2 +TLSv1.3. Cloudflare and other CDNs have a minimum TLS version setting for each site.

Check your other hosts too. Mail servers, APIs and forgotten subdomains are where old versions tend to live on. The SSL Checker tries TLS 1.0 and TLS 1.1 on their own, so it shows whether a server still accepts them even though no browser would ask.

Verdict

Set the minimum to TLS 1.2 everywhere, including mail, API and staging hosts. If a partner or device truly needs TLS 1.0, give it a separate host name with its own settings so your main site doesn't carry the risk. Then check each name and confirm both old versions are off.

More SSL scenarios

Frequently asked questions

Will turning off TLS 1.0 break my site for anyone?
Only for very old clients, like Android 4.4 and older or Internet Explorer 10 and older. Your server or CDN logs can show the TLS version of each request, so you can count how many still use TLS 1.0 or 1.1 before you switch.
Is SSL 3.0 the same problem?
It's worse. RFC 7568 deprecated SSL 3.0 in 2015 after the POODLE attack, and SSL 2.0 was banned before that. If a server still accepts either one, fix that first.
Does turning off TLS 1.1 matter if TLS 1.0 is already off?
Yes. TLS 1.1 has the same weak hashes as TLS 1.0 and no modern ciphers, and RFC 8996 deprecates both together. Turn them off at the same time.