HTTPS is more than a padlock in the browser: it depends on a valid certificate, correct DNS and hosting configuration, consistent redirects, and ongoing renewal checks. This SSL certificate checklist explains how to install SSL, force HTTPS, verify certificate coverage, prevent renewal failures, and troubleshoot browser warnings or mixed content before they affect visitors.
Overview
An SSL certificate enables encrypted communication between a visitor’s browser and your website. In practice, most modern sites use TLS, but “SSL certificate” remains the familiar term used by hosting panels, registrars, and search documentation. HTTPS setup for a website is complete only when the certificate is valid, the correct domain names are covered, the server presents the certificate correctly, and every important page loads securely.
Certificate installation is usually handled in one of three ways:
- Automatic hosting certificate: Your hosting provider issues and installs a certificate through the control panel. This is often the simplest option for standard websites.
- Managed certificate: A hosting platform or CDN manages issuance, installation, and renewal on your behalf.
- Manual certificate: You obtain certificate files and install them on a server, VPS, reverse proxy, or load balancer. This provides more control but requires careful configuration.
The certificate type should match the site’s needs. Domain validation is commonly sufficient when the goal is to prove control of a domain. Organization-oriented certificates may involve additional identity checks, while wildcard certificates can cover a domain and eligible subdomains. The exact options, validation methods, and validity periods can change, so confirm current details with the certificate authority or hosting provider before purchase or deployment.
| Certificate approach | Useful for | Key consideration |
|---|---|---|
| Single-domain | One primary hostname | Check whether both the root domain and www version are covered. |
| Multi-domain | Several specified hostnames | Maintain an accurate list as domains and services change. |
| Wildcard | Multiple subdomains under one domain | Confirm that the certificate scope matches the subdomain structure. |
| Managed certificate | Sites that prioritize automated deployment | Verify who controls validation, renewal, and failure alerts. |
What to track
1. Certificate coverage and expiration
Record the certificate’s expiration date, covered names, issuing service, and installation location. Check the exact hostname that visitors use, not only the origin server. A certificate for example.com may not automatically cover every possible subdomain, and a certificate for www.example.com may not cover the bare domain unless it is included.
Track every public endpoint, including staging environments that are accessible from the internet, customer portals, application subdomains, APIs, and mail-related web services. A certificate can be valid on the homepage while another important hostname remains expired or misconfigured.
2. Renewal and validation status
Automatic renewal reduces manual work, but it is not a reason to stop monitoring. Renewal can fail when DNS records change, validation files are blocked, a domain is moved between providers, an account loses permission, or a reverse proxy serves the wrong response. Keep a record of the renewal method and the person or system responsible for receiving alerts.
For DNS-based validation, document the required TXT or CNAME record and who can edit it. For HTTP-based validation, check that the validation path remains reachable and is not redirected or blocked by access rules. Never assume that a recent hosting migration preserved the renewal configuration.
3. Redirects, mixed content, and canonical URLs
HTTPS should be the consistent public version of the site. Test HTTP-to-HTTPS redirects, page links, image URLs, scripts, stylesheets, forms, canonical tags, sitemap URLs, and robots directives. Mixed content occurs when an HTTPS page requests a resource over HTTP. Browsers may block active content or show warnings for insecure resources, which can break menus, forms, analytics, or payment flows.
Also verify that redirects do not create loops between the web server, CDN, and application. If the application does not recognize that the original visitor used HTTPS behind a proxy, it may repeatedly redirect an already secure request.
4. Domain and DNS dependencies
Certificate validation and website delivery depend on DNS being correct. Track A, AAAA, CNAME, and relevant validation records, along with nameserver ownership. If you recently changed how to point a domain to web hosting, compare the DNS records before and after the change. A DNS propagation checker can help identify whether different resolvers are receiving different answers, but it does not replace testing the live certificate from the affected hostname.
Keep HTTPS monitoring separate from email DNS monitoring. Changes to web records should not unintentionally remove MX, SPF, DKIM, or DMARC records. For related email checks, see the SPF, DKIM, and DMARC setup guide.
Cadence and checkpoints
Use the following SSL certificate renewal checklist as a recurring maintenance routine:
- After installation: Open each public hostname in a current browser, inspect the certificate details, and confirm that the expected names and expiration date appear.
- After DNS or hosting changes: Test the site from the root domain, www hostname, important subdomains, and any separate application endpoint. Confirm that the new server presents the intended certificate.
- Monthly: Review certificate expiration dates, renewal logs, monitoring alerts, DNS validation records, and redirect behavior. Check at least one representative page for mixed content.
- Before renewal: Confirm that the renewal account is active, DNS or HTTP validation still works, and the responsible administrator can access alerts. Use the provider’s current renewal window rather than relying on a fixed number of days.
- After renewal: Recheck the live certificate from outside the hosting control panel. A successful renewal job does not prove that every load balancer, CDN, or origin server is serving the new certificate.
- Quarterly: Review the inventory. Remove obsolete certificates and unused hostnames, verify ownership of DNS accounts, and document any manual steps that could delay recovery.
Pair this routine with a broader hosting performance audit and confirm that a recent website backup can be restored. HTTPS protects connections, but it does not replace backups, access controls, software updates, or monitoring.
How to interpret changes
Browser says the certificate is expired
Check the server’s current date and time, then inspect the certificate actually delivered by the affected hostname. If the certificate has expired, determine whether automatic renewal failed or whether the renewed certificate was installed on only one server. Renew or reinstall it, restart the relevant service if required, and retest through every delivery layer.
Browser says the certificate is not trusted
Confirm that the certificate was issued by a recognized authority and that the server is sending the required certificate chain. This problem can occur after a manual installation that includes the site certificate but omits an intermediate certificate. Ask the hosting provider or certificate authority for the correct bundle rather than assembling files from memory.
Certificate name mismatch
A name mismatch means the requested hostname is not covered by the certificate being served. Check whether visitors are using the bare domain, www version, a subdomain, or an alternate spelling. Install a certificate with the required names or redirect the hostname only after confirming that the redirect itself is reachable.
Mixed content warning
Find the insecure URL in the browser’s developer tools or security panel. Update hard-coded HTTP links in templates, content, CSS, JavaScript, plugins, and embedded services. If an external resource has no HTTPS version, replace it, remove it, or assess the security and functionality implications before allowing it.
Renewal repeatedly fails
Review the validation method, DNS history, firewall rules, redirects, permissions, and recent migrations. Check whether a CDN or proxy is masking the origin response. Preserve the error message and timestamp so the hosting provider or certificate authority can diagnose the specific failure. Avoid deleting working certificate files until a replacement has been validated.
When to revisit
Revisit this checklist monthly or quarterly, before every expected certificate renewal, and immediately after a domain transfer, nameserver change, hosting migration, CDN change, server rebuild, or DNS management update. Also review it when launching a new subdomain, changing the site’s canonical hostname, adding an application or API, or receiving a browser security warning.
For a practical final check, maintain a small inventory containing each hostname, certificate type, expiration date, renewal method, DNS validation owner, hosting location, and alert recipient. Open the main site and important subdomains in a private browser window, confirm HTTPS redirects, inspect certificate coverage, test a form, scan for mixed content, and check that email DNS records remain intact. If a domain is approaching renewal, coordinate this review with the domain renewal checklist so domain expiration and certificate expiration are not treated as separate risks.
HTTPS maintenance is reliable when it is treated as an ongoing operational task rather than a one-time installation. A short recurring review can reveal expired certificates, missing hostnames, broken validation records, and insecure page resources before visitors encounter them.