Back to Tools

MX Record Lookup

Look up MX (Mail Exchange) records for any domain to see which mail servers handle its email. Essential for troubleshooting email delivery and verifying domain configuration.

About this tool

MX records are the DNS entries that tell the internet where to deliver email for your domain. If someone sends a message to you@yourdomain.com, their mail server queries DNS for your MX records, gets back a list of mail servers with priorities, and delivers to the highest-priority one that responds. Get this wrong and your domain simply can't receive email — messages bounce back to the sender with a "host not found" error.

How MX record priority works

Each MX record has two parts: a priority number and a mail server hostname. Lower priority numbers mean higher preference. If you have MX records with priorities 10, 20, and 30, mail servers try priority 10 first. If that server is down, they try 20, then 30. Most email providers give you multiple MX records for redundancy. Google Workspace, for example, uses five: aspmx.l.google.com (priority 1), alt1.aspmx.l.google.com (priority 5), and three more at priorities 10, 10, and 10.

What MX records tell you about a domain

MX records are public, so you can look up any domain's email provider. aspmx.l.google.com means Google Workspace. mail.protection.outlook.com means Microsoft 365. mx1.emailsrvr.com means Rackspace. This is useful for sales teams researching prospects, for deliverability debugging, and for verifying that a domain is set up to receive email before you send to it. Our email validator uses MX lookups as part of its verification process.

Common MX configuration problems

The most frequent mistake is pointing MX records to an IP address instead of a hostname — MX records must use hostnames. Another common issue: setting all MX records to the same priority, which causes random distribution instead of proper failover. If you've recently switched email providers (say, from Microsoft 365 to Google Workspace), stale MX records pointing to the old provider will cause messages to disappear silently. Always verify with our DNS propagation checker after making changes.

MX records and email authentication

MX records handle inbound mail, but they're closely related to your outbound authentication setup. The mail servers in your MX records should also be authorized in your SPF record if they send outgoing email (like auto-replies or forwarding). Make sure your entire email infrastructure — MX, SPF, DKIM, and DMARC — is consistent. If you're troubleshooting delivery issues, run a WHOIS lookup to check the domain's registration status and a blacklist check on your mail server IPs.

Frequently Asked Questions

What are MX records and why do they matter?

MX (Mail Exchange) records are DNS entries that specify which mail servers accept email for your domain. Without them, no one can send you email — their servers literally don't know where to deliver it. Every domain that needs to receive email must have at least one MX record, and most have several for redundancy.

What do MX priority numbers mean?

The priority number determines the order servers are tried. Lower numbers are tried first. If you have records at priority 10 and 20, senders always try 10 first and only fall back to 20 if the first server is unreachable. Multiple records with the same priority (like 10, 10, 10) get traffic distributed randomly between them, which is used for load balancing.

How can I tell which email provider a domain uses?

The MX hostnames give it away. Google Workspace uses aspmx.l.google.com and alt variants. Microsoft 365 uses *.mail.protection.outlook.com. Zoho uses mx.zoho.com. ProtonMail uses mail.protonmail.ch. Amazon SES uses inbound-smtp.*.amazonaws.com. Just look up the domain's MX records and match the hostnames.

What happens if a domain has no MX records?

Email to that domain will fail. According to RFC 5321, if there are no MX records, the sender should fall back to the domain's A record — but many modern mail servers don't implement this fallback, so in practice, no MX records means no email delivery. Some domains intentionally have no MX records because they only send email and never receive it.

Can MX records point to an IP address?

No. MX records must point to a hostname, never directly to an IP address. This is defined in the RFC and strictly enforced. The hostname in your MX record must itself have an A record (or AAAA for IPv6) that resolves to an IP. If you try to use an IP address directly, most mail servers will reject the record.

How long do MX record changes take to propagate?

It depends on the TTL (Time To Live) set on your old MX records. If the TTL was 3600 (1 hour), most DNS resolvers worldwide will pick up the change within 1-2 hours. Some propagate in minutes, others take up to 48 hours in edge cases. During the transition, some emails may go to the old server and some to the new one, so keep both active until propagation is complete.

I switched email providers but emails are still going to the old one. Why?

Almost certainly a DNS propagation issue. Your old MX records are cached by DNS servers around the world. Check the TTL on your old records — that's approximately how long it takes for the change to fully propagate. In the meantime, some senders will still deliver to the old server. Keep the old provider active for at least 48 hours after changing MX records to avoid lost mail.

Do MX records affect my ability to send email?

Not directly — MX records control inbound mail (receiving), while SPF, DKIM, and DMARC control outbound authentication (sending). But they're related: if your MX server also sends outbound mail (auto-replies, forwarding), that server's IP needs to be in your SPF record. And some spam filters check whether the sending domain has valid MX records as a basic legitimacy signal.

Compare email marketing software

Hands-on roundups to help you pick the right platform.