Renewals: domain, hosting, licences and certificates

A single website depends on at least four separately renewing commitments. Each is on its own schedule. Each is potentially billed to a different card and held by a different party. A lapse in any one of them can take the whole thing offline, no matter how well everything else is being maintained. Tracking these individually, rather than as one combined list, is exactly how one of them gets missed.

The four renewals, briefly: domain, hosting, licences and certificates

The domain, renewed annually or for whatever term was chosen at registration — covered fully in domain expiry and renewal. Hosting, generally billed monthly or annually, and just as capable of lapsing on an expired card as a domain is. Software licences, particularly on a self-hosted CMS. A premium theme or plugin’s paid update licence can expire without breaking the software’s current function immediately. But it stops future security updates from being received once it lapses. SSL/TLS certificates, though on most modern setups these renew automatically at no cost — worth confirming rather than assumed, per SSL certificates and HTTPS explained.

Why tracking domain renewal and hosting separately is how one gets missed

Each of these typically renews through a different provider, on a different billing cycle. Each is notified to a different email address, depending on who originally set it up. A business owner watching only their own inbox may never see a renewal notice that went to a developer’s account instead. A developer watching only the accounts they manage may not know about a domain renewal the client handles separately. No single party naturally sees all four unless someone has deliberately built that visibility in.

What a consolidated website renewal checklist should contain, including account access and contact details

For each of the four items: which provider holds it, the renewal date, which party is responsible for actually paying and confirming it, and where the renewal notice is sent. This is a simple document. Its value is entirely in existing at all and being kept current — a renewals list nobody has updated in two years is barely better than no list.

Why premium software licences are the one most commonly forgotten, and the risks of missing it

Domain and hosting renewals are generally visible because the site or email stops working right away if they lapse. A premium plugin or theme licence lapsing is quieter. The software usually keeps working exactly as before. Only the ability to receive future updates is affected, which produces no immediate symptom at all. This makes it the easiest of the four to let quietly expire without anyone noticing. That goes on right up until a security update becomes unavailable at exactly the moment it is needed.

What to do this week: assign responsibility, regardless of how confident anyone feels

Build the consolidated list described above, even if it starts as a rough draft with gaps, and identify which items currently have no clear owner. A gap discovered now, while nothing has lapsed, costs nothing to fix. The same gap discovered during an actual lapse costs considerably more, in both time and, for a domain specifically, real risk of losing the name outright.

Insurance and warranty renewal dates, and reviewing them regularly

Where a business holds a website-related insurance policy or a supplier’s extended warranty arrangement, its renewal date belongs on the same consolidated list. This is an easily overlooked fifth item alongside the four covered above. It follows the identical logic: a renewal nobody is tracking is a renewal that eventually lapses unnoticed.

Why a spreadsheet beats memory, however good the memory is

A list that exists only in one person’s memory disappears the day that person is unavailable, leaves the business, or simply forgets. A shared, written document, however simple, is genuinely more reliable than relying on anyone’s recall, no matter how conscientious they are.

Assigning a single owner for the list itself

Beyond listing who is responsible for each individual renewal, someone should own keeping the list itself current. That means adding new items as they arise, and removing ones no longer relevant. Otherwise, the list quietly becomes as unreliable as the memory it was meant to replace.

Why calendar reminders are not quite enough on their own

A calendar reminder tells someone a renewal is coming. It does not confirm the payment method behind it is still valid, or that the account is still accessible. Pair the reminder with an actual login check: confirm the account can still be reached and the payment details are current. That catches problems a reminder alone cannot, because a reminder only prompts action. It does not verify anything.

What to do the first time this list is built

Do not assume any existing renewal is currently correct. Verify each one directly, rather than copying assumed details from memory or an old document. The entire value of building this list properly the first time is catching an existing, unnoticed gap before it becomes a genuine lapse.

Why this list earns its keep even if nothing ever goes wrong

The list costs little to build and maintain. Its value is not diminished by years passing without an incident. It is closer to a fire extinguisher than a frequently used tool — worth having ready, regardless of how rarely it is actually needed.

Where to go from here

The domain-specific detail behind this list is on domain expiry and renewal. Confirming who currently holds each of these accounts at all is the subject of who holds the hosting account and who owns your business domain. Keeping this list current on an ongoing basis is exactly what what website maintenance costs prices as part of a genuine arrangement.