I run a small WordPress studio — webmaster.co.ua, 18 years, 235+ projects. Of all the ways a client's site can go down, the most avoidable — and most common — has nothing to do with code, hosting, or plugins. It's a domain that lapsed because nobody was watching the renewal date.
A lapsed domain looks identical to a catastrophic technical failure, to the client. From their side, the site is just gone. They don't see an expired registration notice buried in an inbox they don't check — they see "the website I paid for doesn't exist anymore," and the panic that follows is the same as if the server had caught fire. The actual fix is usually a five-minute renewal, but only once someone diagnoses that it's a domain issue and not a code issue.
Domain ownership and site maintenance are two separate relationships, and clients don't distinguish between them. A client might hire us for the site but register the domain years earlier through some other registrar entirely, with a personal email that's since been abandoned. Nobody explicitly owns watching that renewal date — not us, because we didn't register it, and not them, because they've forgotten it exists as a recurring obligation.
We now ask for domain registrar access as a standard part of onboarding, even when we don't manage renewals. Not to take ownership away from the client — to know when the expiration date is, so we can flag it before it becomes an emergency. A single calendar reminder, set once at project start, has prevented more downtime for us than any technical safeguard we've built.
SSL certificates fail the same way, for the same underlying reason. Auto-renewal usually handles this quietly, until a hosting migration or a config change quietly breaks the auto-renewal without anyone noticing until the certificate expires and browsers start showing warnings to visitors. It's the same category of failure as a domain lapse — invisible until it isn't, and entirely preventable with one person responsible for checking.
The pattern across both: failures that are 100% preventable tend to happen exactly because they're boring. Nobody gets excited about tracking renewal dates, so it's the task most likely to fall through the cracks between developer and client. The fix isn't technical sophistication — it's just deciding, explicitly, who's responsible for noticing before the countdown hits zero.
If you've never asked a client who owns their domain renewal or SSL monitoring, it's worth a five-minute conversation — it's the least interesting question you'll ask all project, and one of the most consequential.
Top comments (0)