Blog / Web management /
A practical SSL renewal check for a business owner
The website still opens, so the SSL renewal reminder gets pushed down the list. Does the host handle it? The domain provider? Whoever built the site years ago? Nobody knows. “Automatic renewal” has become an assumption with no owner.
I like a check that a business owner can follow and a technical maintainer can act on. Confirm which public addresses need certificates, who manages renewal and what proves the deployed certificate is current. A payment receipt or an enabled setting doesn’t prove what visitors actually get.
List the public hostnames
Record the preferred website address and important alternatives or subdomains. Include customer-facing services that the business expects to remain available, such as a support or booking route where relevant.
One certificate doesn’t necessarily cover every hostname just because they share a domain. Get the technical person to verify the actual coverage.
Keep the list tied to services the business owns and uses. A collection of abandoned subdomains can create noise, but removing one needs a deliberate decision about its users and dependencies.
Identify the renewal owner
Ask who provisions the certificate and what system performs renewal. A hosted platform, managed service or separately configured process can have different responsibilities.
Record the business and technical contacts. I always ask whether access depends on a contractor who has since left. Keep credentials in the approved secure system rather than adding them to the renewal reminder.
Clarify billing where applicable. Domain renewal, hosting renewal and certificate renewal are separate arrangements even if one provider sends messages about all three. Paying one bill is not proof the others are complete.
Inspect the deployed certificate
Have the maintainer check the certificate currently presented at the public address, including hostname coverage and validity. The useful evidence concerns what visitors receive, not merely a certificate file stored in an account.
Review the relevant connection path where a proxy or CDN is involved. The public connection and the origin connection may use different configuration, and both need the intended supported arrangement.
Never click past a browser warning to make a test look successful. Investigate the mismatch with the technical owner. A reassuring internal note isn’t a working public connection.
Check the renewal mechanism
Confirm the process can perform its required validation and deployment steps. DNS changes, access changes or an altered hosting arrangement can affect a previously working automatic setup.
Ask where failures are reported and who reads them. An automated renewal with nobody watching can stay broken quietly until the certificate expires.
Keep the check aligned with the provider’s actual instructions. Certificate lifetimes and platform processes can change, so avoid relying on a fixed remembered renewal interval as the whole plan.
Test the website beyond the homepage
Open important public routes and follow relevant redirects. An alternative hostname contacted before a redirect still needs appropriate certificate handling for that initial connection.
Check forms, embedded resources and other consequential services where the renewal or hosting configuration affects them. A homepage loading does not establish that every customer-facing dependency works.
Look for mixed-content or resource-loading symptoms with the technical maintainer where relevant. Keep the observation precise: address, time, visible message and affected action help narrow the investigation.
Give failure a clear response route
Record who can act if renewal fails and how the issue is escalated. The business owner should know the first contact and where the configuration reference lives without needing to diagnose cryptographic details.
If a certificate problem interrupts service, communicate verified status and avoid guessed recovery times. The technical team needs room to establish the cause and appropriate correction.
After recovery, verify the deployed public state and the renewal mechanism. Replacing one certificate may restore the site while leaving the process that caused the interruption unresolved.
Keep a concise renewal record
Save the hostname list, renewal arrangement, alert owner and last verification result. Use review triggers such as a provider move, DNS change or ownership transfer as well as the normal maintenance schedule.
Retire obsolete reminders only after the associated service is deliberately closed or transferred. Otherwise, a useful warning can disappear because nobody recognises its original purpose.
Verify that alerts reach a person who can act
A renewal can be set up perfectly while its alerts go to an abandoned mailbox. Confirm where they land and who escalates, especially after a staff or provider change. Ask the maintainer what a failed renewal looks like and where to check its status.
Treat renewal emails with care, too. If one asks for payment, use the account and contact route you already know. Don’t trust an unfamiliar link just because it mentions your domain. And if you moved addresses recently, remember the old hostname still needs a valid HTTPS connection for its redirect.
The outcome you want is a certificate responsibility the business can explain and monitor, not a hopeful assumption that the provider probably has it covered.
Related reading
- DNS and SSL checks to complete before a domain move
- What belongs in a website change record
- A calm process for triaging plugin and app conflicts
Pick the hostname your customers rely on most. Can you say who renews its certificate, who receives a failure alert and what public check shows it’s working?