Website or Email Down After a Domain Transfer, Renewal Lapse or DNS Change: What to Check
If your website or email stopped right after a domain transfer, a missed renewal or a DNS change, the cause is almost always one of three things: the domain registration has expired, the domain now points to different nameservers, or the DNS records (including the MX records that route email) were not copied to the new DNS host. Your website files and mailboxes are usually still intact; the internet has lost the directions to them. You can find out which of the three it is in about 10 minutes without changing anything.
This guide is written for an owner whose developer is unavailable. Entrant Technologies builds websites, web applications, mobile apps and custom software; see our web development services. Every check below involves looking at something, not editing it.
What does it usually mean when a website or email stops after a domain or DNS change?
It usually means the internet can no longer find your website or mail server, not that either has been deleted. Finding them depends on three separate jobs, and the fault is nearly always in the first two.
What is the difference between a registrar, a DNS host and a web host?
The registrar is the company you pay each year to keep the domain name registered to you. The DNS host runs the nameservers, which hold the list of records saying where your website and your email live. The web host is the server that stores and serves the website itself. Email is often a fourth company, such as Google Workspace or Microsoft 365.
One company can do all three jobs, which is why owners often do not know they are separate. Trouble starts when one job moves and the others are assumed to follow. Amazon's Route 53 documentation, for example, warns that some registrars provide free DNS service that might be disabled as soon as a transfer is requested, and that moving DNS at the same time as the registration can make the website and email unavailable.
What can I safely check in about 10 minutes?
You can check the registration, the nameservers and the billing status, because all of them are visible without editing anything. Write down what you find as you go.
- Search your inbox and spam folder, and the mailbox of whoever originally registered the domain, for messages from the registrar: renewal notices, failed payments, transfer confirmations or a request to verify your contact email. An unanswered verification email can lead to the domain being suspended.
- Open ICANN Lookup and enter your domain. Note the registrar, the expiration date, the nameservers and the domain status.
- Compare the expiration date with today's date. If it has passed, you have probably found the cause.
- Read the status against ICANN's status code list. "ok" is normal. "clientHold" or "serverHold" means the domain is not activated in the DNS. "redemptionPeriod" or "pendingDelete" means it expired and was deleted. "pendingTransfer" means a transfer is still in progress.
- Compare the nameservers with an old invoice or welcome email. If they now name a different company, your DNS host has changed.
- Log in to the registrar's control panel and look at the expiry date, the auto-renew setting, the payment card on file and any alert banners.
- Log in to the web host's billing page and check its status page. An unpaid or suspended hosting account looks similar from the outside.
- Try the site on mobile data instead of office Wi-Fi, and note whether the website, the email or both are failing. Different results on different networks suggest a recent DNS change that is still spreading.
If the lookup returns nothing for a country domain such as .uk, .au, .ae or .de, use the registrar's control panel for the same details.
What happens when a domain expires, and can I get it back?
Usually yes, if you act quickly: an expired domain goes through recovery stages before anyone else can register it. For generic domains such as .com, .net and .org, ICANN's Expired Registration Recovery Policy requires the registrar to send at least two notices, about one month and about one week before expiry. After expiry the registrar interrupts the domain's normal DNS resolution before deleting the name, which is the moment the website and email stop. During that interruption the registrar must let you renew, and must then restore resolution "immediately or as soon as is commercially reasonable".
How long a registrar holds an expired name before deleting it varies, so check its renewal terms. After deletion, the same policy requires every generic-domain registry to offer a Redemption Grace Period of 30 days. ICANN's status code list says the domain is purged from the registry five calendar days after that period ends. Recovery during redemption goes through your registrar and may carry an extra fee. These figures were checked on October 6, 2026.
Country domains are run by national registries with their own timelines, so ask the registrar. Paying an overdue renewal from the registrar's billing page is the one action in this article that is safe to take yourself.
Why do DNS changes take time, and why does email break when nameservers change?
DNS changes take time because every DNS answer is cached for a set period called the TTL (time to live). RFC 1035, the internet standard for DNS, defines TTL as the time a record "may be cached before the source of the information should again be consulted". Until that time runs out, networks around the world keep using the old answer. For nameservers the wait is longer: Amazon's documentation says registrars typically use a TTL of 24 to 48 hours for name servers, and that a nameserver change can take up to two days to take effect (checked October 6, 2026).
Why email is usually the first casualty
Email depends on MX records, which RFC 1035 describes as naming "a host willing to act as a mail exchange" for the domain. Those records live at the DNS host. When nameservers are switched to a new company, the new DNS host starts with only the records someone has entered there. If the website's record was added and the MX records were not, the site works and incoming email fails, and senders may see delays or bounce messages.
What should I not change myself?
Do not edit DNS records or nameservers yourself, even if the fix looks obvious. A wrong change is cached like a right one, so mistakes can take up to two days to clear.
- Do not switch nameservers back and forth. Each switch starts the waiting period again.
- Do not lower the TTL hoping to speed things up. Amazon's documentation states that changing the TTL now will not make a change take effect faster.
- Do not cancel the old registrar, DNS or hosting account. It may hold the only copy of your DNS records.
- Do not start a second transfer or change the registered owner's details while the problem is open.
- Do not delete and recreate mailboxes, and do not restore backups. The data is rarely the problem.
When should I call a developer, and what should I have ready?
Call a developer when the nameservers have changed and records need rebuilding, when the status shows a hold you cannot explain, when the domain is in redemption, or when everything looks correct and the site is still down after 48 hours. Have this ready:
- The domain name, the registrar's name and who holds the login.
- A screenshot of the lookup result: expiration date, status and nameservers.
- Where DNS was hosted before and where it is now, plus the web host and email provider.
- When it stopped working and what changed just before.
- The exact error text from the browser and any email bounce message.
- Any export or screenshot of the old DNS records.
How do I stop this happening again?
Keep the registration paid, documented and in the company's name. Turn on auto-renew with a valid card and add renewal dates to a shared calendar. Use a shared company mailbox as the registrar contact, so notices do not go to a former employee or agency. Keep a one-page record of who your registrar, DNS host, web host and email provider are. Before any transfer, have the full DNS record list exported, and move DNS before moving the registration, not at the same time. This belongs in a routine software maintenance and support arrangement.
Quick answers
Why did my website go down after a domain transfer?
A domain transfer usually breaks a website when the old registrar was also hosting the DNS records and stopped doing so during the transfer. The registration moved, but the records that point to the website and email were left behind.
How long do DNS changes take to work?
A DNS change takes effect as cached copies expire, which is set by each record's TTL. Nameserver changes can take up to two days, because registrars typically use a TTL of 24 to 48 hours for name servers, according to Amazon Route 53 documentation checked on October 6, 2026.
Can I get an expired domain back?
Usually yes, if you act quickly. For generic domains such as .com, ICANN policy requires registrars to let you renew after expiry before deletion, and registries must then offer a 30-day Redemption Grace Period, which may involve an extra fee.
Why is my website working but my email is not?
Email uses separate DNS records called MX records. If the nameservers were changed and only the website's record was added at the new DNS host, the website loads while incoming email fails.
How do I check whether my domain has expired?
Enter the domain at lookup.icann.org and read the expiration date and status, or log in to your registrar's control panel. A status of redemptionPeriod or pendingDelete means the domain expired and was deleted.
Conclusion
A site or mailbox that disappears after a transfer, a lapsed renewal or a DNS change is rarely lost. Find out whether the registration expired, whether the nameservers changed and whether the email records were carried across, renew if a payment was missed, and leave the DNS settings alone until someone who understands them can look.
If you have no developer available, you can contact Entrant Technologies and we will take a look.