How to Fix a Low TLS Security Grade (Protocols, HSTS, Certs)
A TLS security grade summarises how safely your site encrypts traffic. It drops when the server still accepts TLS 1.0 or 1.1, sends no Strict-Transport-Security (HSTS) header, or presents a certificate that is expired, incomplete or issued for the wrong hostname. By the end of this guide you will have fixed each listed reason and confirmed an A grade.

Why it matters
1 and on broken certificates, so visitors on a misconfigured site see interstitial warnings and leave. Crawlers, including the bots that collect pages for AI answers, can fail the TLS handshake and skip the page entirely. Without HSTS, the first request a visitor makes can be downgraded to plain HTTP and intercepted on public Wi-Fi.
Payment providers, enterprise buyers and security questionnaires also treat anything below an A as a red flag.
What you need
Step-by-step fix
Note every reason listed next to your grade
Open the audit result and copy the reasons after the grade letter. Each one maps to a fix below:
- Old protocols (TLS 1.0/1.1, SSLv3): step 3
- Certificate problems (expired, hostname mismatch, missing intermediate, self-signed): step 2
- Missing HSTS: step 5
A grade starting with A passes, B is a warning, and anything lower fails. Also find out where TLS actually terminates: your origin server, a load balancer, or a CDN like Cloudflare. You must change the settings at that layer.
curl -sI https://example.com | grep -iE 'server|cf-ray|x-vercel|strict-transport'
Fix the certificate and serve the full chain
The certificate must be unexpired, cover every hostname you serve (both example.com and www.example.com), and be sent together with its intermediate certificates. The most common mistake on Nginx is pointing ssl_certificate at cert.pem instead of fullchain.pem, which breaks validation on Android and in many crawlers. With Let's Encrypt, request one certificate that names both hosts and confirm automatic renewal works.
sudo certbot certonly --nginx -d example.com -d www.example.com # nginx server block ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # confirm auto-renewal sudo certbot renew --dry-run
Disable TLS 1.0/1.1 and enable TLS 1.3
3. conf. Remove any older ssl_protocols line in included files, because a duplicate in another file can override yours.
conf.
# Nginx ssl_protocols TLSv1.2 TLSv1.3; ssl_prefer_server_ciphers off; # Apache (mod_ssl) SSLProtocol -all +TLSv1.2 +TLSv1.3 SSLHonorCipherOrder off
Use a modern cipher list
Weak ciphers such as RC4, 3DES and non-forward-secret RSA key exchange can cap your grade even after old protocols are off. Use the Mozilla SSL Configuration Generator's Intermediate profile (ssl-config.mozilla.org), which supports every browser from the last several years. TLS 1.3 ciphers are configured automatically, so this list only affects TLS 1.2.
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305; ssl_session_cache shared:SSL:10m; ssl_session_tickets off;
Add the HSTS header and force HTTPS
HSTS tells browsers to use HTTPS only for your domain. It is only honoured when sent over HTTPS, so also redirect all HTTP traffic with a 301. Start with a short max-age (for example 300) to make sure nothing breaks, then raise it to 31536000 (one year).
Only add includeSubDomains once every subdomain works over HTTPS.
# Nginx: port 80 server block return 301 https://$host$request_uri; # Nginx: port 443 server block add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always; # Apache (requires mod_headers) Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"
Test the config and reload the server
Validate the syntax before reloading so a typo doesn't take the site down. A reload applies the change without dropping existing connections.
# Nginx sudo nginx -t && sudo systemctl reload nginx # Apache sudo apachectl configtest && sudo systemctl reload apache2
Verify the protocols, header and grade
Confirm that TLS 1.1 is refused, TLS 1.3 is accepted and the HSTS header is present. Then run a scan at ssllabs.com/ssltest and re-run the audit. The grade should start with A, with no reasons listed.
openssl s_client -connect example.com:443 -servername example.com -tls1_1 </dev/null # should fail openssl s_client -connect example.com:443 -servername example.com -tls1_3 </dev/null # should connect curl -sI https://example.com | grep -i strict-transport-security
Platform-specific notes
Cloudflare
Visitors' TLS ends at Cloudflare. In the dashboard, open SSL/TLS > Edge Certificates and set **Minimum TLS Version** to TLS 1.2, turn on TLS 1.3 and Always Use HTTPS, then enable HSTS under HTTP Strict Transport Security (HSTS). Under SSL/TLS > Overview, choose **Full (strict)** and install a valid certificate on the origin (a free Cloudflare Origin CA certificate works).
WordPress
TLS is set by your host, not WordPress. On managed hosts (WP Engine, Kinsta, SiteGround), protocols and certificates are controlled in the host panel or by support. For HSTS on Apache hosts, add the Header line to .htaccess, or use your security plugin's HSTS option. Set both WordPress Address and Site Address to https:// under Settings > General.
Shopify
Shopify manages certificates, protocols and HSTS for storefronts, so you can't edit them. A low grade usually means a domain isn't pointing correctly: in Settings > Domains, check that each domain shows SSL as active. Make sure the A record points to Shopify's IP and www has a CNAME to shops.myshopify.com, then wait for the certificate to be issued.
Next.js / Vercel
Vercel issues certificates automatically and only allows TLS 1.2+ with TLS 1.3. If HSTS is missing, add it via headers() in next.config.js: source '/:path*', key 'Strict-Transport-Security', value 'max-age=31536000; includeSubDomains'. Self-hosted Next.js behind Nginx or a load balancer needs the protocol fixes applied at that proxy.
AWS (CloudFront / ALB)
For CloudFront, choose the security policy TLSv1.2_2021 or newer under the distribution's Settings, and add HSTS with a Response Headers Policy. For an Application Load Balancer, set the HTTPS listener to a policy such as ELBSecurityPolicy-TLS13-1-2-2021-06.
Check that it worked
✅ How to verify
- Re-run the audit: the result should read 'Grade A — modern protocols, valid certificate and HSTS.'
- Run ssllabs.com/ssltest for example.com and www.example.com and confirm both score A or A+ with no chain issues.
- Run curl -sI https://example.com and confirm the Strict-Transport-Security header appears with max-age of at least 31536000.
- Run testssl.sh example.com and confirm TLS 1.0 and 1.1 are reported as 'not offered'.
⚠️ Common mistakes
- Changing the origin server while Cloudflare or another CDN terminates TLS, so the public grade never changes.
- Using cert.pem instead of fullchain.pem, which causes 'chain incomplete' errors that desktop Chrome hides but crawlers and mobile clients hit.
- Adding HSTS with includeSubDomains or preload before every subdomain supports HTTPS, which locks users out of internal or legacy subdomains.
- Leaving an old ssl_protocols line in another included Nginx file, which silently re-enables TLS 1.0/1.1.
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
Will disabling TLS 1.0 and 1.1 block any real visitors?
Practically none. All current browsers dropped TLS 1.0/1.1 in 2020. Only very old devices, such as Android 4.3 and earlier or Windows 7 with old IE, rely on them, and those clients already fail on most of the web.
What is the difference between an A and an A+ grade?
Both pass. A+ usually also requires a long-lived HSTS header (six months or more) and no other warnings. An A without HSTS is rare, because missing HSTS is one of the reasons that lowers the grade.
Should I submit my domain to the HSTS preload list?
Only if you are sure every subdomain will be HTTPS-only for good. Preloading needs max-age of at least 31536000, includeSubDomains and the preload token, and removal from browsers takes months. It isn't required for an A grade.
Does the TLS grade affect Google rankings?
HTTPS is a lightweight ranking signal. A certificate error or failed handshake has a bigger effect: Googlebot can't fetch the page, and visitors see a browser warning. Fixing the grade removes those crawl and trust failures.
How to Fix Cookies Missing the Secure Flag on HTTPS
How to Enable TLS 1.3 on Your Web Server, CDN or Host
How to Fix Cookies Missing the HttpOnly Flag on Your Site
How to Disable TLS 1.0 and 1.1 and Allow Only TLS 1.2+
How to Fix Cookies Missing the SameSite Attribute
How to Add Subresource Integrity (SRI) to CDN Scripts