To check your HTTPS configuration, scan the hostname with an external tool (SSL Labs, testssl.sh, or a free TLS/SSL check) and read five results: protocol versions, cipher suites, certificate chain and expiry, HSTS, and mixed content. To fix it, paste the Mozilla intermediate profile for your web server, disable TLS 1.0 and 1.1, enable TLS 1.3, and add a Strict-Transport-Security header. Most sites move from a mediocre grade to a clean one with a single configuration block and a server reload.
Why this matters for your website
A padlock in the address bar is not a security verdict. It tells the visitor that the connection is encrypted and that the certificate matches the name they typed. It says nothing about the strength of the encryption, whether an attacker can force a downgrade, or whether half your page is still loading over plain HTTP.
Weak TLS has commercial consequences. Payment providers and enterprise buyers ask for evidence that TLS 1.0/1.1 are off. An expired certificate produces a full-page browser interstitial that stops checkout. Mixed content silently breaks scripts and leaks page contents on hostile networks.
What a certificate proves, and what it does not
A publicly trusted certificate proves two things: control of the domain name at issuance time, and possession of the matching private key. Domain-validated certificates, including free ones, prove nothing about the company behind the site.
- It does prove: the hostname is the one you connected to, and traffic is encrypted in transit.
- It does not prove: the site is safe, the operator is legitimate, or the server is patched.
- It does not configure: which TLS versions or ciphers your server accepts — that is your server config, not the certificate.
The five things a TLS audit checks
Every credible TLS security check, manual or automated, covers the same five areas. The OWASP Transport Layer Security Cheat Sheet is the reference to keep open while you work.
1. Protocol versions
Accept only TLS 1.2 and TLS 1.3. SSL 3.0, TLS 1.0 and TLS 1.1 are deprecated by RFC 8996 and should be switched off. TLS 1.3 removes the legacy key exchanges outright and shortens the handshake, so enable it wherever your server version supports it.
2. Cipher suites and forward secrecy
Prefer ECDHE key exchange with AES-GCM or ChaCha20-Poly1305. Forward secrecy means that a stolen private key cannot decrypt traffic captured last year. Remove RC4, 3DES, anything labelled EXPORT or NULL, and static RSA key exchange.
3. Certificate chain and expiry
Serve the leaf certificate plus every intermediate, in order. A missing intermediate works in desktop Chrome and fails on older Android and API clients, which is why the bug is so often reported late. Track expiry with monitoring, not memory.
4. HSTS
The HSTS header tells browsers to use HTTPS for your domain for a fixed period, blocking downgrade and cookie-stealing attacks on the first redirect. Start with a short max-age, confirm nothing breaks, then raise it. Only add preload once every subdomain serves HTTPS.
5. Mixed content
Mixed content is an HTTPS page pulling images, scripts or stylesheets over HTTP. Browsers block active mixed content and downgrade the padlock. In WordPress, the usual causes are hard-coded http:// URLs in the database, a theme option, or a plugin CDN setting.
Copy-paste configuration that fixes most of it
Generate your exact block with the Mozilla SSL Configuration Generator, choosing the intermediate profile and your real server and OpenSSL versions. Intermediate supports all modern browsers; use modern only if you control every client. The snippets below follow that profile.
# nginx — inside the server block listening on 443
ssl_protocols TLSv1.2 TLSv1.3;
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_prefer_server_ciphers off;
ssl_session_cache shared:SSL:10m;
ssl_session_tickets off;
ssl_stapling on;
ssl_stapling_verify on;
add_header Strict-Transport-Security "max-age=63072000" always;# Apache — inside the VirtualHost on port 443
SSLProtocol -all +TLSv1.2 +TLSv1.3
SSLCipherSuite ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384
SSLHonorCipherOrder off
SSLSessionTickets off
Header always set Strict-Transport-Security "max-age=63072000"Test the syntax (nginx -t or apachectl configtest), then reload. If you use Let's Encrypt, certificates last 90 days and renew automatically through the certbot timer; verify it with certbot renew --dry-run and add a deploy hook that reloads the web server, as described in the Let's Encrypt documentation. A renewal that never reloads nginx is the most common cause of a surprise expiry.
Reading an SSL Labs grade and testssl.sh output
Qualys SSL Labs scores a public hostname from A+ to F and explains each deduction. Read the grade as a summary of caps, not a score you tune.
- A+ requires a valid chain, modern protocols and a long-lived HSTS header.
- Caps below A are typically triggered by legacy protocol support or weak cipher suites.
- T or F means trust is broken — name mismatch, expired or self-signed certificate, or a known vulnerable configuration. Fix these first.
For internal hosts, mail servers or anything not reachable from the internet, run testssl.sh locally: ./testssl.sh https://example.com. Scan the output for lines marked NOT ok and for the protocol table showing offered next to TLS 1.0 or 1.1. The vulnerability section names issues directly, so you can search each one in the NVD before changing anything.
How to check your own site
Start with the free TLS/SSL check, which needs no account and previews the certificate, protocol and header findings for a hostname. Use it to confirm whether the configuration above actually took effect after a reload.
Scantinel (scantinel.ai) is an automated website security assessment platform that runs OSINT, network, and OWASP Top 10 web vulnerability tests against ownership-verified assets and delivers actionable, business-owner-legible reports. The Essential scan completes in minutes and its TLS audit flags weak protocols, deprecated ciphers, expiring certificates and a missing HSTS header, alongside a security-headers and cookie-flag review. It is an automated assessment, not a penetration test.
If you need coverage beyond the edge — origin-IP discovery, port and service fingerprinting with CVE correlation, and an active OWASP Top 10 scan — you can run a full TLS audit as part of the Full scan. For the wider context, see the website security guide.
Key takeaways
- A certificate proves domain control and encrypts traffic; it does not prove your server is configured well.
- Disable TLS 1.0 and 1.1, enable TLS 1.2 and 1.3, and keep only ECDHE suites with AES-GCM or ChaCha20.
- Generate your config from the Mozilla intermediate profile rather than copying blocks from forum posts.
- Verify that automatic renewal reloads the web server, and monitor expiry independently.
- Add HSTS with a short
max-agefirst, then raise it once every asset loads over HTTPS.
Frequently asked questions
Is TLS 1.2 still secure?
Yes, when it is configured with forward-secret ECDHE cipher suites and AEAD encryption such as AES-GCM. TLS 1.2 remains the compatibility baseline for most public sites, with TLS 1.3 preferred where clients support it. The risk lies in weak cipher suites left enabled alongside it, not in the protocol version itself.
How do I check my SSL certificate expiry date?
In a browser, click the padlock and open the certificate details. From a terminal, run echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -dates. Better still, put expiry on a monitor so you learn about it weeks ahead rather than from a customer.
Why does my site show not secure even with a certificate?
The three usual causes are mixed content, a missing intermediate certificate, and a name mismatch — for example a certificate issued for example.com served on www.example.com. Open the browser developer console and read the warnings; blocked or insecure resources are listed by URL. Fix the resource URLs or reissue the certificate with both names as subject alternative names.
Published February 2025 by the Scantinel Security Research Team. Verify current guidance against primary sources — OWASP, the NVD and WPScan — before making changes.
Comments
No comments yet.