Domain Expiration — Days Until Registration Lapses
This checks the registration expiry date recorded for a domain — the date the name itself stops being yours, as distinct from any certificate or signature on it. It is the simplest check in this entire catalogue and comfortably the one with the worst consequences when skipped, because a domain that lapses does not degrade: it stops, and then it becomes available to someone else.
Why run it
Auto-renewal is not the guarantee it appears to be. Cards expire, registrar accounts are tied to an employee who has left, renewal notices go to an address nobody reads, and a domain transferred between registrars can lose its renewal settings in the move. None of those produce a signal you would notice. The check exists because the assumption that renewal is handled is exactly the assumption that fails, and it fails silently for months before the deadline arrives.
Why automate it
The expiry date for a domain is typically a year or more away, which means a manual check has to be remembered on a timescale nobody manages reliably, for every domain in a portfolio that grows. Automating it removes the human memory entirely: a scheduled check with staged alerts gives you notice at sixty days, thirty, and seven, and covers the defensive registrations and old project domains that nobody has thought about since they were bought — which are precisely the ones that lapse.
What it gives you
Insurance against the most complete and least recoverable failure in this list. Losing a domain costs the traffic, the email, the certificates and possibly the name permanently, and a scheduled check makes it essentially impossible.