A pre-launch SSL checklist catches the issues that otherwise surface as live incidents in front of real visitors.
The checklist
- Certificate covers the exact domain and subdomains in use (including
wwwif both are served) - Full certificate chain is served, not just the leaf certificate (test from more than one device/browser)
- HTTP automatically redirects to HTTPS site-wide, with no mixed content warnings on any page
- Auto-renewal is configured and tested at least once before relying on it
- TLS 1.0/1.1 disabled; 1.2 and 1.3 enabled
- An independent uptime/SSL monitor is watching expiry, separate from whatever renews it
FAQ
Should I test the renewal process before go-live?
Yes — a dry-run or forced renewal test before launch is the cheapest way to catch a broken automation script before it matters.