How to Enable TLS 1.3 on Your Web Server, CDN or Host
Your HTTPS site still negotiates TLS 1.2 because the server, load balancer or CDN that terminates TLS does not offer TLS 1.3. By the end of this guide you will have found where TLS terminates, turned on TLS 1.3 with TLS 1.2 kept as a fallback, and confirmed that a TLS 1.3 handshake succeeds.

Why it matters
TLS 1.3 completes the handshake in one round trip instead of two, which cuts connection setup time, especially on mobile and high-latency networks, and it supports 0-RTT resumption. It also drops legacy features such as RSA key exchange, CBC ciphers and SHA-1, so weak configurations are no longer possible. Search engines do not rank on it directly, but faster first connections help Core Web Vitals like TTFB and LCP, and security scanners and enterprise buyers increasingly flag TLS 1.2-only servers.
What you need
Step-by-step fix
Find where TLS is terminated
TLS 1.3 must be enabled on whichever system visitors' browsers actually connect to. If you use a CDN or reverse proxy (Cloudflare, CloudFront, Fastly) or a cloud load balancer, that is where you change the setting, not on your origin server. Check the response headers to identify it.
server: cloudflareor acf-rayheader means Cloudflarex-amz-cf-idorvia: ... CloudFrontmeans CloudFrontserver: nginxorApacheusually means your own server
curl -sI https://example.com | grep -iE 'server|via|cf-ray|x-amz-cf-id|x-served-by'
Check your server and OpenSSL versions
TLS 1.3 needs OpenSSL 1.1.1 or newer, plus Nginx 1.13.0+ or Apache 2.4.37+. If the server software was compiled against an older OpenSSL, the directive is accepted but TLS 1.3 is silently not offered. Run the commands below and look for built with OpenSSL 1.1.1 or 3.x in the Nginx output.
openssl version nginx -V 2>&1 | grep -i openssl apachectl -v
Enable TLS 1.3 in Nginx
conf (http block) or in your site file under /etc/nginx/sites-available/. 1. Setting ssl_prefer_server_ciphers off` lets modern clients pick their fastest cipher.
Test the config, then reload.
# /etc/nginx/nginx.conf, inside http { }
ssl_protocols TLSv1.2 TLSv1.3;
ssl_prefer_server_ciphers off;
# then run:
# sudo nginx -t && sudo systemctl reload nginxEnable TLS 1.3 in Apache
Edit SSLProtocol in /etc/apache2/mods-available/ssl.conf (Debian/Ubuntu) or /etc/httpd/conf.d/ssl.conf (RHEL family), and in any <VirtualHost *:443> blocks that override it. Then check syntax and reload.
SSLProtocol -all +TLSv1.2 +TLSv1.3 SSLHonorCipherOrder off # then run: # sudo apachectl configtest && sudo systemctl reload apache2 (or httpd)
Turn on TLS 1.3 at your CDN or load balancer
If a CDN or load balancer sits in front, change it there.
- Cloudflare: SSL/TLS > Edge Certificates > TLS 1.3 = On. Set Minimum TLS Version to 1.2.
- AWS CloudFront: Distribution > General > Edit > Security policy
TLSv1.2_2021(TLS 1.3 is offered automatically). - AWS ALB/NLB: Listener > Edit > Security policy
ELBSecurityPolicy-TLS13-1-2-2021-06or newer. - Google Cloud Load Balancing: attach an SSL policy with profile MODERN and minimum TLS 1.2.
- Azure Front Door / App Gateway: choose a TLS policy that includes TLS 1.3.
Verify the TLS 1.3 handshake
Force a TLS 1.3 connection from your terminal. A success prints Protocol : TLSv1.3 (or New, TLSv1.3) along with a cipher such as TLS_AES_256_GCM_SHA384. Also confirm TLS 1.2 still works so older clients are not locked out, then re-run the audit.
openssl s_client -connect example.com:443 -servername example.com -tls1_3 </dev/null 2>/dev/null | grep -E 'Protocol|Cipher' # fallback check openssl s_client -connect example.com:443 -servername example.com -tls1_2 </dev/null 2>/dev/null | grep -E 'Protocol|Cipher' # or with curl curl -sv --tlsv1.3 --tls-max 1.3 https://example.com -o /dev/null 2>&1 | grep 'SSL connection'
Platform-specific notes
WordPress
WordPress itself has no TLS setting. On managed hosts (WP Engine, Kinsta, SiteGround and similar) TLS 1.3 is usually already on; if not, ask support or check the host's SSL panel. On a VPS, edit Nginx or Apache as shown. In cPanel, TLS protocols are set by the server admin in WHM > Service Configuration > Apache Configuration > Global Configuration (SSL/TLS Protocols).
Shopify
Shopify terminates TLS on its own edge and supports TLS 1.3 on all storefronts and custom domains; there is nothing to configure. If the audit warns, your domain is likely proxied through another service such as Cloudflare, so enable TLS 1.3 there.
Next.js (Vercel, Netlify)
Vercel and Netlify offer TLS 1.3 by default on all domains with no setting to change. If you self-host Next.js with `next start`, TLS is handled by the proxy in front (Nginx, Caddy, a load balancer), so configure TLS 1.3 there; Caddy enables it by default.
Cloudflare
TLS 1.3 is on by default for new zones but can be turned off. Check SSL/TLS > Edge Certificates > TLS 1.3. The 'On' setting enables TLS 1.3 with 0-RTT available separately under Speed > Optimization > Protocol Optimization.
Windows Server / IIS
TLS 1.3 requires Windows Server 2022 or later, where it is enabled by default for HTTP.sys and IIS. Windows Server 2019 and older cannot offer TLS 1.3, so you need an OS upgrade or a CDN in front.
Check that it worked
✅ How to verify
- Run `openssl s_client -connect example.com:443 -servername example.com -tls1_3` and confirm it prints Protocol TLSv1.3 instead of an alert.
- Open the site in Chrome, press F12 > Security tab, and check that Connection shows TLS 1.3.
- Run a scan at an SSL testing service such as SSL Labs and confirm the Configuration > Protocols section lists TLS 1.3: Yes.
- Re-run the audit; the check should report that TLS 1.3 is supported.
⚠️ Common mistakes
- Editing the origin server's config while a CDN or load balancer terminates TLS, so visitors never see the change.
- Setting ssl_protocols in one Nginx server block while the default server on the same IP:port still says TLSv1.2 only.
- Running Nginx or Apache built against OpenSSL 1.0.x, where the TLSv1.3 directive is ignored or rejected.
- Removing TLS 1.2 entirely when adding TLS 1.3, which breaks older Android devices, some bots and payment or API integrations.
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 freeFAQ
Should I disable TLS 1.2 after enabling TLS 1.3?
No. Keep TLS 1.2 enabled as the minimum. A small but real share of clients, crawlers and server-to-server integrations still lack TLS 1.3, and TLS 1.2 with modern ciphers is still considered secure. Disable TLS 1.0 and 1.1 instead.
Does TLS 1.3 improve SEO?
Not as a direct ranking factor. It shortens the handshake by one round trip, which lowers time to first byte on new connections and can help page speed metrics, and it removes weak cryptography that security scanners flag.
How do I check which TLS version my site uses?
In Chrome open DevTools > Security and read the Connection line, or run `openssl s_client -connect example.com:443 -tls1_3` in a terminal. If the TLS 1.3 handshake fails with a protocol version alert, the server only offers TLS 1.2 or lower.
Is 0-RTT safe to enable with TLS 1.3?
0-RTT early data can be replayed, so only enable it if your application treats repeated GET requests safely and never accepts state-changing requests as early data. It is optional; TLS 1.3 itself passes this check without 0-RTT.
How to Fix a Low TLS Security Grade (Protocols, HSTS, Certs)
How to Disable TLS 1.0 and 1.1 and Allow Only TLS 1.2+
How to Fix Cookies Missing the Secure Flag on HTTPS
How to Add Subresource Integrity (SRI) to CDN Scripts
How to Fix Cookies Missing the HttpOnly Flag on Your Site
How to Fix Server Version Disclosure in HTTP Headers