Email Tools

MX Record Checker

Check a domain's mail server (MX) records and their priority.

Not sure what to enter? Try an example: gmail.com

Free & instant No signup How to use FAQ

Enter a domain to check its mail server (MX) records and their priority.

What is an MX record?

An MX (mail exchanger) record is a DNS record that names a mail server responsible for accepting email for a domain, together with a priority number. Sending servers look up a domain's MX records and deliver to the server with the lowest priority number first, falling back to the others if it cannot be reached.

How to check a domain's MX records

Enter the domain, for example example.com, in the box above.
Click Check MX Records.
Compare the mail server hostnames with the values your email provider tells you to publish.
Check the priorities: your main server should have the lowest number.
Run the SPF, DKIM and DMARC checks as well, since MX records alone do not stop others from spoofing the domain.

Related checks

For a plain list of MX records and a guide to recognising the email provider, use the MX Record Lookup.
See MX, SPF, DKIM and DMARC scored together in the Email Security Summary.
MX records are served by the domain's nameservers - check which ones with Nameserver Lookup.

The result lists every MX record published for the domain with its priority number and mail server hostname. Mail is delivered to the lowest number first; higher numbers are fallbacks that are only tried when that server cannot be reached. This checker looks at MX records from an email-security point of view: a domain can have perfectly valid MX records and still be easy to spoof if its SPF, DKIM or DMARC records are missing, so it is worth checking those too. If no MX record is returned at all, the domain cannot reliably receive email. JustChecker tracks your email deliverability configuration continuously.

Frequently Asked Questions

They check the same underlying MX record data - this version is grouped with the other email-security tools as part of a broader mail-deliverability workflow, alongside SPF, DKIM, and DMARC.

While priority itself is primarily about delivery routing/redundancy rather than security, a domain's complete mail setup (MX plus SPF plus DKIM plus DMARC) needs to be evaluated together - MX simply confirms where mail is even supposed to be delivered before authentication is checked.

Technically the DNS records can exist independently, but without an MX record the domain can't actually receive any email at all - the authentication records would be effectively moot since there's no mailbox to deliver validated mail to.

Often yes - major providers (Google Workspace, Microsoft 365, and others) use recognizable, distinctive MX hostname patterns, making the provider identifiable directly from the MX record values.

A domain used purely for a website (with email handled entirely through a different, separate domain) has no functional need for an MX record - this is a deliberate, valid configuration, not necessarily an oversight.

It provides redundancy if your primary mail server is temporarily unreachable, but modern managed email providers often handle this redundancy internally - a backup MX is more commonly seen with self-hosted mail infrastructure.

Share this tool:

Need a website for your business? Only $599