Skip to content

MX Record Lookup: How to Check and Read Mail Records

How to run an MX record lookup with dig, nslookup or a web tool, how to read priorities, and which results mean a domain cannot receive email.

Nov 16, 2026 5 min read 1,076 words
MX Record Lookup: How to Check and Read Mail Records
MX record lookup: how to check and read mail records
MX record lookup: how to check and read mail records

An MX record lookup tells you which servers accept email for a domain. It is the first thing to check when mail bounces, when a new domain will not receive messages, or when you want to know if an address on a list can work at all.

This guide shows three ways to run the lookup, how to read what comes back, and what the odd results mean.

What an MX record is#

MX stands for mail exchanger. It is a DNS record that names the server that receives email for a domain. When someone writes to jane@example.com, the sending server asks DNS for the MX records of example.com and delivers the message to the host it finds there.

Each record has two parts:

  • Priority (preference): a number. Lower numbers are tried first.
  • Mail server host name: the server that takes the mail, such as smtp.google.com.

If a domain has several records, the sender starts with the lowest number and moves up only when a server cannot be reached. Records that share a number are treated as equals. The rules sit in RFC 5321, the SMTP standard.

Three ways to run an MX record lookup#

With dig#

On macOS and Linux, dig is the usual tool:

dig MX example.com +short

The answer is a short list, one record per line:

10 mail1.example.com.
20 mail2.example.com.

The number is the priority. Drop +short for the full response, including the time to live (TTL).

With nslookup#

On Windows, nslookup ships with the system:

nslookup -type=mx example.com

It prints the same records in a more verbose layout.

With a web tool#

If you do not want a terminal, use a web lookup page. Many free DNS lookup sites show a domain's MX records in the browser. Web tools are handy for a one-off check. For many domains, script it with dig or use an API.

How to read the results#

Look at the host names first. They usually reveal the email provider.

Host name looks like Likely provider
smtp.google.com Google Workspace
aspmx.l.google.com Google Workspace, older setup
...mail.protection.outlook.com Microsoft 365
mx.zoho.com Zoho Mail
A host on the company's own domain Self-hosted, or a gateway in front of another service

Google documents (Workspace MX setup) a single record, smtp.google.com with priority 1, as the current option for Workspace, and notes that older accounts may still use legacy values that start with aspmx. If mail already works, there is no need to change those.

A gateway in front of the real mailbox is common. Security tools often sit first, so the MX host may name the gateway and not the mailbox provider.

Results that mean trouble#

An MX record lookup can return surprising answers. Here is what they mean.

  • No records at all. The domain may not receive email. By the older fallback rule, a sender may try the domain's address record instead, but you should not count on it.
  • A single dot as the host (0 .). This is a "null MX". The domain owner is saying it does not accept mail. Anything sent there bounces.
  • A host that does not resolve. The record exists, but the server name leads nowhere. Mail will bounce or sit in a queue.
  • An IP address instead of a name. MX records must point to a host name, not an IP. Fix it in the DNS panel.
  • Wrong priority order. If your backup has a lower number than your main server, the backup takes the mail first.

When mail is failing, the fix is nearly always in DNS: a typo in the host name, an old record left behind after a provider switch, or a missing record on a new domain.

Why sales teams care about MX records#

MX data is not only for admins. If you build lead lists, an MX record lookup is a cheap filter.

  • Dead domains. A domain with no mail servers cannot receive your outreach. Remove it before you send.
  • Provider targeting. Knowing a prospect uses Google Workspace or Microsoft 365 can shape your deliverability testing and your messaging.
  • Catch-all hints. Some mail setups accept every address. That makes a simple check look good when it is not. See the catch-all email verifier to deal with this case.

An MX check says the domain can receive mail. It does not say the mailbox exists. For that, run an email verifier, which tests the domain, the server and the mailbox in one pass. If you clean large lists, bulk verification saves time.

A quick troubleshooting routine#

When a domain will not receive mail, work through this list in order.

  1. Run the MX record lookup and confirm at least one record exists.
  2. Check each host name resolves to an IP address.
  3. Confirm the priorities make sense, with the main server lowest.
  4. Compare the records to what your email provider asks for.
  5. Wait for DNS changes to spread. Old values can live for as long as the TTL says.
  6. Test with a real message, and read the bounce text if it fails.

Also keep in mind that MX records are one part of a healthy mail setup. SPF, DKIM and DMARC decide whether the mail you send is trusted. The SPF checker is a good next stop.

FAQ#

What does an MX record lookup show?#

It lists the mail servers for a domain and their priorities. Lower priority numbers are tried first.

How do I find a domain's mail provider?#

Run the lookup and read the host names. Names that contain google, outlook or zoho point to those providers. A gateway may hide the final provider.

How long do MX changes take to apply?#

It depends on the TTL on the old record. Many are set to minutes or hours, but some resolvers cache longer, so allow up to a day before you judge a change.

Can a domain have no MX record and still receive email?#

Under the older rules, a sender may fall back to the domain's address record. Most modern setups publish proper MX records, so treat a missing record as a sign of a problem.

Does a valid MX record mean an email address is real?#

No. It shows the domain can take mail. The mailbox may still not exist, so verify the address itself.

// start free

See who Tomba finds at any company

Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.

Free plan · No credit card required · GDPR & CCPA

Share
0 clapsEnjoyed it? Give a clap.
AU

// about the author

Tomba Editorial Team

Was this helpful?