Skip to content

MX Record Lookup

Look up MX records for any domain online. Free MX lookup tool showing mail server priorities, email providers, and SPF/DMARC records.

Email ToolsWeb & SEO
Instant results

How to Use MX Record Lookup

1

Enter domain name

Type the bare domain such as example.com without any 'http://' or 'www' prefix. The tool then issues a DNS query for the MX records.

2

View MX records

Results come back as priority and hostname pairs. The lower priority numbers are tried first by sending mail servers, and multiple entries provide redundancy in case the primary host is unreachable.

3

Identify provider (auto)

The tool recognizes the hostname patterns of common providers — Google Workspace, Microsoft 365, Mailgun, SendGrid — and labels them automatically. This is handy for vendor audits and quick deliverability troubleshooting.

4

Verify configuration

Compare what you see against the records your email provider expects. A mismatch usually points at misconfiguration, the wrong provider, or DNS that hasn't finished propagating from a recent change.

When to Use MX Record Lookup

Email deliverability troubleshooting

When emails go missing or bounce, the MX records are usually the first thing to check. They tell you exactly which servers receive mail for a given domain, so a quick lookup often reveals whether the issue is a misconfigured handler, a stale DNS entry, or a third-party email service that has stopped responding.

Email service migration

When you cut over from Gmail to Office 365 (or any other provider), MX changes are what actually flip the switch. Running this lookup against your domain confirms the new records have propagated and that mail is flowing to the right place rather than the previous host.

Spam investigation

A suspicious sender domain often gives itself away through its MX records. Pulling them up shows whether the domain is backed by a legitimate provider like Google or Mailgun, or whether it points at a disposable mail handler that's a hallmark of throwaway phishing infrastructure.

Domain audit

Mapping out which email services your organization actually relies on becomes straightforward with MX lookups across your domains. Auditors use this to build a vendor inventory, spot shadow IT, and decide where consolidation might cut costs.

MX Record Lookup Examples

Standard lookup

Input
Domain: example.com
Output
MX records: 10 mail.example.com, 20 mail2.example.com. Priority numbers (lower = higher priority).

A typical lookup returns one or more priority and hostname pairs. The lower the number, the more preferred that server is. Multiple entries exist so that if the primary mail handler is unreachable, sending servers can fall back to the next one in line.

Common providers

Input
company.com using Google Workspace
Output
MX: 1 ASPMX.L.GOOGLE.COM, 5 ALT1.ASPMX.L.GOOGLE.COM, 5 ALT2.ASPMX.L.GOOGLE.COM, 10 ASPMX2.GOOGLEMAIL.COM, 10 ASPMX3.GOOGLEMAIL.COM

The hostnames Google Workspace uses are unmistakable, and Office 365 (mx.protection.outlook.com), Mailgun (mxa.mailgun.org), and SendGrid (mx.sendgrid.net) follow similar fingerprints. A glance at the records tells you which provider is on the other end.

No MX records

Input
Domain without email
Output
No MX records found. Domain doesn't accept email or uses A record fallback (legacy).

Plenty of domains aren't set up to receive mail at all and simply have no MX entries. Mail aimed at them bounces. A handful of older configurations rely on the A-record fallback the RFC permits, but that's rare on modern setups.

Tips & Best Practices for MX Record Lookup

  • 1.Subdomains can carry their own MX records, so mail.example.com might route somewhere completely different from example.com itself. Always query the exact host you care about rather than assuming the parent domain's records apply.
  • 2.Priority numbers are exactly what they sound like. Lower wins, ties get load-balanced, and the redundancy list exists so a temporarily unreachable primary doesn't take your mail down with it.
  • 3.You can usually identify the provider at a glance once you know the patterns. Google's aspmx.l.google.com, Microsoft's mx.protection.outlook.com, Mailgun's mxa.mailgun.org, and SendGrid's mx.sendgrid.net all show up regularly.
  • 4.MX is the explicit, modern way to route mail; the A-record fallback is a quirk of older specs that very few servers still honor. If you see only an A record, expect deliverability problems.
  • 5.DNS changes don't take effect instantly. The TTL on the previous record dictates how long the old value sticks around in caches, often 24 to 48 hours, so plan email migrations with that window in mind.
  • 6.MX is only one piece of the email-authentication puzzle. SPF lists who's allowed to send for you, DKIM signs outbound messages, and DMARC ties the two together. A full audit pulls all four.

Frequently Asked Questions

MX (Mail Exchange) records are DNS entries that tell sending mail servers which hosts handle incoming email for a domain. Each record has a priority number and a hostname, so a record like '10 mail.example.com' means 'try this server with priority 10'. Multiple records exist so a primary mail server can fail over to a backup without losing mail.