How to Check a Domain's Mail Server MX Records

Email for a domain isn’t arriving, or you’re setting up a new mail provider and need to confirm the DNS records actually point where they should — either way, the MX records are the first thing to check. They’re the DNS entries that tell the internet which mail servers are responsible for receiving email on behalf of a domain, and a misconfigured or missing one is a common, quiet cause of mail simply never arriving.

Reading MX records correctly means understanding both the host each record points to and its priority — two servers can both be listed as valid mail destinations for the same domain, with priority determining which one gets tried first.

What MX records actually specify

An MX (Mail Exchange) record is a DNS entry that specifies which mail server should receive email for a domain, paired with a priority value — lower priority numbers are tried first, and a domain can list multiple MX records as fallbacks in case the primary server is unavailable. This is different from an A record, which points a domain to a web server’s IP address; MX records exist specifically to route email, separately from how a domain’s website resolves.

A domain with no MX records configured generally can’t receive email at all, which is why checking for their presence and correctness is one of the first steps in diagnosing an email delivery problem, whether you’re migrating providers or troubleshooting an existing setup.

Why people get stuck here

• MX records are easy to overlook during a domain or provider migration. Moving a website’s hosting doesn’t automatically carry over mail routing — MX records need to be set correctly and separately, and it’s an easy step to forget.
• Priority values are sometimes misread or misconfigured. Lower priority numbers mean higher preference, which is the opposite of what some people intuitively expect from a “priority” number.
• DNS propagation delays complicate immediate verification. After changing MX records, it can take time for the change to propagate across DNS resolvers, and checking too soon can show outdated results that look like the change didn’t take.
• Confusing MX records with other DNS record types. MX, A, and CNAME records serve different purposes, and troubleshooting the wrong record type wastes time without addressing the actual mail delivery issue.

What a good MX lookup tool looks like

Presents priority and host in a clear table

Since both values matter together for understanding mail routing, a clear side-by-side table format makes it immediately obvious which server is primary and which are fallbacks.

Reflects the current, actual DNS state

An accurate, up-to-date lookup is essential for trusting the result during a real troubleshooting session, rather than working from a stale or cached assumption.

Requires no technical DNS tooling setup

Being able to check MX records directly through a simple web interface, without using a command-line DNS tool, makes the check accessible during a quick troubleshooting session.

Common mistakes to avoid

• Forgetting to configure MX records after migrating a domain to a new host or mail provider, breaking mail delivery until it’s caught.
• Misreading priority values, assuming a higher number means higher preference when it’s actually the reverse.
• Checking MX records immediately after a change and assuming a stale result reflects the current state, without accounting for DNS propagation delay.
• Troubleshooting a mail delivery issue by checking the wrong DNS record type entirely, wasting time before reaching the actual MX records.

How to do it with MX Lookup

Online Tool Store’s MX Lookup looks up how a domain’s MX records would be reported, with a clear priority and host table, entirely in your browser.

1. Enter the domain you want to check.
2. Review the reported MX records in the priority and host table.
3. Confirm the primary and fallback servers match what you expect from your mail provider’s setup.
4. Use the result to diagnose a delivery issue or verify a recent DNS change.

Because it presents priority and host together in a clear table, you can quickly confirm whether a domain’s mail routing is configured correctly without a command-line DNS tool.

Frequently asked questions

What does MX record priority actually mean?

Lower priority numbers are tried first — a record with priority 10 is preferred over one with priority 20. It’s the opposite of what “priority” might intuitively suggest, which is a common point of confusion.

Why doesn’t my MX record change show up right away?

DNS changes take time to propagate across resolvers worldwide, so checking immediately after a change can show outdated results. Waiting and rechecking after some time gives a more accurate picture of the current state.

Can a domain have multiple MX records?

Yes — multiple MX records with different priorities are common, acting as fallbacks in case the primary mail server is unavailable, ensuring mail delivery has a backup path.

Final thought

MX records are foundational to whether a domain can receive email at all, and they’re an easy thing to overlook during a migration or provider change. Check the priority and host table, account for DNS propagation delay, and confirm the setup matches what your provider actually needs.

Try the free MX Lookup