How to Disable TLS 1.0 and 1.1 and Allow Only TLS 1.2+

TLS 1.0 and 1.1 are deprecated encryption protocols, but many servers and CDNs still accept them for backward compatibility. This guide shows you how to find where TLS is handled for your site, restrict it to TLS 1.2 and 1.3, and confirm that the old versions are refused.

By Updated ⏱ 20–40 minutes🎯 Intermediate● High impactSecurity
Illustration: Old TLS versions disabled (1.0/1.1) fix guide
SECURITY · FIX GUIDE Old TLS versions disabled (1.0/1.… IMPACTEFFORT TIME20–40 minutes LEVELIntermediate

Why it matters

1 were formally deprecated by RFC 8996 in 2021. They rely on weak constructions such as SHA-1 and MD5 in the handshake and CBC-mode ciphers exposed to attacks like BEAST. Every current browser already refuses them, so keeping them enabled adds attack surface without helping real visitors.

They also fail PCI DSS requirements and cost you points on SSL Labs and security questionnaires. Turning them off is a small server change that signals to users, partners and automated security scanners that your HTTPS setup is maintained.

✕Beforeopenssl s_client -connectexample.com:443 -tls1_1 completes ahandshake: the server still accepts✓AfterHandshakes using -tls1 and -tls1_1fail with 'no protocols available' or'handshake failure', while TLS 1.2 and

What you need

Admin access to your web server config (Nginx/Apache) or your CDN/load balancer dashboard
SSH access and sudo rights if you manage your own server
A terminal with OpenSSL or nmap for testing
A maintenance window or the ability to reload the web server

Step-by-step fix

1

Confirm which TLS versions are currently accepted

Test the public hostname your visitors use, not the server's IP address. 1 on the client side by default. Lower the client security level for the test, or you may get a false 'pass'.

1 command prints a certificate chain and a 'Protocol' line, that version is still enabled.

text
# Should FAIL after the fix
openssl s_client -connect example.com:443 -servername example.com -tls1 -cipher 'DEFAULT@SECLEVEL=0' </dev/null
openssl s_client -connect example.com:443 -servername example.com -tls1_1 -cipher 'DEFAULT@SECLEVEL=0' </dev/null

# Or list everything at once
nmap --script ssl-enum-ciphers -p 443 example.com
Pro tip: Also test www.example.com and any subdomains. Each hostname can be served by a different server or CDN configuration.
2

Find out who terminates TLS for your site

The setting must be changed wherever the HTTPS connection actually ends. This might be your origin server, a CDN, or a load balancer. Check the response headers and DNS:

  • A server: cloudflare or cf-ray header means Cloudflare.
  • x-amz-cf-id or via: ... CloudFront means AWS CloudFront.
  • DNS pointing to an *.elb.amazonaws.com name means an AWS load balancer.
  • No CDN headers usually means your own Nginx/Apache/IIS answers directly.
text
curl -sI https://example.com | grep -iE 'server|via|cf-ray|x-amz|x-served-by'
dig +short example.com
Pro tip: If a CDN sits in front, fix the CDN first, because that is what the audit and visitors connect to. Then also restrict the origin so nobody can bypass the CDN with old protocols.
3

Check whether any real clients still need TLS 1.0/1.1

1 in 2020. 3 and below), Windows 7 without updates, or outdated API integrations and payment terminals. On Nginx, log the negotiated protocol for a few days to see whether anything legitimate is affected.

1 before you switch.

nginx
# In the http {} block of nginx.conf
log_format tlslog '$remote_addr [$time_local] "$request" $ssl_protocol "$http_user_agent"';
access_log /var/log/nginx/tls.log tlslog;

# After a few days:
awk '{print $(NF-1)}' /var/log/nginx/tls.log | sort | uniq -c
Pro tip: On Apache, add %{SSL_PROTOCOL}x to your LogFormat to get the same data.
4

Restrict protocols in Nginx

conf. Set the directive in the http {} block so it applies to all virtual hosts. Nginx negotiates the protocol using the default server's settings, so a value set in only one server {}` block can be silently ignored.

Then test the config and reload.

nginx
# Find existing settings
sudo grep -Rn 'ssl_protocols' /etc/nginx /etc/letsencrypt 2>/dev/null

# /etc/nginx/nginx.conf  (inside http { ... })
ssl_protocols TLSv1.2 TLSv1.3;
ssl_prefer_server_ciphers off;

# Apply
sudo nginx -t && sudo systemctl reload nginx
Pro tip: `ssl_prefer_server_ciphers off` follows Mozilla's 'Intermediate' profile. Because all enabled ciphers are strong, letting the client choose is fine and helps mobile devices pick ChaCha20.
5

Restrict protocols in Apache

conf for SSLProtocol`. Set it in the global SSL config so every vhost inherits it. Remove or update any per-vhost overrides.

1 or newer.

apache
# Find existing settings
sudo grep -Rn 'SSLProtocol' /etc/apache2 /etc/httpd /etc/letsencrypt 2>/dev/null

# e.g. /etc/apache2/mods-available/ssl.conf or /etc/httpd/conf.d/ssl.conf
SSLProtocol -all +TLSv1.2 +TLSv1.3
SSLHonorCipherOrder off

# Apply (Debian/Ubuntu)
sudo apachectl configtest && sudo systemctl reload apache2
# RHEL/Alma/Rocky
sudo apachectl configtest && sudo systemctl reload httpd
Pro tip: If you use cPanel/WHM, go to WHM » Service Configuration » Apache Configuration » Global Configuration » SSL/TLS Protocols. Set it to `TLSv1.2 +TLSv1.3` there instead of editing files that WHM overwrites.
6

Set the minimum TLS version on your CDN or load balancer

If a CDN or load balancer terminates TLS, change it in its dashboard:

  • Cloudflare: SSL/TLS » Edge Certificates » Minimum TLS Version » TLS 1.2. Keep 'TLS 1.3' switched on on the same page.
  • AWS CloudFront: Distribution » General » Edit » Security policy » TLSv1.2_2021 (requires a custom SSL certificate with SNI).
  • AWS ALB/NLB: Listener » HTTPS:443 » Edit » Security policy » ELBSecurityPolicy-TLS13-1-2-2021-06.
  • Azure Front Door / App Service: set Minimum TLS version to 1.2 under the domain or TLS/SSL settings.
text
# AWS CLI example for an ALB listener
aws elbv2 modify-listener \
  --listener-arn arn:aws:elasticloadbalancing:REGION:ACCOUNT:listener/app/example-co/... \
  --ssl-policy ELBSecurityPolicy-TLS13-1-2-2021-06
Pro tip: Cloudflare applies the minimum version per zone, but you can override it per hostname via Certificate Packs or Custom Hostnames. Check that no subdomain still has an override set to 1.0.
7

Retest and confirm old versions are refused

Repeat the tests from step 1 against every hostname. 1 should now fail the handshake. 3 should still connect.

Then run a full scan and rerun the audit.

text
# Expected: handshake failure / no protocols available
openssl s_client -connect example.com:443 -servername example.com -tls1_1 -cipher 'DEFAULT@SECLEVEL=0' </dev/null

# Expected: success, 'Protocol  : TLSv1.3' (or TLSv1.2)
openssl s_client -connect example.com:443 -servername example.com -tls1_2 </dev/null | grep Protocol
openssl s_client -connect example.com:443 -servername example.com -tls1_3 </dev/null | grep Protocol
Pro tip: CDN changes can take a few minutes to propagate to all edge locations. Wait 5–10 minutes before declaring a test failed.

Platform-specific notes

WordPress

WordPress itself has no TLS setting. The protocol is controlled by your host. On managed hosts (e.g. WP Engine, Kinsta, SiteGround), TLS 1.2+ is usually enforced already. If the audit still fails, open a support ticket or check the host's 'SSL/TLS' panel. On a VPS, use the Nginx/Apache steps. In cPanel, use WHM's SSL/TLS Protocols setting. In Plesk, go to Tools & Settings » SSL/TLS Ciphers and Protocols.

Shopify

Shopify manages TLS for all storefront domains and only accepts TLS 1.2 and 1.3, so there is nothing to configure. If the audit fails on a Shopify store, a proxy or CDN in front of the store (e.g. a custom Cloudflare setup or a separate subdomain on another server) is accepting old versions. Fix it there.

Next.js / Vercel / Netlify

Vercel and Netlify only accept TLS 1.2+ by default. If you self-host Next.js with `next start`, TLS is handled by whatever sits in front of it (Nginx, Caddy, a load balancer or a CDN). Set the minimum version to TLS 1.2 there and enable TLS 1.3. Caddy already defaults to TLS 1.2–1.3.

Cloudflare

Set SSL/TLS » Edge Certificates » Minimum TLS Version to TLS 1.2. This only covers the connection between visitors and Cloudflare. Also restrict your origin server so it can't be reached directly over TLS 1.0/1.1. Ideally, also firewall the origin to Cloudflare IP ranges.

IIS / Windows Server

Disable TLS 1.0 and 1.1 in the registry under HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server and TLS 1.1\Server. In each, set Enabled=0 and DisabledByDefault=1. Alternatively, use the free IIS Crypto tool with its 'Best Practices' template. A reboot is required.

Check that it worked

✅ How to verify

  • Run `openssl s_client -connect example.com:443 -servername example.com -tls1 -cipher 'DEFAULT@SECLEVEL=0'` and the same with `-tls1_1`. Both must fail the handshake.
  • Run `nmap --script ssl-enum-ciphers -p 443 example.com` and confirm only TLSv1.2 and TLSv1.3 sections are listed.
  • Scan the domain with Qualys SSL Labs (ssllabs.com/ssltest). Under Configuration » Protocols, TLS 1.0 and TLS 1.1 should show 'No'.
  • Rerun the audit for each HTTPS hostname and confirm it reports that TLS 1.0 and 1.1 are refused.

⚠️ Common mistakes

  • Changing only the origin server while a CDN or load balancer in front still accepts TLS 1.0/1.1. The audit tests what the public hostname accepts.
  • Setting `ssl_protocols` in a single Nginx server block while the default server or an included Certbot file still allows TLSv1/TLSv1.1.
  • Testing with a modern OpenSSL client without `-cipher 'DEFAULT@SECLEVEL=0'`. The client refuses old protocols itself, so you get a false 'pass'.
  • Accidentally removing TLS 1.3 (e.g. `SSLProtocol TLSv1.2` only). This still passes the check but gives up faster, more secure handshakes.

Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.

Check my site free

FAQ

Will disabling TLS 1.0 and 1.1 break my website for visitors?

Not for real visitors using current software. Chrome, Firefox, Safari and Edge all dropped TLS 1.0/1.1 in 2020, and any device from roughly 2014 onward supports TLS 1.2. The only clients affected are very old Android versions, unpatched Windows 7/XP machines, and outdated scripts or integrations. Check your logs first if you have B2B API clients.

How do I check which TLS versions my server supports?

There are three ways. You can run `nmap --script ssl-enum-ciphers -p 443 example.com`. You can test each version with `openssl s_client -connect example.com:443 -tls1_1 -cipher 'DEFAULT@SECLEVEL=0'`. Or you can use the Qualys SSL Labs online test, which lists every supported protocol under Configuration.

Should I also disable TLS 1.2 and only allow TLS 1.3?

Not yet for a public website. TLS 1.2 with modern ECDHE/AEAD ciphers is still considered secure. Some corporate proxies, older devices and server-to-server clients don't support TLS 1.3. Allowing TLS 1.2 and 1.3 is the recommended baseline in Mozilla's Intermediate configuration.

Is disabling TLS 1.0 required for PCI DSS compliance?

Yes. PCI DSS has prohibited TLS 1.0 (and early TLS generally) as a security control since June 2018. Assessors and ASV scans flag servers that still accept it. TLS 1.1 is also widely flagged, so allowing only TLS 1.2 and 1.3 avoids scan failures.