What happens to my email when my domain expires?

Incoming mail stops being deliverable, usually before you notice the website is down. ICANN's Expired Registration Recovery Policy requires the registrar to interrupt the existing DNS resolution path after expiration [1], which means the MX record that tells the world where to deliver your mail is no longer answered. The mailbox still exists; nothing can reach it.

Do senders get told their message did not arrive?

Eventually, and not usefully. A sending server that cannot resolve or reach your mail host queues the message and retries; the standard says retries continue until the message is sent or the sender gives up, and 'the give-up time generally needs to be at least 4-5 days' [2]. So your customer gets a failure notice most of a week later, if at all.

How long do I have to renew before it is really gone?

Registrars may delete an expired registration at any time after expiry [1], so there is no guaranteed grace period at that stage. After deletion, gTLD registries must offer a Redemption Grace Period of 30 days during which the deleted registration can be restored at the registrant's request by the registrar that deleted it [1]. Restoration is typically far more expensive than renewal.

Will the mail sent during the outage be delivered once I renew?

Some of it. Messages still sitting in a sending server's retry queue when service returns will go through. Anything already given up on - roughly four to five days out for a typical sender [2] - has bounced and will not be retried. Expect a partial recovery, not a full one.

Why is my email still broken for hours after I renewed?

DNS caching. Every DNS record carries a TTL, the interval for which it may be cached before being discarded [3], and resolvers around the world are entitled to hold the failure result until it expires. Renewal fixes the authoritative answer immediately; the internet catches up over the following TTL window.

Who is supposed to warn me before this happens?

Your registrar. ICANN policy requires at least two expiration notices, one approximately a month before expiry and one approximately a week before [1]. The catch is that those notices go to the registrant contact address on file - which is very often an address at the expiring domain, so the warning arrives in a mailbox that is about to stop receiving mail.

How do I make sure this never happens again?

Put the registrar contact on an address at a different domain, turn on auto-renew, keep the payment card current, and confirm the registration is in the business's name rather than a former contractor's. You are entitled to move a registration between registrars, and a registrar may refuse only in the specific circumstances ICANN lists, one of which is non-payment for the previous registration period [4] - so fix the billing before you try to move.

What Happens to My Email if My Domain Expires?

The sixty-second answer

Your email stops. ICANN policy requires a registrar to interrupt the domain's DNS resolution after expiry, so the MX record that routes your mail disappears and nothing can be delivered. Sending servers retry for roughly four to five days, then bounce. After deletion there is a 30-day redemption window, at restoration prices.

Email breaks before the website does

When a domain lapses, the failure people expect is a website that stops loading. The failure that costs money is the one nobody sees: mail simply stops arriving, and there is no error message on your end because nothing is trying to reach you any more.

The mechanism is DNS. Your website is found through an address record; your mail is found through an MX record on the same domain. The mail standard is strict about this: names used in SMTP must resolve to MX or address records, and "if MX records are present, but none of them are usable, or the implicit MX is unusable, this situation MUST be reported as an error" [2]. Once the domain stops answering, there is no MX to find, and every sending server in the world treats your business as unreachable.

Crucially, your mailbox is fine. The messages already in it are untouched, your password still works, your provider is still running. What has gone is the signpost. This is why "my email is down" and "my domain expired" so rarely get connected by the person experiencing them.

The actual timeline

ICANN's Expired Registration Recovery Policy governs what a registrar of a generic top-level domain must do, and it is more specific than most people realise.

Before expiry. Registrars must notify the registered name holder at least twice: one notice approximately one month before expiration, and one approximately one week before [1]. These must be delivered in a way that does not require you to take action to receive them - typically email.

At expiry. Registrars may delete an expired registration at any time after it expires [1]. There is no universal grace period you can rely on. What is mandatory is the interruption: for registrations deleted within eight days of expiration, the existing DNS resolution path specified by the registrant "must be interrupted by the registrar from expiration of the registration until its deletion"; and for registrations deleted eight or more days after expiry, the path must be interrupted for at least the last eight consecutive days that the registration remains renewable [1]. In other words, the policy deliberately makes the domain stop working so that you notice.

After deletion. With the exception of sponsored gTLD registries, all gTLD registries must offer a Redemption Grace Period of 30 days immediately following deletion, during which the deleted registration may be restored at the registrant's request by the registrar that deleted it [1]. Restoration is a defined process, and it is priced as a recovery rather than a renewal.

After that. The name is released and can be registered by anyone. At that point somebody else can receive mail addressed to your business, which is a materially worse problem than an outage.

What your senders experience

Nothing dramatic, which is the trouble. A customer sends you a quote request. Their mail server cannot find a working MX for your domain, so it queues the message and retries. The standard's guidance is that "retries continue until the message is transmitted or the sender gives up", and "the give-up time generally needs to be at least 4-5 days" [2].

So for the better part of a week, your customer believes the message was sent and is waiting for a reply. Then they receive a delivery failure notice - or, on some systems, nothing at all - and conclude you did not bother to answer. The reputational damage lands days after the technical fault, and it lands as rudeness rather than as an outage.

This is also why the recovery is partial. Renew inside the retry window and queued messages flow in as servers make their next attempt. Renew after it, and the messages that already bounced are gone; the sending server will not try again, because from its point of view it already told the sender.

Why it is still broken after you pay

Renewing restores the authoritative DNS answer immediately. It does not reach into every resolver on the internet that has already cached the previous answer. Each DNS record carries a TTL - "a 32 bit unsigned integer that specifies the time interval (in seconds) that the resource record may be cached before it should be discarded" [3] - and caches are entitled to hold what they have until that clock runs out.

Practically: expect mail to start trickling in within minutes for some senders and within hours for others, and do not conclude the renewal failed because one particular correspondent still gets a bounce. If you are about to make DNS changes deliberately, lowering the TTL a day in advance shortens this window - the same trick that makes a planned provider move painless, described in switching business email providers without losing mail.

The warning that goes to the wrong place

Here is the failure loop that catches small businesses. The registrar must send expiration notices to the registrant contact on file [1]. That contact address is very often an address at the domain being renewed. When the domain expires, the mailbox stops receiving - including the follow-up notices telling you it has expired.

The second version of the same loop: the registration is in the name of a web designer, a former employee, or a contractor who set the site up years ago. The notices go to them. They no longer work with you. You find out from a customer.

Both are fixable in ten minutes. Set the registrar account's contact and login to an address on a different domain - a personal address is fine for this one purpose. Confirm the registrant is your business. And check that you can log in to the registrar yourself. ICANN's Transfer Policy says registrants "must be able to transfer their domain name registrations between Registrars", and limits refusal to an enumerated list that includes non-payment for the previous registration period [4] - which is another reason to settle the bill before attempting to move a lapsed name anywhere.

The record-keeping problem underneath

An outage is annoying. A gap in your records is a different category of problem.

Every person carrying on business in Canada must keep records and books of account, and section 230(4)(b) of the Income Tax Act requires them to be retained until the expiration of six years from the end of the last taxation year to which they relate; where those records are kept electronically, subsection 230(4.1) requires them to be retained in an electronically readable format for the same period [5]. Purchase orders, invoices and confirmations that arrive by email are records. Messages that bounced during a lapse were never received and cannot be produced.

The same gap has a privacy dimension. Under PIPEDA's Schedule 1, an individual may request to be informed of the existence, use and disclosure of their personal information and be given access to it, and may challenge its accuracy [6]. "We were unreachable that fortnight" is an uncomfortable answer to give a customer asking what you did with their file. Our longer treatment is in business email retention and records in Canada.

The five-minute prevention checklist

Confirm the domain is registered to the business, not to an individual or an agency. Move the registrar login and contact address off the domain itself. Enable auto-renew and verify the card on file has not expired. Note the expiry date somewhere that is not email - a calendar reminder 60 days out. And keep the registrar account credentials where a second person in the business can reach them.

If the domain is currently held by someone else and you want it back in your own name, that is a transfer, and the policy that governs it is on your side [4].

Where we sit

MapleMail hosts business email on a domain you own and control. We are not your registrar, and we deliberately do not want to be the only party holding your domain - the point of the arrangement is that your mail provider and your domain registration are separable, so a dispute with either one never strands you.

What we do is keep the mail side boring: Canadian-hosted mailboxes, standard IMAP access, and DNS records for your domain that we will document for you rather than hide. If your domain lapses, we will still have your mailbox and its contents when the name comes back. What we cannot do is invent the messages that bounced while the world could not find you - nobody can. That part is prevented, not repaired.

Plans and what each mailbox includes are on the pricing page. Before you look at that, though, go and check your domain's expiry date and who the registrant contact is. It is a two-minute job and it is worth more than anything else in this article.

What happens to my email if my domain expires?