What it means
TLS 1.3 is the current version of the protocol behind HTTPS. Our check offered it first, as every modern browser does, and your server chose an older version instead. TLS 1.2 still works, so nothing is broken.
Why it matters
TLS 1.3 connects in fewer round trips, so pages start loading sooner, especially on mobile networks. It also removes the older ciphers and key exchanges that caused most past TLS weaknesses, and it always provides forward secrecy. Every current browser supports it.
How to fix it
- Check that your server software is recent enough: nginx 1.13 or later, Apache 2.4.37 or later, both built with OpenSSL 1.1.1 or newer. Most systems released since 2019 qualify.
- Add TLS 1.3 to the allowed versions, keeping TLS 1.2 for older clients.
- Reload the web server, or save the setting in your CDN or load balancer.
nginx
ssl_protocols TLSv1.2 TLSv1.3; then sudo nginx -s reload.
Apache
SSLProtocol -all +TLSv1.2 +TLSv1.3 then reload Apache.
Cloudflare
Under SSL/TLS, Edge Certificates, turn on TLS 1.3. It is on by default for new zones.
Load balancers
Most cloud load balancers choose TLS versions through a named security policy. Pick a current policy that includes TLS 1.3.
Check it worked
Run the SSL check again. The connection line in each card should show TLS 1.3, and the version table should read "Accepted" for it.