MX Record Lookup - Free Mail Server Checker

Use our MX record checker to instantly see which mail servers handle your email. Verify DNS settings to ensure smooth delivery and prevent bounce issues

Global DNS propagation takes up to 48 hours!

Track global results with a DNS propagation checker!

An MX record lookup shows which mail servers accept email for a domain and in what order they are tried. Use it to confirm a new email provider is set up, to find out who hosts a domain's email, or to diagnose mail that bounces or never arrives.

What is an MX record?

An MX (mail exchange) record is a DNS record that names a mail server for a domain, together with a priority number. When someone emails [email protected], their mail server looks up the MX records for example.com and delivers to the server with the lowest priority number, falling back to the others if it can't connect.

How to check MX records

  1. Enter the domain part of the email address, e.g. example.com for [email protected].
  2. Choose a DNS server, or leave it on Google.
  3. Click Search to list the MX records with their priority and TTL.

From a terminal, the equivalent is dig example.com MX or nslookup -type=mx example.com.

Understanding your results

  • Priority: lower numbers are tried first. Records with the same priority share the load.
  • Value: the mail server's hostname. It must have its own A or AAAA record; check it with an A Lookup.
  • TTL: how long resolvers may cache the record. After changing provider, old MX records can be used until it expires.
  • A single record 0 . is a "null MX": the domain explicitly does not accept email.

The hostnames usually reveal the provider:

MX hostname looks likeEmail provider
smtp.google.com or aspmx.l.google.comGoogle Workspace / Gmail
example-com.mail.protection.outlook.comMicrosoft 365 / Exchange Online
mx.zoho.com, mx2.zoho.comZoho Mail
mail.protonmail.chProton Mail

Common MX record problems

  • No MX records. Senders may fall back to the domain's A record, which usually isn't a mail server, so mail fails or bounces.
  • MX points to an IP address. The value must be a hostname. Create an A record such as mail.example.com and point the MX at that.
  • MX points to a CNAME. This isn't allowed by the DNS standards, and some sending servers will refuse to deliver.
  • Old provider's MX left in place. After a migration, any leftover record means some mail still goes to the old mailbox. Remove it, then confirm with the DNS Propagation Checker.
  • Mail arrives but your replies go to spam. MX only controls incoming mail. Outgoing mail depends on SPF, DKIM and DMARC, plus the sending IP's reverse DNS and blocklist status.

Frequently asked questions

How many MX records should a domain have?

As many as your email provider tells you to publish. Some providers use one hostname that is highly available behind the scenes; others give two or more with different priorities. Don't add a backup MX unless it is actually configured to accept your mail.

What MX priority should I use?

Copy the values your provider gives you. Only the relative order matters: a record with priority 10 is tried before one with 20, and records with equal priority are used in turn.

How long do MX record changes take?

Until the old record's TTL expires in every resolver's cache, often between a few minutes and a day. Lowering the TTL before you switch provider shortens the overlap.

Can an MX record point to an IP address?

No. An MX record must point to a hostname, and that hostname must have an A or AAAA record. It also must not be a CNAME.