What this check shows
MX records tell sending mail systems which servers accept email for a domain. Each record includes a hostname and a priority; lower numbers are normally attempted first.
A global comparison is useful after changing email providers, adding a backup mail exchanger or diagnosing why some senders still deliver to an old platform.
When to use it
- Email provider migrations
- Inbound mail delivery failures
- Incorrect MX priorities
- Removing obsolete mail servers
How to read the result
- The MX target should be a hostname, not an IP address, and that hostname must resolve independently.
- Different priority values are normal when a domain has primary and backup mail exchangers.
- No MX answer does not always prevent delivery because some senders may fall back to the domain A record, but publishing explicit MX records is safer.
Command examples
Use these dig commands when you need to compare DNSRadar with a terminal check or collect evidence for a DNS provider.
dig example.com MX +short
dig @1.1.1.1 example.com MX
dig mail.example.com A +shortQuestions
Does a lower MX number mean higher priority?
Yes. A sender normally attempts the lowest preference value first.
Can MX propagation affect only some senders?
Yes. Sending systems use different recursive resolvers, so cached MX answers can expire at different times.
Related DNS tools
Check DNS records worldwide across independent public resolvers for A, AAAA, CNAME, MX, TXT, NS, SOA, PTR, SRV and CAA answers.
Check DNS propagation worldwide and compare record values, status and latency across independent global DNS resolvers.
Run a global A record lookup to check IPv4 addresses, TTL values and propagation across independent DNS resolvers.
Check AAAA records worldwide to verify IPv6 addresses, propagation, TTL behavior and resolver differences before or after a dual-stack change.
Check CNAME records worldwide, compare canonical targets across public DNS resolvers and detect stale aliases after CDN, SaaS or hosting changes.
Check TXT records worldwide for SPF, DKIM, DMARC and domain verification, and compare long DNS text values across independent resolvers.