Why Auto-Renew Fails (and Domains Expire Anyway)

"We have auto-renew on" is the most common reason people give for not tracking domain expiry. It's also the reason a lot of domains lapse. Not because auto-renew is broken, but because of what it actually is: a standing instruction to attempt a charge. It is not a guarantee that the domain renews. Between the instruction and the renewal sit a payment processor, a registrar account, a registry, and several settings — and any one of them can quietly break the chain.

Here's where it actually goes wrong, roughly in order of how often it happens.

1. The card expired, and nobody read the email

This is the big one, and it has a nasty property: payment methods and domains expire on completely unrelated schedules. You register a domain for three years. Your card is reissued after two. The card on file is now dead, and the renewal attempt eighteen months later fails against a card number that hasn't existed for a year.

What makes it dangerous isn't the failure — it's the silence. A failed charge produces an email that looks like every other billing email, arriving months before anything visible breaks. Nothing on your site changes that day. By the time there's a symptom, the domain has already lapsed.

The same applies to an expired PayPal authorization, a revoked bank mandate, or a corporate card that got cancelled when someone left.

2. Auto-renew is per-domain, and you checked the account setting

Most registrars have an account-level default and a per-domain toggle. People check the first and assume the second. But the per-domain setting is what governs, and it doesn't always inherit:

• Domains transferred in from another registrar frequently arrive with auto-renew off.
• Domains bought during a promotion sometimes default to off, so the discounted first year doesn't roll into a full-price renewal automatically.
• Bulk imports and API-created domains follow whatever the API sent, which may be nothing.

So the honest check isn't "is auto-renew on for my account?" — it's "is auto-renew on for this domain?", answered one domain at a time.

3. The renewal price changed

Auto-renew charges the current renewal price, not the price you paid. First-year promotional pricing is standard in this industry, and the renewal can be several times the initial cost. Registry-level price rises get passed through too.

That matters twice. If the amount exceeds a card limit or a prepaid balance, the charge fails. And even when it succeeds, a portfolio quietly renewing at rates nobody has looked at in three years is its own problem — the reason it's worth recording what each domain should cost.

4. A status code is blocking the renewal

Registration records carry EPP status codes, and some of them prevent renewal outright — clientRenewProhibited is the explicit one, but a domain in a dispute or under a registry hold can also be unrenewable. Auto-renew will keep failing against a domain that is not, at that moment, renewable at all.

These codes are public. Our WHOIS & DNS lookup shows them, and how to read a WHOIS record explains which are protective locks (most of them) and which are signs of trouble.

5. Registrant verification suspended the domain

This one surprises people because it has nothing to do with money. Under ICANN rules, gTLD registrants must verify their contact email — and if you change the registrant email and don't click the verification link, the domain can be suspended regardless of how paid-up it is. Auto-renew works perfectly; the domain stops resolving anyway.

The related trap: renewal notices and verification requests both go to the registrant address on file. If that address is a former employee's mailbox or an alias nobody monitors, every warning lands somewhere nobody reads. That failure mode is covered in more depth in why registrar renewal reminders aren't enough.

6. The domain is at a registrar you forgot you had

Portfolios sprawl. A client bought one domain at their host, a contractor registered another, an old project used a different registrar because of a promo. "Auto-renew is on" is usually true of the account you're thinking of — and unverifiable for the two accounts you aren't.

7. Auto-renew works, but the timing doesn't save you

Registrars attempt renewal on their own schedule and retry failed charges over a window. If the retries span the expiry date, there's a period where the domain has technically lapsed. Depending on the TLD and registrar, that can mean DNS stops resolving before the successful retry lands.

Recovery is usually possible — that's what the grace and redemption periods are for, and what happens when a domain expires covers the sequence — but "recoverable" is not the same as "didn't go down".

How to actually verify it

The check that means something is per-domain, and it has three parts:

1. Is auto-renew on for this specific domain? Not the account default.
2. Is the payment method on file currently valid? Check the expiry date on the card, not just that a card exists.
3. Is the domain in a state where it can renew? No blocking status codes, no pending verification.

Do that across every registrar you use, not just the main one.

The backstop

All three of those answers can be true today and false in six months, silently, without anything visibly changing. That's the case for tracking expiry independently of the system that's supposed to handle it — a second opinion that doesn't depend on the registrar's email reaching you or its charge succeeding.

That's what DomainChest does. It reads each domain's registration directly, so the expiry date it shows is the registry's, not a status your registrar dashboard reports. It records whether auto-renew is off and flags those domains, tracks what each renewal should cost, and emails you well before the date regardless of what your registrar does or doesn't send. For domains at supported registrars you've connected, it can turn auto-renew back on from the dashboard.

You can check any single domain right now with the free domain expiry checker — no account needed. If you want the systematic version rather than the spot check, how to never let a domain expire lays out the full routine.