Domain Expiry and Transfers: Process, Timelines and Gotchas

A domain name is less like property you own and more like a lease you renew every year. Miss the renewal and your website and email go dark together; wait longer and the price of getting it back climbs sharply, until a point of no return where anyone — including professional domain snipers — can grab it. The good news: expiry is not a same-day deletion. It is a multi-stage lifecycle, and knowing what each stage allows (and costs) is enough to avoid almost every disaster.

This guide covers two things. First, the post-expiry timeline — how long the grace, redemption and pendingDelete windows last and how the cost jumps between them. Second, registrar transfers — unlocking, the auth/EPP code, how long a transfer takes, and how to keep your site and mail online throughout. To see where your domain stands right now, check its expiry date and status codes with the WHOIS lookup tool.

The expiry timeline: what each stage allows and costs

For gTLDs like .com and .net, an expired domain walks through the stages below in order. The pattern to remember: with every stage, your options shrink and the price grows.

Note that the grace window varies wildly by registrar policy — some give 45 days, others push the domain into redemption almost immediately — so never assume you have a month of slack. Whether WHOIS shows autoRenewPeriod or redemptionPeriod changes the price by an order of magnitude; decode any EPP status you see with the domain status code explainer.

Worked example: you discover the domain 40 days after expiry

Scenario: you find out that example.com expired 40 days ago. The site shows a parking page and inbound mail is bouncing. What are your options?

1. Run a WHOIS lookup first. If the status reads redemptionPeriod, the registrar's grace window (say, 30 days) has already ended and the domain is in redemption.
2. If it is in redemption:request a restore through the original registrar. Expect a restore fee (registry charge plus registrar markup, usually $80–150) on top of a one-year renewal. Painful, but it is the only guaranteed way back — at this stage you cannot transfer it away or re-register it fresh.
3. If you are lucky and still in grace (a registrar with a 45-day window): log in and renew at the normal price. Service typically returns within hours.
4. If it is already pendingDelete: there is nothing to restore. Your only move is placing a backorder to catch the name the second it drops (~5 days later) — and for any desirable name you will be bidding against professional drop catchers, where auction prices can run into the hundreds or thousands of dollars.

The lesson: every day of delayed discovery removes an option. Enable auto-renew, keep the payment card current, and glance at the WHOIS expiry date once a quarter — it is the cheapest insurance you will ever buy.

Registrar transfer, step by step

Moving to a cheaper or better registrar is a "registrar transfer". The domain itself does not change — only the company managing its registration does. The standard flow:

1. Unlock the domain: at your current registrar, remove the clientTransferProhibited status (the default anti-theft lock). A transfer request against a locked domain is rejected outright.
2. Get the auth code (EPP code):issued from the current registrar's control panel. This code is what proves the owner consents to the move.
3. Start the transfer at the new registrar: enter the domain and auth code and pay the transfer fee — which almost always includes one year of renewal, added on top of your current expiry date. You lose nothing.
4. Wait for approval: confirm the email sent to the registrant address. If the losing registrar releases immediately it can finish in hours; otherwise auto-approval makes the whole thing take about 5–7 days.

• The 60-day rule: ICANN policy blocks transfers within 60 days of the initial registration and within 60 days of a previous transfer. Many registrars also impose a 60-day lock after a material change to the registrant name or email.
• Never transfer right before expiry. If the domain expires mid-transfer you can end up in the worst of both worlds — a domain in grace limbo at the losing registrar. If expiry is close, renew for a year first, then transfer at your leisure.
• If the registrant email in WHOIS is a dead mailbox, the approval mail never arrives and the transfer stalls indefinitely. Update the contact email before you start.

The classic mistake: a transfer does not move your DNS

A registrar transfer moves the registration, not your DNS hosting or web hosting. The trap: if you were relying on the old registrar's free DNS service, that nameserver service can be cut off once the transfer completes — and your site and mail vanish days later with no obvious cause.

• Using third-party DNS (Cloudflare, Route 53, etc.): your nameservers are independent of the registrar, so the transfer changes nothing. This is the safest setup.
• Using the old registrar's bundled DNS:before transferring, export every record (A, AAAA, CNAME, MX, TXT/SPF, DKIM, DMARC…), recreate them at the new DNS host, switch the nameservers, let things settle — then start the registrar transfer.
• Missing even one record — MX and TXT are the usual victims — silently breaks email. Work through the migration with the DNS change checklist so nothing is left behind.

The rule of thumb: DNS first, transfer second. With nameservers already on an independent host, it does not matter whether the transfer takes five days or seven — your services never blink.