HTTPS and your TLS certificate
Make sure every visitor gets an encrypted connection with a certificate browsers trust, that does not expire, using TLS 1.2 or newer.
What it is
HTTPS encrypts the connection between a visitor and your site. The certificate proves the site is really yours. Browsers reject certificates that are expired, issued for a different name, or self-signed.
Why it matters
Without valid HTTPS, anyone on the same network can read or change what visitors send and receive, and browsers show a full-page warning that drives people away.
How to fix it
sudo certbot --nginx -d example.com -d www.example.com # renewal runs automatically; test it with: sudo certbot renew --dry-run
ssl_protocols TLSv1.2 TLSv1.3;
SSLProtocol -all +TLSv1.2 +TLSv1.3
SSL/TLS > Overview: Full (strict) SSL/TLS > Edge Certificates > Minimum TLS Version: 1.2
Most hosting platforms (Vercel, Netlify, Railway, Render) issue and renew certificates for you once your domain points at them.
Does your site have this problem?
Kompile Scan checks for this and the other problems in these guides in under a minute. Free for one site.