SSL Hygiene Beyond the Padlock: A Question Checklist for Small Teams

GhostHosts editorial ·

A filter (=kernel, neuron) in a convolutional artificial neural network. The input to the filter is three features thick. The three features come from three separate filters in the previous layer of the deep neural network.
Illustrative image. Cecbur · CC BY-SA 4.0 · Cropped and resized. Image source

Most site owners think about SSL only when a browser warns about it. A certificate that is valid today can still leave visitors with broken pages, redirect loops, or insecure resources loaded from third-party embeds. Good SSL hygiene means looking past the expiry date and asking a set of specific questions about what your site actually serves. This article walks through those questions in a way small technical teams can apply with whatever tools and hosting arrangement they already have.

Start With a Hostname Inventory

A certificate only protects the names it was issued for. Before you can judge whether your SSL setup is healthy, you need a complete list of every hostname that serves traffic on your behalf. That includes the apex domain, the www variant, any subdomains for blogs, shops, or APIs, and forgotten hostnames left over from old campaigns or staging environments.

Ask who created each hostname, what it points to, and whether anyone still depends on it. Hostnames that no one remembers are the usual cause of surprise expiry alerts. Write the inventory down in a shared location and assign an owner to each entry so that a renewal reminder has someone to reach.

Check What Visitors Actually Receive

The certificate installed on a server is not always the one a visitor sees. Load balancers, reverse proxies, and content delivery layers can each present their own certificate. Ask which system terminates the TLS connection for each hostname, and verify the chain from the outside rather than trusting a configuration file.

Look at the full chain, not just the leaf certificate. An incomplete chain can work in some browsers and fail in others, which makes the problem hard to reproduce. Testing from more than one client type helps reveal these gaps before a visitor reports them.

Audit Redirects and Protocol Consistency

A site that is technically secure can still send visitors through insecure steps. Check whether plain HTTP requests redirect to HTTPS in a single hop, and whether the www and non-www versions agree on a single canonical destination. Redirect chains that bounce between variants slow pages down and can drop query parameters that tracking or login flows depend on.

Also confirm that HSTS, if you use it, is configured deliberately. A long max-age on a domain that you may later need to serve over plain HTTP for a subdomain can create a lockout that takes time to unwind. Document the decision and the reasoning behind it.

Find Mixed Content Before Visitors Do

Mixed content appears when a secure page loads scripts, stylesheets, images, or frames over plain HTTP. Browsers may block these resources or show warnings, and the result can break forms, widgets, or checkout elements. The problem often arrives with a new theme, a plugin update, or an embedded video from a third party.

Review your pages with a crawler that reports the resource URLs loaded by each page, not just the page status. Pay attention to hardcoded absolute URLs in templates and database content, since those survive a protocol change unless someone updates them deliberately.

A Practical Hygiene Checklist

Work through these questions on a fixed schedule, such as once per quarter or before any planned migration. Does every active hostname appear in the inventory with a named owner? For each hostname, which system terminates TLS, and when does its certificate expire? Does the full chain validate from at least two different client environments? Does HTTP redirect to the correct HTTPS destination in one hop? Are www and non-www behaviors consistent with your chosen canonical form? Is HSTS set to a value your team has agreed on? Do any pages load insecure resources, and are absolute URLs in content still pointing to HTTP?

If your hosting plan or control panel does not expose some of these details, ask your provider directly how certificates are issued, renewed, and installed, and who is responsible when renewal fails. Treat those answers as part of your site documentation rather than assumptions. Hygiene is less about any single tool and more about keeping a current, shared picture of what your site serves and who is accountable for each part of it.