Network & DevOps ToolkitMX Record Lookup
Which servers receive this domain's email — with priorities and TTLs.
Enter a domain (not an email address) — the MX record type is pre-selected.
Loading…
Reading MX results
- Lower priority wins. Mail is delivered to the lowest-number host first; the higher numbers are fallbacks.
10 aspmx.l.google.combeats20 alt1.aspmx.l.google.com. - Recognize the fingerprints:
*.l.google.com= Google Workspace,*.mail.protection.outlook.com= Microsoft 365,*.mx.cloudflare.net= Cloudflare Email Routing. - No MX records? Mail falls back to the domain's A record — usually a misconfiguration worth fixing explicitly.
- After a mail migration, stale TTLs mean old servers keep receiving mail until caches expire — that's what the TTL column tells you.
Why is mail to my domain bouncing even though MX records exist?
Check that the MX targets resolve (look them up as A records here) and aren't behind a firewall on port 25. A common failure is an MX pointing at a host that no longer exists.
Can an MX record point to an IP address?
No — the standard requires a hostname. Some servers tolerate IPs, but many reject them; always point MX at a name with its own A/AAAA record.
What does MX priority 0 mean?
It's valid and simply the highest priority. A single '0 example.com' MX is fine; Null MX (RFC 7505) uses '0 .' to declare the domain accepts no mail at all.
Related tools
- TXT / SPF Lookup — the other half of email deliverability.
- DNS Lookup — all record types for any domain.
- NS Lookup — verify who's authoritative before you blame the records.
🔐 DNS queries are answered server-side by this site's own resolver API and are not logged. Every other tool on this site runs entirely in your browser.