Short answer
If you forget to renew a domain, the cost depends on how late you are. Inside the auto-renew grace period (typically the day of expiry through 30 to 45 days after, depending on the registrar and TLD), you can usually renew at the regular price with no penalty — the registrar's auto-charge may have failed, but a manual renewal at the standard rate closes the gap. Inside the redemption period (typically ~30 days after the grace period ends), the domain can still be recovered, but only by paying a redemption fee on top of the renewal price, commonly $80 to $200 for a .com, often $100 to $250 for a .net or .org, and sometimes $200 to $500+ for a premium or restricted TLD. After redemption, the domain enters pending delete, is released by the registry, and becomes available for new registration by anyone; drop-catching services routinely register valuable expired domains within seconds of release. Plan for the cheap case (grace period renewal) but prepare for the expensive case (redemption) and the worst case (drop) — because the difference between them is a calendar reminder and a backup payment method.
The domain expiry timeline, stage by stage
The expiry timeline is one of the few parts of domain cost that is governed by ICANN and the registry, not by your registrar. The exact day counts vary by TLD and by registrar policy, but the structure is the same for nearly every generic TLD (.com, .net, .org, .info, .biz, .io, .co, and so on). Country-code TLDs follow a similar pattern with their own windows.
- Active registration. The domain is registered, DNS resolves normally, and email and web services work. The registrar attempts to charge the saved payment method on the renewal date.
- Expiration day, T+0. The registration period ends. If auto-renew succeeded, the domain rolls over and stays active. If auto-renew failed (expired card, insufficient funds, disabled auto-renew), the domain enters expired status. The registrar typically sends a first expiration reminder email.
- Auto-renew grace period, T+0 to T+45 (typical). Most registrars allow the original registrant to renew at the regular renewal price during a window of roughly 0 to 45 days after expiry. The domain may continue to resolve DNS, or the registrar may suspend DNS and park the domain on a default landing page; both policies exist. The registrant can still recover at the standard renewal price, no redemption fee.
- Redemption grace period (RGP), T+45 to T+75 (typical). The domain is held by the registrar but cannot be renewed at the regular price. Recovery is possible only by paying a redemption fee (charged by the registry and passed through by the registrar) on top of the renewal price. DNS is suspended. Email to the domain stops working. The website, if any, is offline.
- Pending delete, T+75 to T+80 (typical). The domain is locked at the registry level. No recovery is possible through the registrar. The domain is queued for release.
- Released / dropped, T+80 (typical). The domain becomes available for new registration. Drop-catching services and backorder providers monitor the release queue and submit registration requests within seconds. For a desirable domain (short, keyword-rich, existing backlinks, brand value), the domain is usually gone within minutes. For a generic domain with no resale value, the domain may sit available for hours or days.
- New registration by someone else. Once a domain is dropped and registered by another party, the original registrant has no way to recover it at any price. The only path back is to wait for it to expire again, negotiate a buyout, or accept the loss.
The exact day counts are set by the registry and the registrar's policy. ICANN requires a minimum of a 30-day redemption period for gTLDs (.com, .net, .org), and most registries follow a ~75-day total window from expiry to release. Registrars can extend the grace period at the start of the timeline, but they cannot shorten the redemption period at the end; that part is fixed.
What each stage costs to recover
The table below lines up the stages of the expiry timeline with the typical cost to recover the domain at each stage, the typical DNS and email status, and what the stage actually means in practice. Numbers are illustrative ranges across common registrars and TLDs; verify the current grace, redemption, and pending-delete windows on your registrar's policy page, because each registrar sets its own grace window and each registry sets its own redemption fee.
| Stage | Typical day window (from expiry) | Cost to recover | DNS / email status | What it really means |
|---|---|---|---|---|
| Active registration, renewal succeeds | Day -1 to T+0 | Standard renewal price (often $9 to $20 for a .com, $9 to $25 for a .net, $10 to $25 for a .org) | Normal; nothing changes | The best case: the saved payment method is charged, the domain rolls over, and the user does not notice. |
| Auto-renew grace period | T+0 to T+30 to T+45 (varies by registrar and TLD) | Standard renewal price, no penalty. The registrar may charge the saved payment method automatically when the user clicks "renew now." | DNS may resolve normally, or the registrar may suspend DNS and park the domain on a default page; both policies exist. Email may continue to flow or may bounce, depending on the registrar. | The cheap recovery path. As long as the user notices the reminder email and renews within the grace window, the only cost is the regular renewal price. |
| Redemption grace period (RGP) | T+30/45 to T+75 (typical ~30 days) | Redemption fee + renewal price. For a .com this commonly totals $80 to $220; for a .net or .org it commonly totals $100 to $250; for some premium or restricted TLDs it can total $200 to $500+. | DNS suspended. Email stops working. Website is offline. The domain still belongs to the original registrant, but the registrar has flagged it for release. | The expensive recovery path. The domain is still recoverable, but the cost has multiplied. Some users discover the problem here and pay the redemption fee without realizing they could have renewed at the regular price a few days earlier. |
| Pending delete | T+75 to T+80 (typical ~5 days) | No recovery possible. The domain is locked at the registry. The registrar has no power to undo the release. | DNS suspended. Domain is queued for release. | The "too late" stage. The original registrant cannot recover the domain at any price through the registrar. The only remaining path is to wait for release and try to re-register before anyone else does. |
| Released / dropped | T+80 (typical) | Re-registration cost (the new registration price for that TLD at the registrar that catches it). If the domain has resale value, drop-catchers and backorder services can drive the effective cost to hundreds or thousands of dollars through auction or premium pricing. | Domain is in the public pool. Whoever registers it first owns it. | The worst case for the original registrant. For a desirable domain (existing traffic, backlinks, brand value, short length), the domain is usually re-registered within seconds by a drop-catcher. The original registrant has lost the domain and any SEO, traffic, or brand value tied to it. |
| Re-registered by someone else | T+80 onward | Re-registration cost is moot; the domain is no longer the original registrant's. Recovery requires negotiation, auction buyout, or accepting the loss. | DNS resolves to whoever registered the domain. Email and any service tied to the domain are now under new ownership. | The unrecoverable case. The original registrant's path back is to negotiate a buyout at whatever the new owner asks, or to start over with a different domain name. |
The cheapest way to read this table is to assume the cost of a missed renewal is at least the redemption fee plus the renewal price, and to plan for the grace period as the realistic recovery window. After grace, the price jumps; after redemption, the window closes entirely.
Why auto-renew is not enough
Auto-renew is the most common reason a domain gets close to expiry in the first place. The mechanism is simple: the registrar attempts to charge the saved payment method on the renewal date, and if the charge succeeds, the domain rolls over without the user noticing. But the mechanism has several failure modes, and each one is a real risk for the domain owner.
- Expired credit or debit card. The saved card expires and the auto-renew charge fails. The registrar sends a reminder email, but the email goes to the same address the user has not checked in six months. By the time the user notices, the domain is in grace or redemption.
- Changed email address. The user switches email providers, forgets to update the contact email at the registrar, and the reminder email goes to an inbox the user no longer reads. The user has no way to act on a reminder they never see.
- Disabled auto-renew. Some users disable auto-renew to avoid surprise charges (a common reaction to a controversial renewal price). They intend to renew manually, then forget. The domain expires and there is no auto-charge to catch it.
- Registrar's first-charge failure behavior. Some registrars disable auto-renew after a single failed charge, which means the next year's renewal will not be attempted. Other registrars retry for several days before giving up. The behavior is not consistent across registrars, and it is not always documented clearly.
- Domain in a registrar account the user no longer uses. A common pattern: a developer registers a domain under a personal account, leaves the company, and the company has no idea the domain exists. The renewal reminder goes to the developer's old email, the auto-renew fails, and the domain drops. The company loses a domain that may have been carrying traffic, email, or brand value.
- Payment provider block. Some banks and payment providers block recurring charges they do not recognize, especially on first-time charges or charges from foreign merchants. The block looks like a generic decline, and the user does not know to update the payment method until the domain is already in grace.
The fix is not a single setting. The fix is layered redundancy: auto-renew enabled, a valid backup payment method, a current contact email, a calendar reminder at T-30, T-14, T-7, and T-1 before expiry, and (for important domains) a registrar that does not silently disable auto-renew on a failed charge.
What changes by registrar and by TLD
The redemption fee is set by the registry and passed through by the registrar, with the registrar sometimes adding a handling fee on top. The grace period length is set by the registrar, with a minimum set by the registry. The day counts and the dollar amounts below are illustrative ranges across common registrars and registries; verify the current values on your registrar's policy page.
| Registrar / TLD | Auto-renew grace period | Redemption fee (typical) | Total recovery cost during redemption (typical) | What to verify before relying on it |
|---|---|---|---|---|
| GoDaddy (.com) | ~18 days after expiry (registrar-specific grace) | ~$80 redemption fee + standard renewal | ~$100 to $120 total | Confirm the exact grace window and whether DNS continues to resolve during grace. |
| Namecheap (.com) | ~30 days after expiry (registrar-specific grace) | ~$80 to $100 redemption fee + renewal | ~$100 to $130 total | Confirm whether the grace period is "renewal at standard price" or "renewal with a small fee." |
| Cloudflare Registrar (.com) | At-cost renewal; no markup during grace | No additional Cloudflare markup; the registry's RGP fee still applies (typically $80 to $100) | ~$90 to $120 total | Confirm the exact RGP fee and the grace window on the registry's published schedule. |
| Porkbun (.com) | ~30 days after expiry | Registry's RGP fee (typically $80 to $100) + standard renewal | ~$100 to $130 total | Confirm whether Porkbun adds a handling fee on top of the registry's RGP fee. |
| Hover (.com) | ~30 to 40 days after expiry | Registry's RGP fee + renewal | ~$100 to $130 total | Confirm the grace window length and the RGP fee total. |
| Gandi (.com) | ~30 days after expiry | Registry's RGP fee (typically higher than .com for some TLDs) + renewal | ~$100 to $200 total for .com, higher for premium TLDs | Confirm the RGP fee schedule by TLD; some ccTLDs are notably higher. |
| Generic .com / .net / .org RGP (any registrar) | Varies; minimum ~30 days set by ICANN | Set by the registry, typically $80 to $200 | ~$100 to $220 for .com; often $120 to $250 for .net and .org | The redemption fee is not negotiable; the registrar passes the registry's fee through. The total cost is the sum of the two. |
| .io and other registry-priced TLDs | Varies by registry | Higher than .com; often $100 to $300 | Often $150 to $400 total | Premium and registry-priced TLDs have higher RGP fees. Verify on the registry's fee schedule, not just the registrar's renewal page. |
| Country-code TLDs (ccTLDs) | Varies widely; some are 0 to 30 days, others longer | Varies widely; some are $50 to $100, others $200 to $500+ | Varies; some ccTLDs are notably cheaper, others notably more expensive | ccTLD policies differ from gTLD policies. Some ccTLDs do not have a redemption period at all, which means expiry leads directly to release. |
| Premium TLDs (.app, .dev, .ai, etc.) | Varies by registry | Often $200 to $500+ | Often $250 to $600+ | Premium TLDs have premium redemption fees. The higher the original registration cost, the higher the redemption fee is likely to be. |
The cheapest way to read this table is to assume the redemption fee for a standard .com is around $80 to $200, and to plan for $200 as the realistic worst case at a registrar that adds a handling fee. For premium TLDs, double the buffer.
Drop catching and backordering: what happens to a dropped domain
Once a domain enters the pending delete stage and is released, the registry hands it back to the public pool. For a generic domain with no resale value, the domain may sit available for hours or days before anyone re-registers it. For a desirable domain (short, keyword-rich, existing traffic, brand value, existing backlinks), the domain is almost always snapped up within seconds of release by a drop-catching service.
Drop-catching services operate by submitting a large volume of registration requests the instant a domain becomes available, betting that at least one of their requests will land first. The services charge either a flat fee (often $10 to $100 per backorder) or a percentage of the auction price if they catch the domain. The most well-known providers are SnapNames, DropCatch, and NameJet, and most of the major registrars offer backordering through one of these services.
The economics of drop catching matter for the original registrant in two ways. First, if the original registrant realizes the domain is in pending delete and tries to re-register it the moment it is released, they are competing against services that submit hundreds of requests per second. The original registrant almost always loses unless they pay for a backorder service themselves. Second, once the domain is caught and re-registered, the new owner can choose to auction it, list it for sale at a premium, or hold it. The original registrant's path back is to negotiate a buyout at whatever the new owner asks, which is often hundreds to thousands of dollars for a valuable domain.
The realistic scenarios for a dropped domain:
- Generic, low-value domain. The original registrant can usually re-register the domain within hours or days for the standard registration cost. The risk is low; the cost of recovery is the standard registration fee.
- Brand or keyword domain with backlinks. Drop-catchers and SEO resellers are likely to grab it. The original registrant's path back is a backorder service (typically $10 to $100 per attempt) or a buyout negotiation (often $200 to $5,000+ depending on the domain's value).
- Short, dictionary-word, or premium domain. Drop-catchers and domain investors will almost certainly grab it. Re-registration is unlikely; buyout is the only realistic path, and the price is set by the new owner's market.
The cheapest way to avoid this entire sequence is to renew the domain inside the grace period. Once the domain is in pending delete, the cost of recovery is no longer in the user's control.
How to prevent a missed renewal in the first place
Prevention is the cheapest fix, and the prevention list is short. The list below is the minimum set of actions to keep a domain from expiring unintentionally. For a portfolio of multiple domains, all of these scale linearly with the number of domains.
- Keep auto-renew enabled and on a valid payment method. Use a credit card or payment account that will not expire before the renewal date. Check the card expiration date against the renewal date once a year.
- Keep the contact email current at the registrar. Renewal reminders go to the contact email on file. If you change email providers, update the contact email at the registrar first, then start using the new address.
- Add a backup payment method at the registrar. Many registrars allow a secondary card or PayPal account. If the primary charge fails, the secondary method can be a backup before grace expires.
- Set a calendar reminder at T-30, T-14, T-7, and T-1 before expiry. The reminders should trigger a manual check of the domain's status, even if auto-renew is enabled. Auto-renew should be the safety net, not the only line of defense.
- For a portfolio, audit the renewal dates at least once a year. A spreadsheet or a password manager entry with the domain, registrar, renewal date, and auto-renew status is enough. The audit catches the domains that have slipped out of auto-renew without anyone noticing.
- For business-critical domains, consider multi-year registration. Registering for two, three, five, or ten years at a time reduces the number of renewal events. The cost is paid up front, but the risk of a missed renewal drops to near zero for the registration term.
- For domains you no longer use but want to keep, set a calendar reminder anyway. The "I'll just let it drop" decision should be made deliberately, not by accident. A parked domain that you no longer care about is cheaper to renew for another year than to recover from a drop.
- For domains you do want to drop, turn off auto-renew and let the domain expire. This is the inverse of the previous point: if you do want to drop the domain, turn off auto-renew, mark the expiry date, and let the domain drop on schedule. The domain will enter the public pool after the redemption period ends.
The unifying rule is that auto-renew is a single point of failure. Layered reminders and a backup payment method are the redundancy that catches the failure before it becomes a redemption fee.
The answer box
The real cost of a forgotten domain is the cost of where you are in the expiry timeline when you notice. Inside the grace period (typically 0 to 45 days after expiry), recovery costs the standard renewal price with no penalty — usually $9 to $25 for a standard .com. Inside the redemption period (typically 30 days after grace, total ~75 days from expiry), recovery costs the renewal price plus a redemption fee, commonly $80 to $200 for a .com, often $100 to $250 for a .net or .org, sometimes $200 to $500+ for premium or restricted TLDs. After redemption, the domain enters pending delete and is released; a drop-catching service can re-register it within seconds, and the original registrant's path back is a backorder attempt or a buyout negotiation at whatever the new owner asks. The cheapest way to stay out of this entire sequence is auto-renew on a valid payment method, a current contact email, a backup payment method, and calendar reminders at T-30, T-14, T-7, and T-1 before expiry.
Buyer checklist: domain expiry and redemption
- Confirm the current auto-renew grace period for your registrar and your TLD; the window is set by the registrar and varies, and the day counts above are typical but not universal.
- Verify the redemption fee for your TLD on the registry's published schedule, not just the registrar's renewal page; the fee is set by the registry and passed through, with some registrars adding a handling fee on top.
- Keep the saved payment method valid through the renewal date; check the card expiration date against the renewal date at least once a year, and add a backup payment method as a redundancy.
- Keep the contact email at the registrar current; renewal reminders go to the contact email on file, and a missed reminder is the most common cause of an unrecoverable expiry.
- Set calendar reminders at T-30, T-14, T-7, and T-1 before expiry, even with auto-renew enabled; auto-renew should be the safety net, not the only line of defense.
- For a portfolio of multiple domains, audit the renewal dates and auto-renew status at least once a year; a spreadsheet or password-manager entry with the domain, registrar, renewal date, and auto-renew flag catches the domains that have slipped out of auto-renew.
- For business-critical domains, consider multi-year registration; registering for two, three, five, or ten years reduces the number of renewal events and the risk of a missed renewal for the registration term.
- If the domain does enter the redemption period, pay the redemption fee promptly; every day of delay increases the risk of an accidental drop, and the redemption window is the last guaranteed recovery point before the domain is released to the public pool.
Affiliate disclosure: PriceGap is an independent buyer-education site. This article contains no advertiser checkout links, does not claim a current sponsor relationship with any registrar, and does not quote fixed live prices, grace windows, or redemption fees. Grace periods, redemption fees, drop-catching rules, and registry RGP schedules change frequently and vary by TLD; verify current terms directly with your registrar and on the relevant registry's published schedule before relying on a specific window or fee.