Why Registrar Renewal Emails End Up in Spam

When a domain expires, the post-mortem usually includes the line "but the registrar should have told us". Usually it did. For generic domains like .com, ICANN's Expired Registration Recovery Policy requires registrars to send reminders: roughly a month before expiry, roughly a week before, and once more shortly after. The mail went out. It just did not reach anyone who acted on it.

Here is why that keeps happening, and why the answer is not "check spam more carefully".

The address is from the day you bought it

The reminders go to the registrant or account contact on file, and that address was set when the domain was bought. Over the years it tends to drift away from anyone who is paying attention:

• A former employee. The person who registered the company domain left two years ago. Their mailbox was closed, or forwards to a manager who filters it.
• An agency or freelancer. They set up the site, registered the domain on their own account and moved on to other clients.
• A personal address. A founder used a private Gmail on day one. It is still there, and the founder now reads work mail somewhere else.
• An address on the domain itself. admin@example.com is the riskiest choice of all, for reasons covered below.

Nobody updates registrar contacts as part of their normal work. They are only ever thought of when something is already broken.

Privacy forwarding adds another hop

Most registrars now hide contact details behind a privacy service or a redacted public record. Mail sent to the public contact goes to a forwarding address, which then passes it on to the real one. Each hop is another place where a filter, a bounce or a misconfigured forward can drop the message without anyone noticing.

The registrar's own reminders usually go straight to the account email, but people often mix up the two. Then a "domain contact" that was updated in one place still points at the old address in the other.

Automated mail looks like marketing

A renewal reminder is sent in bulk, from an automated address, with a template, links and an unsubscribe footer. That is exactly what spam filters, and people, are trained to ignore.

• Filters sort it with promotions. Gmail's tabs and Outlook's Focused Inbox file it next to the same registrar's weekly offers on new domain extensions.
• People unsubscribe. Someone clicks "unsubscribe" on the registrar's marketing mail and assumes it covers everything. Often it doesn't. Sometimes it does.
• Sender reputation varies. A registrar's bulk mail shares sending infrastructure with its marketing. If that reputation dips, the important mail goes to spam along with the rest. How SPF, DKIM and DMARC decide this is covered in why your email lands in spam.

Phishing taught everyone to distrust it

"Your domain is about to expire, renew now" is one of the oldest phishing templates there is. Fake renewal notices and fake invoices from lookalike registrars arrive all year. Careful people learned the right lesson for phishing, which is not to click renewal links in emails, and the wrong lesson for real reminders, which is to ignore them.

The result is that a genuine notice gets the same suspicion as a fake one, and both go unread.

The address that dies with the domain

If the contact address is on the domain that is expiring, the failure locks itself in. While the domain is active, the reminders arrive and get ignored. Once it expires, the DNS changes, the mail records go with it, and every further notice from the registrar bounces. The "final notice" can't reach the mailbox it is addressed to, because that mailbox stopped existing when the domain lapsed.

That is why a registrar contact should always be on a different domain from the one it is responsible for.

What to do about it

Fixing the email helps:

1. Update the account and registrant contacts to an address on another domain that a current person reads.
2. Turn on auto-renew and check that the card on file has not expired.
3. Allowlist the registrar's sending domain so its mail skips the promotions tab.
4. Put the expiry date in a calendar that someone actually looks at.

But all four still rely on one message reaching one person at the right moment. A better approach is to stop relying on the registrar's email at all. Barkme reads the registration expiry date from the registry over RDAP once a day and sends its own warnings at 30, 14, 7 and 1 days before the domain lapses, to the email, Slack, Telegram or webhook channels your team chose. The warnings come from outside your domain, so they still arrive if the domain itself has already gone.

Domain monitoring and SSL alerts covers what is checked and on which plans. For what happens if a domain does lapse, read the domain that lapsed. For a quick check of when a domain expires, use the free domain health check.