MX Lookup
Find the mail servers that receive email for a domain, in the order senders will try them.
What this tool checks
The MX lookup queries the MX records of a domain through a public resolver (Cloudflare by default, or Google Public DNS or Quad9). MX records tell other mail servers where to deliver email addressed to someone@example.com. Enter only the domain, the part after the @.
The query is sent from our server over DNS over HTTPS, so the resolver never sees your IP address.
How to read the result
Each line of the answer shows:
| Column | Meaning |
|---|---|
| Name | The domain, for example example.com. |
| TTL | Seconds the resolver will keep this answer in cache. |
| Preference | Lower values are tried first. |
| Mail server | Host name of the receiving server. It must have its own A or AAAA records. |
Some typical patterns:
- One or two entries from the same provider, such as
mx1.mail.example.netandmx2.mail.example.net: a hosted mail service. The names usually tell you which provider handles the domain’s mail. - Several entries with different preferences: a primary and one or more backups.
0 .: a null MX, meaning the domain never receives mail.- No answer with status
NOERROR: the domain exists but publishes no MX. Senders will fall back to its A or AAAA record. NXDOMAIN: the domain does not exist. Check for a typo.
Checking a switch of mail provider
- Before the switch, note the current MX records and their TTL, and lower the TTL to 300 seconds if your DNS panel allows it.
- Make the change: remove every old MX record and add the new provider’s records exactly as documented.
- Run this lookup again. Your own resolver cache does not matter here, because the query goes through a public resolver; if you still see the old records, the resolver’s cache has not expired yet.
- Run the propagation checker with type MX. Once the authoritative nameservers show only the new records, the change is published.
- Update SPF to include the new provider and enable DKIM signing there, then check everything with the email checker.
Common problems and fixes
- Mail still arrives at the old provider after a switch. The old MX is still cached somewhere, or it is still published. Remove every old MX, then check the propagation checker with type MX: the authoritative nameservers show what you have published, the public resolvers show what may still be cached.
- Mixed records from two providers. If you left an old record in place with a low preference, some senders will keep using it. Keep only the new provider’s records.
- An MX pointing to an IP address or a CNAME. Both are invalid under RFC 2181 and RFC 5321. Point the MX to a host name with A or AAAA records.
- The MX target does not resolve. Look up its A and AAAA records with the DNS lookup. A target without addresses is a dead end.
- Messages are delivered but land in spam. That is not an MX problem. Receivers judge your outgoing mail by SPF, DKIM, DMARC and the reputation of your sending servers. Run the email checker to review them.
Going further
The MX record covers only incoming mail. A complete email setup also needs:
- SPF, a TXT record listing the servers that may send for the domain. Check it with the SPF checker.
- DKIM, a public key used to verify message signatures. Check it with the DKIM checker.
- DMARC, the policy for messages that fail. Check it with the DMARC checker.
- Reverse DNS for the IPs that send mail. Check it with the reverse DNS tool.
The email checker also confirms that each MX target resolves, and it checks MTA-STS and TLS-RPT, which protect mail in transit to your MX servers.
Read the MX record guide for syntax, examples and a full list of common mistakes.
Frequently asked questions
What does the number before each server mean?
It is the preference. Senders try the lowest number first and use higher numbers only if the lower ones cannot be reached. Servers with the same number share the load.
The lookup shows no MX records. Can the domain still receive email?
Possibly. RFC 5321 tells senders to fall back to the domain's A or AAAA record when there is no MX. Whether a mail server is actually listening there is another matter, so publish proper MX records if you expect mail.
What is MX 0 with a target of '.'?
That is a null MX (RFC 7505). It means the domain does not accept email at all. Senders should reject messages to it immediately rather than retry.
Can you test whether the mail server accepts messages?
No. This site runs on an edge platform that cannot open outgoing SMTP connections on port 25, so we check DNS only. To test delivery, send a message from an external account and read the bounce or the headers.