why domain auto-renew fails (and how to not lose your domain).

auto-renew is an instruction to attempt a payment, not a promise that a domain will be renewed.

that distinction is the whole article. people who lose domains almost never decided to let one go — they had auto-renew switched on, believed the matter was settled, and the attempt failed somewhere they were not looking. every failure mode below is silent by design: the domain still appears in your account, the flag still reads 'on', and nothing indicates that the thing has quietly stopped working.

the payment failures

the card expired. the most common cause by a distance, and the most irritating, because cards expire on a schedule nobody tracks. a card issued in 2023 with a three-year life expires in 2026, and every subscription attached to it fails within the same fortnight. domains lose this race because their renewal is annual — you are not reminded of them monthly the way you are with everything else.

the billing address changed. you moved. the card still works everywhere because the shops you use do not check, but the registrar's processor runs address verification and declines a mismatch. the card is fine; the transaction is not. this one is unusually deceptive since the same card is visibly working elsewhere.

insufficient funds, or the bank blocked it. an annual charge on a card the bank has not seen bill that merchant for twelve months looks anomalous to a fraud model. it gets held for verification, the verification prompt goes to an app you have notifications muted on, and the charge is refused. some registrars retry a few times over some days; some try once.

strong customer authentication. in the UK and EU, some card transactions require an additional challenge. an unattended annual renewal is precisely the kind of transaction that trips this, and there is nobody present to approve it. registrars handle this with varying grace and it fails quietly.

the card was replaced after fraud. your bank issued a new number. you updated the four services you use weekly and forgot the registrar you log into once a year.

the communication failures

the notice went to spam. renewal notices are bulk transactional email from a domain you do not correspond with, containing urgency language and a payment link. that is an excellent description of a phishing email, and filters agree. gmail's promotions tab has swallowed a great many of these.

the contact address does not exist any more. the domain was registered by a co-founder who left, on an email at a company that was acquired, or on an address at a domain that itself lapsed. this compounds beautifully: domain A's renewal notice goes to an address at domain B, which expired last month.

you unsubscribed. registrars send marketing and transactional mail from adjacent systems. an unsubscribe aimed at the upsells occasionally catches more than intended.

the notices arrive and you have stopped reading them. if you own forty domains you receive renewal notices constantly, nearly all of which need no action. the one that matters looks identical to the ninety that did not. this is alert fatigue, and it is a design problem rather than a discipline problem.

the state failures

these are the nastiest, because the payment method is fine and the email arrives — the domain simply is not set to renew any more, and nothing told you.

auto-renew is off after a transfer. the single most under-appreciated item on this list. when a domain moves to a new registrar, the new registrar's default applies, and the setting from your old account does not come with it. many registrars default auto-renew off for incoming transfers. you moved the domain to save money, the transfer added a year, and the flag you were relying on quietly reset. always check the setting at the destination after any transfer completes — and there is a 60-day ICANN transfer lock afterwards, so you have plenty of time to do it.

the domain is in a different account. you have three logins. the domain you are worried about is not in the one you check. an audit that only covers the accounts you remember is not an audit, which is what a bulk WHOIS lookup across every domain you can think of is actually for.

a bulk change missed rows. you selected all, toggled auto-renew, and pagination applied it to the visible page. this happens more than anyone admits.

the registrar will not auto-renew it. some TLDs are excluded from auto-renew at some registrars, usually ccTLDs with registry-specific rules. some registrars refuse to auto-renew a domain under a dispute, a lock, or a failed identity verification. the flag reads on; the renewal is not going to happen.

the reseller in the middle failed. you bought through a web host or site builder that resells someone else's registrations. your payment to them succeeded. their payment to the registrar did not. you will find out late, and it will be a support ticket rather than a button. run a registrar lookup if you are unsure whether there is a company in the chain you have never thought about.

why registrar reminders are not a safety net

the common thread: the registrar's reminder system and the registrar's renewal system share failure modes. if the contact email is wrong, both the notice and the receipt go nowhere. if the account is one you have forgotten, no reminder helps. if the domain is at a reseller, the reminder chain has an extra link that can break. a warning that fails in the same conditions as the thing it warns about is not a safeguard, it is a copy of the problem.

worse, registrar reminders taper. you get plenty before expiry and steadily fewer as the domain moves through grace and into redemption — which is exactly backwards relative to how much the situation now costs you.

defence in depth

three layers, and they must be independent of each other or you have one layer written down three times.

layer one: auto-renew, everywhere, verified. turn it on, then confirm it row by row rather than trusting a bulk toggle. use a card with a distant expiry date, and put a reminder in your calendar for two months before that card expires — that single entry protects every subscription you have, not just domains.

layer two: independent monitoring. something that reads expiry from the registry rather than from your registrar's mailing list, covers every registrar at once, and alerts on a channel you cannot filter into a tab. registry data does not care whether your card worked; it reports the actual date the actual registry holds. if a domain is 30 days out and the date has not moved, the renewal did not happen — regardless of what your account says.

layer three: a calendar entry that is not automated at all. one annual review, in your own calendar, where you open every registrar account and look. it catches the category that no automation catches: the domain you forgot you owned, in the account you forgot you had.

for layer two, this is exactly what owndle does — it enriches every domain straight from the authoritative registry, so it sees the real expiry rather than what any registrar told you, and alerts at 90, 30, 7 and 1 days by email and push across every registrar in one place. the free tier covers 10 domains, which is enough for most people's genuinely important ones. any tool that reads the registry independently will do; the requirement is independence, not us.

if you want to check the current state of a single domain right now, expiry check returns the live registry date and status in a couple of seconds — and if the date it returns is not the one you were expecting, you have found your answer.