Domain Renewal Management

What renewal management includes

Here is a story most domain owners recognize. A renewal notice arrives from a registrar you forgot you had an account with. It looks exactly like the phishing attempts you delete every week, so you delete it too. It sits in the trash for days. By the time you realize it was real, the domain has already expired and you are reading recovery instructions instead of a receipt.

Renewal management exists so that never happens. It is more than a list of expiration dates. A working system tracks five things for every domain: the expiration date, the actual renewal price this year, the payment method that will be charged, the auto-renew setting, and the account that controls all of it. Then it adds the piece almost everyone skips: a decision deadline before each renewal, so the keep-or-drop call is made while there is still time to act on it.

If your domains live at more than one registrar, renewal management is one slice of a bigger job. The guide on how to manage domains across multiple registrars covers the master inventory this page builds on. This page goes deep on the renewal layer specifically.

Why the expiration date alone is not enough

Knowing when a domain expires feels like the whole job. It is maybe a fifth of it. ICANN's Expired Registration Recovery Policy requires registrars to send at least two renewal reminders before a domain expires, roughly one month and one week out. On paper, the system works. In practice, it fails in ordinary, human ways:

• The expired card. Auto-renew is on, but the card on file got reissued. The charge silently fails.
• The dead admin email. Reminders go to an address you set up years ago and never check.
• The departed employee's account. A domain was registered under someone's personal login. They left. Nobody knew it was there.
• The registrar acquisition. Your registrar got bought, the migration email looked like spam, and your login quietly stopped working.
• The undocumented handoff. DNS is documented. The registrar login is not. The person who knew is two jobs gone.
• The scam that looked real. A fake renewal notice and the legitimate one landed in the same inbox. You deleted both.

None of these are exotic failures. They are Tuesday. And the numbers say quiet lapses happen at scale: Verisign's Domain Name Industry Brief put the .com and .net renewal rate at 75.0 percent for the fourth quarter of 2025. One in four of those registrations did not renew. Some were dropped on purpose. Plenty were not.

It happens to companies with entire teams for this. In July 2017, marketo.com expired, the primary domain of a marketing technology company serving thousands of enterprise customers. Links and images in millions of already-sent emails broke, and the site vanished, until a customer named Travis Prebble noticed and paid the renewal himself. Marketo recovered, reviewed its procedures, and became the industry's standing reminder that renewal systems fail through cards, contacts, and process, not through malice.

The same mechanism runs on your fifteen domains right now. The only difference is scale. So the fix is not a better expiration date. It is controls around the payment, the contact, the account, and the attention.

The 90-60-30 day reminder system

Three reminders per domain, in one calendar you actually look at, each with its own job:

• 90 days out: review. Does this domain still have a purpose? Is the registrar login working, and is the card on file current? Ninety days leaves room to fix access problems, which always take longer than expected.
• 60 days out: decide. The keep-or-drop deadline. Keep for a written reason, launch it, redirect it, sell it, or release it. Made now, the decision is calm. Made at expiration, it is a panic.
• 30 days out: verify. For keepers, confirm auto-renew is on and the payment method clears. This is the catch-the-silent-failure pass, not the decision pass.

Three reminders feels redundant until the first one saves you. The registrar's own emails are a fourth layer, not a replacement; they fail in all six ways listed above.

Why not lean on the grace period instead? Because grace and redemption windows are not universal. They differ by registry, registrar, and domain ending, recovery often costs extra, and some names are simply gone once they lapse. A recovery window is for people who already lost the domain. The reminder system is so you never meet it.

Auto-renew and payment failure controls

Auto-renew is a payment instruction, not a tracking system. It will faithfully charge a card that no longer exists and tell you about it in an email you will not see. Treat it as one control in a set, not the safety net:

• Auto-renew on for every domain you intend to keep, at every registrar. Off is fine too, but only as a written decision to let a specific domain go.
• A current payment method on each registrar account, with the card's own expiration date noted in your inventory. An expired card on a registrar you rarely log into is the classic way a domain dies.
• A backup payment method where the registrar supports one, so a single reissued card cannot take the whole account down.
• The account email pointed at an inbox you read. Renewal reminders, failed-payment alerts, and verification requests all land there, and an unanswered verification can suspend a domain on its own.
• After every renewal, a receipt check. A charge that silently failed looks exactly like a charge you forgot about, until the domain drops.

One honest test: could a card reissue this month cost you a domain? If you cannot answer at every registrar you use, that is the first item on the checklist below.

Premium renewal handling

Not every domain renews at the standard rate, and this is where renewal budgets quietly break. Some registries designate certain names as premium, and at many endings that premium applies to the renewal every single year, not just the first purchase. A name that cost real money up front can also carry a renewal price many times the standard rate, forever.

The rules vary by registry, by ending, and by registrar, so the only reliable move is to check the actual renewal price for each specific domain in your registrar account, before you buy and once a year after. Do not assume the first-year price is the ongoing price; promotional first years with much higher renewals are common and legal.

In the inventory, flag every premium renewal explicitly. A $12 renewal can survive on autopilot for years without much harm. A $300 renewal deserves a real decision every single year, which is exactly what the 60-day deadline is for.

Keep-or-drop decision fields

A renewal date tells you when to decide. These fields are how you decide. Add them to your inventory next to the dates and prices:

How to actually make the call, including when a simple page beats selling and when releasing is the right answer, is its own framework: the guide on what to do with unused domains walks the six states and the decision matrix. This page's job is making sure that decision has a deadline and the data to be made well.

The monthly reconciliation

Once a month, fifteen minutes, four questions:

1. What expires in the next 90 days, and does each of those domains have its decision made and written down?
2. Do any payment cards expire in the next 90 days? Update them now, while it is a two-minute task instead of a recovery project.
3. Did every recent renewal charge actually clear? Check the receipts against the inventory.
4. Does the inventory still match reality? Spot check dates, prices, and auto-renew status against each registrar. Renewal prices drift, and transfers reset dates.

This monthly pass is the renewal-specific slice of the wider rhythm in the domain management checklist, which adds the quarterly full reconciliation and the annual decision review on top.

And remember that renewal is the one dimension of domain health that sends reminders. Ownership and access, DNS and certificates, visibility, and purpose all run silent, which is why the domain health check audits all five on the same rhythm.

Spreadsheet, calendar, and software options

Three honest ways to run this system, and the point where each one stops being enough:

A spreadsheet plus a calendar is the right starting point for a small portfolio. The spreadsheet holds the inventory and decision fields; the calendar holds the 90-60-30 reminders. It costs nothing and works, with one weakness: it only knows what you typed. It will not notice a price increase, a failed charge, or a transfer that reset a date. Under roughly twenty domains, with a real monthly pass, it holds up fine.

Registrar tools alone work only if everything lives at one registrar and the contact and payment details never drift. Each registrar reminds you about its own domains and nothing else, which is exactly how the forgotten-account story at the top of this page happens.

A portfolio platform earns its keep when domains span registrars or the list has outgrown manual upkeep. SiteWarming, for disclosure the product behind this resource center, approaches renewals from the decision side: the domain renewals analysis takes your domain list and returns a keep-or-drop recommendation for each name, and the asset dashboard holds the whole portfolio in one view across registrars, with an estimated value beside every domain. To be clear about the boundary: the renewals themselves still happen at your registrar. SiteWarming informs the decision; it does not process the charge.

Whichever option you pick, the system is the same five controls: one inventory, three reminders, verified payment, a read inbox, and a decision deadline. The tool just decides how much of it is maintained by hand.

Copy the renewal-control checklist

The one-time setup, the monthly pass, and the per-renewal decision as plain text, ready to paste into your notes app, task manager, or team wiki.

RENEWAL-CONTROL CHECKLIST (sitewarming.com/domain-management/domain-renewal-management/)

ONE-TIME SETUP
[ ] Build one inventory of every domain: registrar, expiration date, renewal price, auto-renew status, payment method, and account email
[ ] Confirm auto-renew is ON for every domain you intend to keep, and OFF only as a written decision
[ ] Confirm the payment method on every registrar account, and note the card's expiration date in the inventory
[ ] Confirm every registrar account email is an inbox you read, not one you retired years ago
[ ] Flag premium renewals: any domain whose renewal price is above the standard rate for its ending
[ ] Add reminders at 90, 60, and 30 days before each expiration, in one calendar
[ ] Set a decision deadline 60 days before each expiration: keep for a reason, or let it go

EVERY MONTH
[ ] Review everything expiring in the next 90 days: is the keep-or-drop decision made and written down?
[ ] Check for payment cards expiring in the next 90 days and update them now, not at renewal time
[ ] Confirm recent renewal charges actually went through; a silent card failure looks like success until the domain drops
[ ] Reconcile the inventory against each registrar: dates, prices, and auto-renew status
[ ] Check spam folders for renewal notices, and whitelist the senders you almost deleted

AT EVERY RENEWAL DECISION
[ ] Re-read the purpose you recorded for the domain
[ ] Check this year's renewal price against last year's; prices change and premium tiers exist
[ ] Decide: keep for a reason, launch, redirect, sell, or release, and write the decision down
[ ] If keeping: confirm auto-renew, the payment method, and the contact email one more time
[ ] If releasing: check nothing depends on the domain (email, links, logins), then let it expire on purpose

Renewal management is not about becoming more technical. It is five controls, set up once and checked monthly, so no domain you still care about disappears over an expired card.

Limitations

• Grace, redemption, and recovery windows are not universal. They vary by registry, registrar, and domain ending, and some names cannot be recovered at all once they lapse. Confirm the rules for each specific domain with its own registrar; nothing on this page is a promise of a recovery window.
• The Verisign renewal rate cited below covers .com and .net registrations only, and a non-renewal is not always an accident; some domains are dropped on purpose.
• This page covers tracking renewals and deciding on them. The renewals themselves, along with transfers and DNS changes, still happen at each registrar.

Sources

1. 5 things every domain name registrant should know about ICANN's Expired Registration Recovery Policy (verified 2026-07-08) (ICANN)
2. The Domain Name Industry Brief, Q4 2025 (verified 2026-07-08) (Verisign DNIB)
3. Marketing giant Marketo forgets to renew domain name (verified 2026-07-08) (The Register)
4. SiteWarming domain renewals analysis (SiteWarming)

Related resources