// how to fix
No MX record on your domain
MX records tell the world where to deliver email for your domain. Without them, you cannot receive replies, and some receivers distrust your emails.
What it means
MX (Mail Exchanger) records are DNS records that say which servers receive email for your domain. When someone writes to contact@yourdomain.com, their server looks up your MX records to know where to deliver it.
Your domain has none, or its MX records point to names that do not exist.
Why it matters
- Nobody can email you: replies to your emails are lost.
- Bounce messages (delivery failures) cannot reach you, so you never learn about problems.
- Some receivers distrust senders whose domain cannot receive email, and may filter their messages.
How to check
Type your domain in the Domain scanner at /domain-scanner. The MX section lists your mail servers and checks that each one has an address.
How to fix it
- Find your email provider's MX values. They are in its setup instructions or admin console.
- Open your DNS provider (often where you bought the domain).
- Remove old or wrong MX records, for example from a previous host.
- Add the new MX records with the priority given by your provider. A lower number means higher priority.
Google Workspace
Google now uses a single MX record:
yourdomain.com MX 1 smtp.google.com
Older setups with aspmx.l.google.com and several alternates still work.
Microsoft 365
The value is unique to your domain and shown in the Microsoft 365 admin center under Settings, Domains. It usually looks like this:
yourdomain.com MX 0 yourdomain-com.mail.protection.outlook.com
Your web host or another provider
Hosting companies (OVH, IONOS, Hostinger…) give their own MX values in their email setup page. Copy them exactly.
Common mistakes
- An MX must point to a name, never directly to an IP address.
- That name must have an A (or AAAA) record. If it does not resolve, nobody can deliver to you.
- Do not point an MX to a CNAME.
- Some DNS providers add your domain automatically: check the final value does not end with your domain twice.
Domains that only send, or never use email
If a domain truly must not receive email, you can publish a "null MX", which clearly says so:
example.com MX 0 .
Be aware that replies and bounces will then fail. For a domain you send from, a working MX is better.
Check that it is fixed
DNS changes are not instant. Most are visible within a few minutes, but some providers take up to 24 to 48 hours.
Run the Domain scanner again: your mail servers should be listed with their addresses. Then send an email to your domain from another mailbox and confirm it arrives.
Check that it is fixed
DNS changes can take from a few minutes to a few hours. Then send a new test email or scan your domain again.
Related guides
- No SPF record on your domainYour domain does not say which servers may send email for it. Add one TXT record and receivers can tell your real emails from fakes.
- SPF error: too many DNS lookups (permerror)SPF allows at most 10 DNS lookups. Above that, the whole record breaks and receivers treat it as invalid. Here is how to slim it down.
- Several SPF records on one domainA domain must have only one SPF record. With two or more, SPF breaks for every email. Merge them into a single line.
- SPF fails: the sending server is not authorizedYour domain has an SPF record, but the server that sent your email is not in it. Find which service sent the email and add it.
- No DKIM signature on your emailsDKIM adds a digital signature that proves an email really comes from your domain. Turn it on in your email provider and publish its key in DNS.