Multi-Region MX DNS Propagation Checker
Test MX DNS propagation across multiple worldwide DNS servers in North America, Europe, Asia, and Oceania.
| Domain | Type | Primary NS | Responsible Person | Serial | Refresh | Retry | Expire | Minimum | TTL |
|---|
| Name Server | IP Address | TTL |
|---|
| Domain | Type | TTL | Record Value |
|---|
| Trace Result |
|---|
| Domain | Type | Record | Status |
|---|
| Domain | Type | Record | Status |
|---|
MX Record Propagation Checker
MX records tell other mail servers where to deliver email for your domain. Each one has a priority number and a mail server hostname, and senders try the lowest number first.
When you move email to a new provider such as Google Workspace or Microsoft 365, the MX records are what switch delivery over. This checker asks your authoritative name servers for the MX set from eight regions. It lists every priority and hostname each region receives, sorted the same way, so the lists can be compared line by line.
Reading MX Results
Same hosts and priorities everywhere
The new mail routing is published. Sending servers that looked up your MX earlier keep using their cached copy until its TTL expires. Keep the old mailbox accepting mail for at least that long so nothing is lost in the handover.
A region still lists the old provider
One of your name servers has not picked up the change. Until it does, senders routed to that server can deliver to the old system. Check the NS records and have the DNS provider resync the lagging server.
Same hosts, different priorities
The zone was edited while its copies were out of step. Mail may go to a backup server first, which usually means slower delivery rather than loss.
No MX record anywhere
Without MX records, senders fall back to the domain's own A record, which is rarely a mail server. Treat a missing MX as an error unless the domain is meant to receive no mail.
Common MX Mistakes
Pointing MX at an IP address or an alias
The MX target must be a hostname with its own A or AAAA record. An IP address is not valid in an MX record, and the target should not be a CNAME. Some senders tolerate these errors, but many reject or delay the mail.
Old and new hosts mixed together
Leaving the previous provider's hosts in the MX set splits incoming mail between two systems, and messages seem to go missing. After a migration every region should list only the new provider's hosts.
Domains that never receive mail
A domain used only for sending can publish a single "null MX" (priority 0 with a target of a single dot). It tells senders not to try delivery at all. Do not combine it with other MX records.
How This Check Works
Eight Regions Across Six Continents
Every check is run from South Asia (Mumbai), Southeast Asia (Singapore), East Asia (Tokyo), the Middle East (Dubai), Europe (London), North America (N. Virginia), South America (São Paulo) and Oceania (Sydney). Each location reports on its own, so one slow or unreachable region never hides the results from the others.
Response Time and Fastest Region
Each region asks the authoritative name servers directly and times only that one exchange. Authoritative servers do not answer from a cache, so every figure is a fresh lookup from that part of the world. The Fastest Region in the summary panel is the lowest of those times in the current check.
Ticks, Crosses and the Map
A green tick means the region received an answer and shows it. A red cross means it got none; hover the marker to see why, such as NXDOMAIN, a timeout or no record of that type. The world map below the results marks each region with its outcome, so you can tell whether a problem is limited to one continent.
Global Propagation Troubleshooting & Common Fixes
After migrating to a new server or hosting provider, some global locations resolve the new IP while others return the old address. When authoritative nameservers answer with conflicting data, it usually means secondary (slave) nameservers have not received zone updates due to delayed AXFR/IXFR zone transfers, firewall restrictions, or an unchanged SOA serial number.
When six or seven regions return green checkmarks with valid responses, but one region (such as São Paulo, Sydney, or Dubai) displays a red cross or connection timeout, this indicates regional packet loss, firewall geo-blocking, or routing blackholes between that region's network and your authoritative nameservers.
Seeing different IP addresses across North America, Europe, and Asia is frequently expected behaviour rather than an error. Modern Content Delivery Networks (Cloudflare, Fastly, Akamai) and cloud load balancers use latency-based routing, Geo-DNS, or Anycast BGP to deliver traffic to the nearest geographic edge node.
Check Another Record Type
- A record propagation: after moving a website to a new server or IP address.
- CNAME record propagation: after pointing www, a subdomain or a service verification name at another host.
- NS record propagation: after changing name servers at your registrar or moving DNS hosting.
- PTR record propagation: after your server provider sets reverse DNS for a mail server IP.
- Multi-region DNS check overview: how the eight-region check works and which record to pick.
