TLS and HTTPS hygiene
- Enforce HTTPS everywhere; redirect HTTP → HTTPS.
- Enable HSTS with a sensible max-age and consider preload.
- Disable TLS 1.0 and 1.1; prefer TLS 1.3.
- Renew certificates well before expiry.
A no-nonsense checklist of website security improvements that actually move the needle — TLS, headers, DNS hygiene, blacklist monitoring, and continuous verification.
Strict-Transport-Security — force HTTPS.Content-Security-Policy — block unexpected scripts.X-Content-Type-Options: nosniff.Referrer-Policy: strict-origin-when-cross-origin.Permissions-Policy — restrict browser features.CAA records prevent unauthorized certs. SPF, DKIM, and DMARC stop spoofing of your domain. DNSSEC protects against cache poisoning. These are cheap, high-leverage wins most sites skip.
Security isn't a checkbox. Monitor SSL expiry, blacklist status, header drift, and DNS changes. Drift detection catches the 1% of changes that quietly weaken your posture.
Run through these steps in order. Each step links to the right diagnostic tool.
Enforce HTTPS everywhere with HSTS and modern TLS versions, then add strict security headers. Most sites still get this wrong.
Helpful but not mandatory. Start with platform updates, MFA, secrets rotation, and proper DNS hygiene. Add a WAF when you have value worth attacking.
Run an HTTP headers check. You want HSTS, CSP, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy at minimum.
Set CAA records to control who can issue certs, configure SPF/DKIM/DMARC for email, and consider DNSSEC if your registrar supports it.
Monitor it continuously
Save this check, get alerts on changes, and track multiple domains in one dashboard.