Blog ·
Domain renewal reminder: why registrar emails miss, and what to add
A domain renewal reminder that works has three parts: auto-renew turned on at the registrar, a payment method on file that will still be valid on the renewal date, and one reminder that goes to a person who is still around. The registrar already sends you expiry emails, and for most domains that is required by policy. Those emails fail for a dull reason: they go to the address on the registration, and that address often belongs to someone who left, an inbox nobody reads, or a spam folder. This guide explains what the registrar sends, why it misses, and how to add a reminder of your own, from a calendar entry for one domain to a monthly renewals ticket for a team that owns dozens.
Statements about registrar notices are as of October 2026, from ICANN's Expired Registration Recovery Policy and Gandi's documentation.
What your registrar already sends #
For generic top-level domains such as .com, .net and .org, ICANN's Expired Registration Recovery Policy sets a minimum. The policy says:
Prior to the expiration of any gTLD registration, registrars must notify the registered name holder of the expiration at least two times.
It then fixes when those two notices go out:
One of these notices must be sent approximately one month prior to expiration
and the other approximately one week before. One more notice must follow in the first few days after the domain expires. Many registrars send more than the minimum. Gandi, for example, documents reminders at two months, one month, 15 days and one day before the renewal end date, and sends the two-month reminder "only to the billing contact".
Country-code domains such as .uk or .de follow their own registry's rules, so the schedule varies. Check your registrar's help pages for the exact dates on those.
| Reminder | Who sets it | Who receives it | Where it fails |
|---|---|---|---|
| Registrar expiry emails | ICANN policy plus the registrar | The contacts on the registration | Old address, unread inbox, spam filter |
| Auto-renew | You, at the registrar | Nobody: it just charges | Expired card, closed account, disabled by a transfer |
| Calendar entry | You | Whoever owns the calendar | One person's calendar, one domain at a time |
| A renewals ticket | Your team | Whoever the ticket is assigned to | Only if nobody owns the ticket |
The registrar's emails are a safety net, and they land in exactly the inbox your process forgot about. Treat them as the backup, never the plan.
What happens if the reminder is missed #
Expiry is rarely instant loss, but the first effect is visible. The ICANN policy requires the registrar to interrupt the domain's existing DNS resolution path for at least the last eight days after expiration that the domain can still be renewed, so the website and often the email on that domain stop working before the name is lost. After the domain is deleted, generic registries must offer a 30-day Redemption Grace Period, during which the policy says:
the registry must disable DNS resolution and prohibit attempted transfers of the registration
Restoring a domain in redemption usually costs more than renewing it, and the exact fee is set by the registrar. Past that point, the name can be registered by anyone.
So the real cost of a missed renewal is the outage before anyone notices, and the scramble to find who has the registrar login.
Set up a domain renewal reminder for one or two domains #
If you own a handful of domains and you are the only person who touches them, keep it simple:
- Find the expiry date. Your registrar's dashboard shows it. ICANN's lookup tool at lookup.icann.org shows it for most generic domains, including ones registered elsewhere.
- Turn on auto-renew at the registrar, and check the card on file expires after the renewal date.
- Update the contact email on the registration to an address that will outlive any one employee, such as a shared admin mailbox.
- Add a calendar entry 30 days before expiry, repeating every year, titled with the domain name and the registrar's name so you know where to log in.
- Write down where the login lives, in your password manager, next to the domain.
That covers most people. The calendar entry exists for the year auto-renew fails quietly: a declined card, a registrar migration, or a transfer that switched it off.
When one calendar entry stops being enough #
Teams that manage many domains hit three problems a personal reminder does not solve.
- Renewals are scattered across the year. Twenty domains bought at different times means twenty dates. One calendar entry per domain becomes clutter that nobody reads.
- The owner changes. The person who registered the domains leaves, and their calendar leaves with them.
- Nobody can prove it was checked. An auditor, a client or a manager asks whether renewals are reviewed, and the honest answer is "someone usually notices".
The fix is to stop tracking each date and instead run one check on a fixed rhythm: every month, someone opens the list of domains, looks at everything expiring in the next 60 days, and confirms each one will renew. Certificates fit in the same check, since a TLS certificate expiring takes a site down just as fast. One recurring check catches every date, whoever holds the job this year.
Keep a domain list in Jira #
If your team already works in Jira, the list and the check can both live there. A simple setup:
Create one issue per domain, or a table in the project's description if you prefer a single page. Issues are easier to filter.
Add fields for registrar, expiry date, auto-renew (yes or no), and the account that pays.
Save a filter for anything expiring soon. Assuming a date field named
Expiry date:project = OPS AND "Expiry date" <= 60d ORDER BY "Expiry date" ASCUpdate the expiry date each time a domain renews, as part of closing the monthly check.
The same register pattern works for software licences and warranties, covered in asset management for Jira.
Make the renewals check appear every month #
The list only helps if someone looks at it. A ticket that appears on the 1st of every month, assigned to the person who owns domains, turns "someone usually notices" into a dated record.
| Calendar reminder | Jira Automation scheduled rule | A scheduling app | |
|---|---|---|---|
| Who gets reminded | One person | Whoever the rule assigns | Whoever the rule assigns |
| Record that the check happened | None | The resolved ticket | The resolved ticket |
| Lands on a weekend or holiday | Yes | Unless the rule says otherwise | Moves or skips, set per project |
| Survives the owner leaving | No | Yes | Yes |
| Cost | Free | Counts toward your plan's automation usage | App licence |
Jira Automation #
Jira's built-in Automation can create the ticket with a Scheduled trigger set to monthly. It works well for one rule. The things to know: each run counts toward your plan's automation usage, which our Jira Automation pricing guide explains, and "first working day of the month" needs a cron expression, covered in Jira cron expression.
A scheduling app #
Recurring Work Items for Jira is our app, and a monthly check like this is the job it was built for:
- Turn the app on for the project that holds the domain list, and choose who may schedule.
- Create a rule that runs every month on a date, such as the 1st, or on a weekday position, such as the first Monday.
- Title it with tokens so each month's ticket is named for its month, for example
Domain and certificate renewals {{now.monthName}} {{now.year}}. - Put the saved filter's link in the description, with the rule "confirm everything expiring in the next 60 days will renew".
- Set the assignee and a due date of one week after the run.
It uses no Jira Automation quota, because the scheduling is the app's own. If the 1st falls on a weekend or a holiday you have set for the project, the rule moves or skips as you chose. Every created or failed run is written to the rule's history with its reason. It is free for up to 10 users.
For a single domain that renews once a year, the same app can run a rule every 12 months. For most teams the monthly sweep is better, because it catches every date at once.
What to check each month #
Put this list in the ticket's description, or as subtasks if several people share the work:
- Expiring in the next 60 days: confirm auto-renew is on, or renew by hand now.
- Payment method: confirm the card or account on each registrar is valid past the next renewal.
- Contacts: confirm the registrant and admin email addresses still reach a person.
- Certificates: confirm anything expiring soon will renew automatically, or schedule it.
- Unused domains: decide whether to keep paying for them.
Close the ticket with a one-line comment: what was renewed, what was dropped, what was fixed. A year of closed tickets answers the question "do you check renewals?" without anyone having to remember. If this check is part of a wider ops routine, Jira for IT operations shows where it sits beside backups, patching and access reviews.
When the manual way is enough #
If you own fewer than five domains, all on auto-renew with a valid card and a contact email you read, the registrar's own reminders plus one calendar entry a year are enough. You do not need a ticket. The monthly check earns its place when domains are spread across registrars or years, when more than one person might be the owner, or when someone outside the team expects proof that renewals are reviewed.
Frequently asked questions #
Do registrars have to send renewal reminders? For generic domains such as .com, yes: ICANN's policy requires at least two notices before expiration, about one month and one week ahead, and one more shortly after. Country-code domains follow their own registry's rules.
Why did I not get a domain expiry reminder? Usually because the contact email on the registration is old or filtered. Check the registrant and admin contacts in your registrar's dashboard.
Is auto-renew enough on its own? Mostly, until the card on file expires or a transfer switches it off. One reminder of your own covers that year.
Can Jira remind me about domain renewals? Jira can hold the domain list and a filter for upcoming expiry dates. A scheduled rule, from Jira Automation or an app like Recurring Work Items for Jira, creates the monthly check ticket so someone reviews the list.