MX points to an IP address
An MX record must name a hostname, not an IP. Pointing it directly at an IP is invalid and many senders will refuse to deliver. Create a hostname with an A record and point the MX at that.
// free tool, no signup
Free MX Record Lookup
Look up the MX records on any domain to see which servers receive its mail, in priority order, with each server's resolved IP addresses. It runs free in your browser over DNS-over-HTTPS, with no signup and nothing stored.
What is an MX record?
An MX (Mail Exchange) record is a DNS record that names the servers responsible for receiving email for a domain, each with a priority number. When someone sends mail to you@yourdomain.com, the sending server looks up yourdomain.com's MX records and delivers to the reachable server with the lowest priority value, falling back to higher numbers if it is unavailable. MX records govern inbound mail, where messages are received, which is separate from SPF, DKIM, and DMARC, which authenticate the mail you send. This lookup reads the live MX records, sorts them by priority, and resolves each mail server to its IP addresses.
How to read your result
- Priority
The preference number. Sending servers try the lowest value first, so a record at priority 10 is used before one at 20. Equal values share the load between servers.
- Mail server (the exchange)
The hostname that accepts mail for the domain, for example alt1.aspmx.l.google.com. It must be a hostname, not an IP address, and it should resolve to one or more A records.
- IP addresses
The addresses each mail server resolves to. A mail server with no A record cannot receive mail, which is a common and easily missed misconfiguration.
- No MX records
If a domain publishes no MX records, the SMTP standard says senders fall back to the domain's A record. Most domains that handle mail should publish explicit MX records rather than rely on this fallback.
Common problems and fixes
The mail server has no A record
If the exchange hostname does not resolve to an IP, mail cannot be delivered to it. Every MX target needs working A or AAAA records.
No MX records at all
With no MX, mail relies on the A-record fallback, which is fragile and often unintended. Publish explicit MX records for any domain that should receive email.
MX target is a CNAME
The hostname in an MX record should not be a CNAME; the standards require it to resolve directly to address records. Use a hostname backed by A or AAAA records instead.
Stale MX after a migration
After switching email providers, leftover MX records can route mail to a server that no longer accepts it. Remove old providers' MX records once the new ones are live.
// FAQ
Questions, answered.
What is an MX record used for?
It tells sending servers where to deliver email for your domain. Each MX record names a receiving mail server and a priority, and senders try the lowest priority that is reachable.
What does the priority number mean?
It is a preference, lowest first. A server at priority 10 is tried before one at 20, which acts as a backup. Two records with the same priority share the load roughly evenly.
Does MX affect whether my sent mail reaches the inbox?
No. MX controls inbound delivery to you. Whether the mail you send lands in the inbox depends on authentication and sender reputation. To test that, run a free inbox placement test.
Why does my domain show no MX records?
Either none are configured, or they were removed. Without MX, senders fall back to your A record, which is rarely what you want for a mail domain. Add MX records pointing at your email provider's servers.
Is the lookup live?
Yes. It queries current DNS over DNS-over-HTTPS directly from your browser, with no signup and nothing stored. Results reflect what senders see right now.
// before you hit send