An expired or incorrectly installed SSL certificate can turn a working website into a browser warning, failed API request, or lost customer visit. This reusable SSL certificate renewal guide shows how to check expiry, complete domain validation, install the renewed certificate, test the certificate chain, and troubleshoot HTTPS errors without making changes blindly.
Overview
SSL certificates enable HTTPS by allowing a browser to verify a website’s identity and establish an encrypted connection. The certificate is only one part of that process: the domain must resolve to the expected server, the certificate must cover the requested hostname, and the server must present a complete and trusted certificate chain.
Renewal normally involves four stages:
- Check: Confirm the certificate’s expiration date, covered hostnames, issuer, and installation location.
- Validate: Prove control of the domain through a DNS, HTTP, or account-based challenge.
- Install: Place the certificate, private key, and any required intermediate certificates on the correct web server or hosting platform.
- Test: Verify HTTPS for every important hostname, including redirects, subdomains, APIs, and administrative paths.
Before starting, record the current certificate details and take a backup of relevant configuration. If the site is managed through a cloud hosting dashboard or website builder, use that platform’s certificate workflow rather than manually replacing files that the platform controls. If DNS or nameserver changes are also required, review the Domain DNS Setup Guide first.
Certificate types at a glance
| Type | Typical coverage | Renewal considerations |
|---|---|---|
| Domain validation | One or more specified domain names | Requires proof of control; confirm every hostname that the site uses. |
| Organization validation | A domain plus additional organization checks | Keep organizational contact and validation details available for renewal. |
| Wildcard | A domain and its subdomains at one level, depending on the certificate scope | Check that the wildcard pattern actually covers each required subdomain. |
| Automated ACME certificate | Hostnames approved through an automated certificate workflow | Make sure scheduled renewal, challenge access, and deployment permissions still work. |
The right choice depends on the hostnames, validation method, hosting environment, and operational requirements. Do not assume that a certificate for example.com automatically covers www.example.com or other subdomains; inspect the certificate’s subject alternative names.
Checklist by scenario
Scenario 1: The certificate is approaching expiry
- Open the certificate details in the hosting panel, server configuration, or browser security information.
- Record the expiration date, issuer, covered names, and the server currently presenting the certificate.
- Check whether renewal is manual or automated. For automated certificates, inspect the last successful renewal and the next scheduled attempt.
- Confirm that DNS still points the hostname to the environment where renewal will run.
- Start renewal early enough to investigate validation or deployment failures before the existing certificate expires.
- After renewal, verify the live site rather than relying only on a success message in a dashboard.
Scenario 2: Domain validation fails
Certificate authorities commonly verify domain control through a DNS record, an HTTP file, or an approval workflow. Use the method shown by your certificate provider and check the following:
- DNS validation: Confirm the required TXT or CNAME record is at the correct name, has the exact value, and was added to the authoritative DNS provider. Avoid adding the full domain twice if the DNS interface automatically appends the zone name.
- HTTP validation: Confirm the challenge URL is publicly reachable over HTTP, returns the expected content, and is not blocked by authentication, a firewall, a redirect rule, or a deployment process.
- Multiple DNS providers: Check which nameservers are authoritative. Editing a record at a registrar or old host will not help if another provider serves the active zone.
- Proxying and caching: Temporarily review proxy, CDN, caching, or security rules if they alter the challenge response.
Do not delete unrelated DNS records while troubleshooting. Make one controlled change, allow for DNS propagation, and retry validation using the provider’s documented process.
Scenario 3: The certificate has been renewed but HTTPS still fails
- Check the certificate presented by the public hostname, not only the certificate file on disk.
- Confirm the certificate covers the exact hostname in the browser address bar.
- Verify that the web server or load balancer is using the new certificate and matching private key.
- Install the required intermediate certificates so clients can build a complete trust chain.
- Reload or restart the relevant service according to the hosting platform’s procedure.
- Test the root domain,
wwwversion, important subdomains, and API endpoints separately. - Check both IPv4 and IPv6 destinations if the domain publishes both address types.
A successful renewal does not necessarily mean successful deployment. The renewal system may have created a new certificate while the web server continues presenting an older one.
Scenario 4: You changed hosting or DNS
When migrating a website, certificate checks can reach different servers depending on DNS records, cached answers, load balancers, or IPv6 configuration. Complete the migration checklist, then issue or install the certificate on the new environment. Keep the old environment available until DNS, HTTPS, redirects, and application behavior have been tested. The shared hosting to managed cloud migration checklist can help organize that change.
What to double-check
- Hostname coverage: Review every name used by the website, including redirects, media hosts, staging environments, webhooks, and APIs.
- Private-key match: The renewed certificate must correspond to the private key used by the server. A mismatched key can cause installation or handshake errors.
- Certificate chain: Confirm that intermediate certificates are installed in the order expected by the server and hosting platform.
- TLS configuration: Use the hosting provider’s maintained TLS settings where possible. Avoid enabling obsolete protocols or weak cipher settings merely to accommodate an old client without understanding the security trade-off.
- Redirect behavior: Test HTTP-to-HTTPS redirects, canonical host redirects, and paths that use query parameters. Watch for redirect loops.
- Mixed content: HTTPS can still show warnings when a page loads images, scripts, stylesheets, or other resources over HTTP. Update hard-coded asset URLs and check third-party integrations.
- Monitoring: Add certificate-expiry monitoring and an uptime check. Monitoring should test the public endpoint, not just whether a server process is running. See the Website Uptime Monitoring Guide for a practical approach.
Common mistakes
- Waiting until the expiry date: A renewal that depends on DNS validation or a provider response needs time for investigation.
- Checking only one hostname: The main site may work while a subdomain, API, or
wwwalias still presents an expired certificate. - Editing the wrong DNS zone: Always identify the authoritative nameservers before changing validation records.
- Installing only the leaf certificate: Some clients will reject an incomplete chain even when desktop browsers appear to work.
- Replacing files without a rollback: Save the previous certificate configuration and document how to restore it.
- Testing from only one network: Compare normal browsing with an external check when DNS, CDN, or IPv6 behavior may differ.
- Ignoring email infrastructure: Website HTTPS and domain email authentication are separate systems. For mail-related DNS records, consult the SPF, DKIM, and DMARC Setup Guide.
When to revisit
Use this checklist before every planned certificate renewal and whenever the underlying environment changes. Revisit it immediately after moving hosts, changing nameservers, adding a subdomain, replacing a load balancer, enabling a CDN, changing firewall rules, or receiving a browser certificate warning.
Review automated renewal after any change to DNS permissions, server access, deployment pipelines, or hosting accounts. A monthly or quarterly operational check can confirm that expiry monitoring is active, renewal logs show recent success, and the public site presents the expected certificate. Refresh internal instructions when your hosting panel, certificate provider, validation method, or TLS configuration workflow changes.
For a safe renewal, use this final sequence: inspect the current certificate, back up configuration, validate domain control, renew, install, reload, test every hostname, confirm monitoring, and record the result. If a deployment causes an outage, follow a documented rollback plan rather than making several untracked changes at once. The Website Deployment Rollback Plan provides a useful structure for that response.