Skip to content
DMARC Pulse

MX lookup

MX Record Lookup

Look up a domain’s MX records to see which servers receive its email, in which order, and which provider hosts the mailboxes.

MX records decide where incoming email is delivered.

Example result

Sample data, not a live check. Run the tool above to see your own result.

Result for

acme.example

Looks good

Google Workspace
1
aspmx.l.google.com
142.250.153.26
Google Workspace
5
alt1.aspmx.l.google.com
142.250.150.26
Google Workspace
10
alt2.aspmx.l.google.com
74.125.200.26
Google Workspace

What we found

  • Mail is hosted by Google Workspace

    Detected from the MX host names.

  • 3 MX record(s) found

    The domain can receive email.

What to do with the result

MX records were found and every host resolves

Senders can find a destination for this domain. The check stops at DNS, so it cannot show whether those servers accept mail for your addresses.

  1. Compare each host and priority with the values in your email provider’s admin console.
  2. Send a test message from an outside account and confirm it arrives.

A dash under Provider means we do not recognize that host, which is not a fault by itself. If you run a single MX host yourself, plan for outages. While it is down, senders queue the message and retry for a limited time.

No MX records were found

If “MX lookup failed” appears too, a DNS query failed (a timeout or a server error such as SERVFAIL), so this result does not show whether the domain has MX records. We keep each result for 15 minutes, so check again after that. If it repeats, ask whoever runs the domain's DNS servers to check them.

Otherwise, confirm you entered the exact domain: mail.example.com does not inherit the MX records of example.com. Without MX records, senders try the domain’s own A or AAAA address (its IP addresses in DNS), often a web server.

To receive mail, publish the MX records from your provider. Caution: if a server at that address takes mail today, create the mailboxes at the new destination first.

Null MX: the domain does not receive email

The domain publishes a null MX, one record with priority 0 and host . that declares it accepts no mail. Senders that support it report the failure on the first attempt.

  • If the domain should receive mail, replace that record with your provider’s MX records.
  • If it is intentional, keep the domain out of your From and return-path addresses, because that mail risks being rejected. A domain that sends nothing can also publish this SPF record, which authorizes no server:

    v=spf1 -all

  • If the table lists hosts too, keep only one side. RFC 7505, section 3, forbids other MX records next to a null MX.

A host does not resolve, or the MX points to an IP address

A temporary DNS failure also shows as “does not resolve”, and we keep each result for 15 minutes. Check again after that.

If the error stays, senders skip that entry. If it is the only one, they cannot deliver. An MX record must name a host with an A or AAAA address (RFC 5321, section 5.1), and that host must not be a CNAME, an alias for another name (RFC 2181, section 10.3). Use your provider’s host name, or add the missing address record for your own server.

Caution: an MX edit reroutes inbound mail, so confirm first that the new host accepts your domain.

The MX records point to several providers

This usually follows an unfinished migration. Senders use the lowest priority number first and choose at random between equal numbers, so the other provider may receive part of your mail or all of it during an outage.

If both are deliberate, such as a filtering gateway or a contracted backup MX, stop here: those hosts are in use. The steps below apply only to a migration that was left unfinished.

  1. Confirm which provider holds your mailboxes today.
  2. Lower the TTL (how long resolvers may cache a record) and wait for the old value to expire.
  3. Remove the old hosts. Keep the old mailboxes open until the TTL has passed.

Before step 3, confirm that any MTA-STS policy (the hosts senders must reach over TLS) lists the hosts you keep. If SPF uses mx, removing a host also removes its authorization to send.

Explained

How an MX lookup works

When someone sends you email, their server runs an MX lookup on your domain and delivers to the host with the lowest priority number first, falling back to the next ones if it’s unavailable.

Common problems

  • MX pointing to an IP address instead of a host name.
  • A host that no longer resolves after a migration.
  • Old and new providers mixed after switching email services.

Frequently asked questions

How do I find a domain’s email provider?
Run an MX lookup. Host names like aspmx.l.google.com or *.mail.protection.outlook.com reveal the provider.
What does MX priority mean?
Lower numbers are tried first. Servers with the same priority share the load.
Do MX records affect sending email?
Not directly — they control receiving. Sending is authorized by SPF and DKIM.
What is a null MX?
A single MX record with priority 0 and host “.”, declaring that the domain accepts no email (RFC 7505).

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.

Related tools