Skip to content

How to Check MX Records: 4 Quick Methods and Fixes

Four quick ways to check MX records, how to read priority values, and the common problems that stop mail from being delivered.

Abedrahim B Nov 15, 2026 5 min read 1,166 words
How to Check MX Records: 4 Quick Methods and Fixes

When mail does not arrive, the first thing to check MX records is the domain's DNS. MX records tell the world which servers accept email for a domain. If they are missing, wrong or out of date, mail bounces or goes to the wrong place. This guide shows four quick ways to look up MX records, how to read the result and how to fix the most common problems.

How to check MX records for a domain
How to check MX records for a domain

TL;DR#

  • An MX record lists the mail servers for a domain, each with a priority number.
  • A lower number means a higher priority.
  • You can check MX records with dig, nslookup or a free web tool.
  • After a change, wait for DNS to update, then test again.

What is an MX record?#

MX stands for mail exchanger. It is a type of DNS record. When someone sends a message to you@example.com, their mail server asks DNS where to deliver mail for example.com. The answer is the MX record.

Each MX record has two parts:

  • A priority number. The server with the lowest number is tried first.
  • A hostname. This is the mail server that accepts the mail.

The rules for how mail servers use these records are set out in RFC 5321. For a broader view, see our guide to DNS and MX records for deliverability.

Why you should check MX records#

You may need to check MX records in several cases:

  • You just set up a new domain or a new mail service.
  • You moved from one provider to another.
  • People report that they cannot reach you.
  • You want to see which provider a company uses.
  • You are cleaning an email list and want to know if a domain can receive mail at all.

A domain with no MX records can usually not receive mail. That is a quick sign that an address on it will bounce.

Method 1: Use dig#

dig is a command line tool on macOS and Linux. It gives clear, raw DNS answers.

dig MX example.com +short

The output looks like this:

10 mx1.example.com.
20 mx2.example.com.

The first number is the priority. The second is the server name. Add @8.8.8.8 to the command to ask a specific DNS server, such as Google's public resolver.

Method 2: Use nslookup#

nslookup is available on Windows, macOS and Linux.

nslookup -type=mx example.com

Look for lines that say "mail exchanger". Each line shows the preference (priority) and the server name. The result is the same as dig, in a different layout.

Method 3: Use a free web tool#

If you prefer a browser, many sites run the lookup for you. Google's Admin Toolbox Dig is one simple option. Type the domain, choose MX as the record type and read the answer.

Web tools are handy when you do not have a terminal. They are also good for a second opinion, since they query from a different place.

Method 4: Check at scale while you verify emails#

If you need to know whether many domains can receive mail, checking one by one is slow. An email verifier tests the format, the domain and the mailbox in one step. It looks up the MX records for you and tells you if an address is likely to bounce. For a quick one-off test, the free email checker works well.

How to read the results#

Here is an example of a set of records for a domain.

Priority Mail server
10 mx1.mailhost.example.
20 mx2.mailhost.example.
30 mx3.mailhost.example.

Mail goes to the lowest number first. If that server is down, the sender tries the next one. Two records with the same number share the load.

You can often tell which provider a domain uses from the server names. A name that points to a known mail service shows where the mailboxes live. Use that clue with care, since a domain can sit behind a filter or a gateway.

Common MX record problems#

No MX record at all#

The domain has no mail servers listed. Mail to it may fail. Add the records your mail provider gives you.

Old provider records still there#

After a move, old records can linger next to the new ones. Mail may go to the old provider. Remove records you no longer use, and keep the ones your new provider asks for.

An MX that points to an IP address#

An MX record should point to a hostname, not an IP address. Replace it with the host name.

An MX that points to a CNAME#

MX targets should be hostnames that resolve directly. Pointing to an alias can cause failures with some servers. Use the real host name.

Wrong priority order#

If the backup server has a lower number than the main one, mail goes to the backup first. Check the numbers against your provider's guide. Our walkthrough on Google Workspace MX records shows a typical set.

Changes not showing yet#

DNS uses caching. A new record can take time to spread, depending on its TTL, the time to live. Wait, then test again from a different network or resolver.

After you check MX records, check the rest#

MX records only say where mail goes in. They do not cover how you send. For outgoing mail, review your SPF, DKIM and DMARC records too. The free SPF checker is a quick start. Missing authentication can send your mail to spam even when MX records are perfect.

A short checklist#

  1. Run dig MX yourdomain.com +short.
  2. Confirm the servers match your mail provider's guide.
  3. Check that priorities are in the right order.
  4. Remove old records from a previous provider.
  5. Send a test message to the domain and confirm it arrives.
  6. Check SPF, DKIM and DMARC for outgoing mail.

FAQ#

How do I check MX records for a domain?#

Use the dig or nslookup command, or a web tool such as Google's Admin Toolbox. Each returns the servers and their priorities. The steps above show the exact commands.

What does MX priority mean?#

It sets the order in which servers are tried. A lower number is tried first.

How long does an MX change take to work?#

It depends on the TTL of the old record and on resolver caches. It can be quick, or it can take longer. Check again after the old TTL has passed.

Can a domain work without MX records?#

Some mail servers fall back to the domain's address record, but you should not rely on that. Always set proper MX records.

Final thoughts#

To check MX records, run one command or open one web page. Read the priorities, match them to your provider and clean up old entries. Then confirm that mail actually arrives. When you work with lists, let a verifier run these checks at scale. Try the Tomba Email Verifier to test addresses before you send.

// 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.
Abedrahim B

// about the author

Abedrahim B

CEO

Was this helpful?