Almost every 'lost my domain' story is a renewal or transfer-code failure, not an attack. Four settings prevent nearly all of them.
Published September 8, 2026 · ~3 min read
The process
The ongoing-maintenance checklist, in order of how often it actually bites people.
Directions
1Enable auto-renew and keep the payment method current
Auto-renew is the single biggest lever against accidental loss — it charges your card on file some number of days before expiration instead of relying on you to notice a reminder email. The main failure mode isn't forgetting to renew; it's an expired card silently failing the auto-renew charge.
Check your registrar's renewal reminder settings too: most send 3–5 emails over 30–60 days before expiration, all to the contact email on file, which is exactly why WHOIS contact accuracy (below) matters.
2Understand what happens if a renewal is missed anyway
If a domain isn't renewed by expiration, most gTLDs enter an auto-renew grace period (commonly ~0–45 days depending on the registrar's own policy) where you can still renew at the normal price. After that, it typically enters a Redemption Grace Period (RGP, ICANN-standard ~30 days) where the registry suspends the domain and only the original registrar can restore it — usually for a steep redemption fee ($80–$300+ is common). After redemption expires, the domain is deleted and becomes available to anyone.
ccTLDs (country-code domains) set their own grace and redemption rules independent of ICANN's gTLD policy — some have none at all, so a missed renewal on a ccTLD can mean instant loss. Check the specific registry's policy rather than assuming gTLD norms apply.
3Update your registrant email whenever it changes
Renewal notices, transfer confirmations, and abuse complaints all go to the registrant/admin contact email on file. An inbox you stopped checking is how people lose domains they had every intention of renewing — they simply never saw the notice.
4Know what's needed to move a domain to another registrar
ICANN policy imposes a 60-day transfer lock after initial registration and after any registrant-of-record change, during which the domain can't be transferred to a new registrar. Outside that window, transferring requires unlocking the domain at the current registrar and obtaining an EPP auth code (sometimes called a transfer key), which you then supply to the gaining registrar.
A transfer also generally adds a year to the registration term (for gTLDs, at the standard renewal price) — plan transfers around your renewal date rather than treating them as free.
Typical transfer flow: unlock domain at current registrar → request EPP/auth code → start transfer at new registrar with that code → approve confirmation email → wait ~5-7 days (or approve immediately to skip the wait)
5Re-check nameservers and DNS after any registrar move
A transfer moves registration, not necessarily DNS hosting — if your nameservers point elsewhere (Cloudflare, your host), a transfer normally leaves them untouched, but it's worth confirming immediately after any transfer or registrar-side change, since a reset to registrar-default nameservers is the most common cause of unexpected downtime.
Common issues & fixes
My domain expired and now shows a redemption/pending-delete status.
Contact your current registrar immediately — during the Redemption Grace Period only they can restore it, typically for a fee. Waiting until pending-delete clears means the name becomes public and can be registered by anyone, including specialized backorder services.
A transfer is stuck for days.
Check for a still-active transfer lock, an auth code that was already used or expired (they're often single-use and time-limited), or a pending confirmation email sitting unapproved in the registrant's inbox.
I don't want to wait 60 days to transfer a domain I just registered.
You can't skip ICANN's post-registration lock, but you usually can still change nameservers/DNS immediately — a transfer moves who bills and administers the domain, not where its DNS is hosted.
Honesty note: articles are drafted with AI assistance, then a human checks each one against the vendor's current setup flow before it publishes — nothing goes live unreviewed. Vendor interfaces still change; if a step looks different, the underlying record is what matters.