Email not arriving or not sending? A checklist for site owners

If your own domain’s email stops working, either nothing arrives or what you send lands in spam, and the cause is usually in the DNS records rather than in your mailbox. This checklist works from the simplest causes to the more technical ones. You can check most of it with our email checker and MX record lookup.

How email finds you

When someone sends a message to you@yourdomain.com, their mail system looks up your domain’s MX records in DNS. These list the servers that accept mail for you. The sender connects to one of them and hands the message over. If the records are missing, wrong or point to a service you no longer use, mail has nowhere to go.

Step 1: is the domain itself healthy?

  • Has the domain expired? An expired domain stops its DNS working, and email stops with it. See what happens when a domain expires.
  • Does the website load? If the whole domain has disappeared, email will not work either. Check with our website checker.
  • Were the name servers changed recently? New name servers need all your records recreated, including mail ones.

Step 2: check the MX records

Use the MX lookup to see what your domain publishes. You should see the servers your email provider told you to use. Common problems:

  • No MX records at all. Mail cannot be delivered.
  • Old provider’s records still present. Mail may go to the wrong place, or only some of it arrives.
  • Typos or wrong priority numbers. Lower numbers are tried first.
  • Records pointing at an address instead of a name, which is not permitted for MX.

After a change, allow time for caches to refresh. See what DNS propagation means.

Step 3: check SPF, DKIM and DMARC

These three records are how receiving servers decide whether a message from your domain is genuine. Without them, even legitimate mail is often sent to spam or refused.

  • SPF lists which servers are allowed to send mail for your domain. It is a TXT record that starts with v=spf1. A domain should have only one.
  • DKIM adds a digital signature to each message, which the receiver checks against a key published in your DNS. Your email provider supplies the record.
  • DMARC tells receivers what to do when SPF and DKIM checks fail, and where to send reports. A cautious starting policy is monitoring only, then tightening it once you are sure all your mail passes.

Step 4: if mail you send goes to spam or bounces

  • Read the bounce message. It usually says why in plain words, such as a failed SPF check or a blocked address.
  • Check that every service sending mail on your behalf, such as a newsletter tool or a contact form, is included in your SPF record and set up for DKIM.
  • Avoid sending from your domain through a service that has not been authorised.
  • Check whether the sending address is on a public block list, which can happen with shared hosting.

Step 5: if mail you expect does not arrive

  • Look in the spam or junk folder.
  • Check that the mailbox is not full or suspended.
  • Ask the sender for the bounce message if they received one.
  • Check filters and forwarding rules in your mailbox for something that diverts or deletes messages.
  • Check the email provider’s status page for an outage.

Step 6: the website form that sends you email

If it is a contact form on your website that has stopped sending, the likely culprits are a hosting change that blocked outgoing mail, a form plugin sending from an address that fails SPF checks, or an account password that changed. Sending through an authenticated mail service is more reliable than relying on the web server to send directly.

Prevent it happening again

  • Turn on auto-renew for your domain and keep contact details current.
  • Keep a copy of your DNS records, especially MX, SPF, DKIM and DMARC, somewhere outside your DNS provider.
  • Send yourself a test from an outside address after every DNS change.
  • Review your records after you add or remove any service that sends or receives mail.

Summary

Missing email almost always comes down to the domain, the MX records or the authentication records. Check that the domain is healthy, look up the MX records, confirm SPF, DKIM and DMARC are present and correct, and read any bounce message carefully. It tells you what the receiving server thinks is wrong.

Check a website now

Is it down for everyone, or just you? Paste an address and we test it from fifteen places.

Open the checker

Related guides

Last updated 2 November 2026. Written by the siteupdown.com team. Spotted a mistake?

← All help guides