SSL Certificate Inventory: Mapping Every Hostname Before It Expires at GhostHosts

GhostHosts editorial ·

rack OE16 at the "esams" data center in Haarlem near Amsterdam, part of toolserver operated by Wikimedia Deutschland. November 2011. Imported from wikitech. http://wikitech.wikimedia.org/view/OE16 (own work)
Illustrative image. Mutante · CC BY-SA 3.0 · Cropped and resized. Image source

Teams that run websites on GhostHosts, or on any other hosting service, often discover certificate problems at the worst possible moment: a browser warning on a checkout page, a login form that fails for mobile visitors, or a forgotten subdomain that quietly stopped serving valid HTTPS. The fix is rarely dramatic. It is an inventory. Before you can keep certificates healthy, you need a complete list of the hostnames they cover, where each certificate lives, who is responsible for renewing it, and what happens if the renewal fails. This article walks through a method small technical teams can use to build that inventory and check it on a regular schedule.

Start with hostnames, not certificates

Most people think about certificates as files, but visitors encounter hostnames. Begin by listing every name a browser might request: the apex domain, the www variant, staging and preview subdomains, API endpoints, email-related hosts, status pages, and any legacy names that still redirect somewhere. Include names you think are retired, because redirects and old links often keep them alive in ways nobody remembers.

Pull this list from several sources rather than one. DNS zone records show what is published. Web server configuration files show what is served. Analytics and inbound links show what people still visit. Marketing materials and old email signatures reveal names that no longer appear in code. Compare the sources and mark each hostname as active, redirect-only, or unknown. Unknown entries deserve attention first because they are the ones that expire without anyone noticing.

Record the certificate behind each name

For every active hostname, record which certificate serves it, the issuer, the list of covered names, the expiry date, and the mechanism used to renew it. A single certificate may cover several hostnames, and a wildcard may cover many subdomains that you do not individually track. Those wildcard relationships are exactly where gaps hide, because a subdomain added last year may depend on a certificate whose renewal path nobody has tested since setup.

Check what the browser actually receives, not only what your configuration file claims. Connect to each hostname from outside your network, inspect the presented chain, and confirm the names listed match your inventory. Mismatches usually indicate a deployment that updated one server but not another, or a load balancer still holding an older copy.

Ask your host the questions that matter

Whether you use shared hosting, managed WordPress, or a VPS, the renewal responsibility may sit with the host, with you, or with a third-party tool. Write down the answer for each hostname rather than assuming. Useful questions include: Who receives expiry notices, and at which address? Is renewal automatic, and what is the process when automation fails? Which hostnames are covered by the current setup, and how are new subdomains added? If a certificate is installed manually, who holds the private key and where is it stored? What is the procedure for replacing a certificate quickly after a compromise?

Do not treat vague answers as confirmation. If a provider's documentation does not clearly state how renewal works for your plan, ask in writing and keep the reply with your inventory. This is an information-gathering step, and you should verify every answer against your own environment rather than relying on memory of a sales conversation.

Build a practical review routine

An inventory is only useful if it stays current. Assign one named person to maintain it and set a recurring review, perhaps monthly for small sites and more often when you add services. Each review should confirm that the hostname list matches live DNS, that expiry dates are recorded with enough lead time to act, that notification recipients still exist and read their mail, and that the renewal owner is still employed or still responsible for the service.

Use a short checklist during each review: Are all active hostnames in the inventory? Does each one present a valid chain to a browser? Is every expiry date at least several weeks away, or is a renewal already scheduled? Have notification addresses been tested recently? Has any redirect-only name started serving content again? Record the date and the reviewer's initials so the next person can see what changed.

When you find a problem, fix the process as well as the certificate. If a renewal failed because a DNS record changed, add a step that checks DNS before renewal. If a subdomain was forgotten, add a rule that every new hostname is entered into the inventory at the moment it is created. A good inventory turns certificate expiry from an emergency into a scheduled, boring task, which is exactly the outcome small teams need.

Part of the ToddMichael.tv network.