Auto-Renew: Necessary, Not Sufficient
Auto-renew is a registrar setting that automatically charges your payment method and renews a domain before it expires. It is the first line of defense against losing a name — and a payment instruction rather than a guarantee, because it fails silently whenever the card, the account, or the notification email has gone stale.
How auto-renew fails in practice
- •The card on file expires, gets reissued, or the bank declines the charge.
- •The registrar account email is one you no longer read, so failure warnings go unseen.
- •The domain sits at a registrar you stopped logging into — common in multi-registrar portfolios.
- •Auto-renew was toggled off on one name in a batch operation and nobody noticed.
The layered approach
Treat auto-renew as layer one. Layer two is a renewal ladder of reminders (60/30/14/7 days out) going to an inbox you actually read. Layer three is verifying expiry dates against the registry via RDAP rather than trusting dashboard or spreadsheet dates. Sourdough automates this across every registrar, with a 7-day free trial, $0 due today.
Frequently Asked Questions
Should I enable auto-renew on every domain?
Enable it on everything you intend to keep, and make the drop decision deliberately before the renewal date. The one real downside is accidentally paying for names you meant to release — a renewal review 60 days out solves that.
When does auto-renew actually charge?
Varies by registrar — commonly somewhere between 30 days and a day before expiry, with retries on failure. Know your registrar's schedule so a failed charge still leaves you time to fix it.