The domain and SSL renewals nobody remembers until they lapse
The domain registrar's renewal cycle
A "not secure" label shows up right in the browser bar, right where the logo used to load cleanly. A customer texts to ask if something's wrong. Nothing crashed. A certificate simply expired, days ago now, and nobody noticed until someone else finally did.
Your domain name, the actual address people type into a browser, is registered through a company called a registrar, typically on a yearly cycle. That registration has to be renewed on its own schedule, entirely separate from your hosting bill or anything to do with the site's content.
It's easy to assume the domain was a one-time purchase, because it was paid for once during setup. It wasn't. It's a recurring registration that lapses the moment nobody renews it, regardless of how well the rest of the site is running.
The site itself can be perfectly healthy, hosted correctly, fully up to date, and still go dark because of a single unpaid renewal on a completely separate account. That mismatch between site health and domain health is exactly what catches so many otherwise careful owners off guard.
Auto-renew settings and why they get missed anyway
Most registrars offer an auto-renew setting that charges a card on file automatically each cycle. It sounds like it should solve this entirely, and it often does, right up until the card on file expires or the account belongs to someone no longer involved with the business.
Auto-renew reduces the risk considerably. It doesn't eliminate it, particularly when the account itself is one you can't directly access or don't fully control.
A card that expires quietly, unrenewed on its own separate schedule, is the single most common way auto-renew fails. Nobody gets a dramatic warning. The charge just doesn't go through, and the account sits one missed attempt closer to expiration.
Who holds the registrar login, and why that matters
If the domain was registered by a previous designer, in their own account, under their email address, you may not even know where to look when a renewal needs attention. That single detail decides how bad any of this actually gets.
Confirm today whether the domain sits in an account you control, with your own contact information on file. If it doesn't, working out who legally owns that registration is a question worth resolving well before it becomes urgent, not after a lapse notice. Who owns your website covers that ownership question in full, including what a fair contract should say about it up front.
A registrar account is easy to overlook because it rarely gets touched after the initial setup. That's exactly why it's worth checking now, while there's no fire to put out and no deadline pressuring the answer.
SSL certificate expiration and the browser warning it triggers
Separate from the domain entirely, a security certificate has to be renewed on its own cycle, sometimes shorter than the domain's, occasionally as often as every few months depending on how it's configured. When it lapses, browsers show visitors a prominent warning before they can even reach the site.
Many hosting setups renew this automatically in the background without anyone doing anything. Some don't, particularly on older or manually configured sites, which means it's worth confirming directly rather than simply assuming it's handled.
The warning itself looks alarming, full-page and hard to click past. Visitors who don't recognize what caused it will assume the site itself is unsafe, not just the certificate behind it. That impression can stick even after the certificate is fixed.
What it actually takes to lose a domain to expiration
A domain doesn't vanish the instant it lapses. Registrars typically hold it for a window after expiration where it can still be reclaimed, often at an added cost, before it opens up for anyone else to register.
The real risk isn't losing it overnight. The risk is not noticing for long enough that the recovery window closes, at which point someone else, a competitor or a stranger, can register your exact domain name outright.
Reclaiming a domain during that grace window costs noticeably more than a normal renewal would have. It's still far cheaper than losing the name entirely and having to rebuild every link, listing, and business card pointing to it.
Setting your own renewal reminders, separate from the registrar's
Don't rely solely on the registrar's notification emails. Those can land in spam, go to an old address, or simply get skimmed past during a busy week without registering at all. A single missed email is all it takes for the whole system to fail silently.
Set your own calendar reminder tied to the actual renewal date, a month or two ahead, checked by a person who will genuinely see it. It's a small habit that closes off one of the more avoidable ways a website goes dark, and it costs nothing beyond a few minutes.
If more than one person could plausibly be responsible for this, name one specific person. A reminder sitting in a shared inbox that three different people glance past is barely better than no reminder existing at all.
Write down where the domain is registered, where the certificate comes from, and who has login access to each, in one place you'd actually think to check. It won't matter for years, right up until the one year it does, and by then the details are exactly the kind of thing everyone assumes someone else remembers.
This sits alongside hosting as a recurring bill someone has to actively own, and it's one more piece of what taking care of a website after launch actually means once the excitement of the launch itself has faded.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go