MX Record Propagation CheckerVerify your mail server change has reached every independent DNS resolver
- 7 independent networks
- Records + DNS flags
- No ads, no sign-up
Independent networks
7 public DNS networks, queried in parallel
Every test query is answered by these unaffiliated resolvers on separate networks and infrastructure. When they agree, you can trust the result.
- 8.8.8.8
Google Public DNS
Google LLC · North America
- 1.1.1.1
Cloudflare
Cloudflare, Inc. · Global Anycast
- 94.140.14.14
AdGuard DNS
AdGuard Software Ltd. · Europe
- 45.90.28.0
NextDNS
NextDNS, Inc. · Global Anycast
- 185.222.222.222
DNS.SB
xTom / Layer0 · Europe
- 223.5.5.5
Alibaba DNS
Alibaba Cloud · Asia
- 119.29.29.29
DNSPod
Tencent Cloud · Asia
How it works
A test query for flag propagation check, done right
Most checkers query a single resolver or a set of geographically labelled servers behind the same anycast network. isPropagated queries genuinely independent DNS operators and compares both their records and their response flags.
Enter a domain and run the test query
Type any domain, pick a record type (A, AAAA, CNAME, MX, TXT, NS and more), then run a single test query that fans out to every network at once.
We query independent global networks
Instead of asking one resolver, we ask several unaffiliated public DNS networks in parallel — across North America, Europe and Asia — so no single cache can mislead you.
Compare records and DNS flags
Each network returns its answer plus the DNS response flags (AD, CD, RA, RD, TC). We check that both the records and the flags agree before calling a domain propagated.
Read the propagation verdict
A clear consensus score shows how many networks resolved the record and whether their answers match — so you know the moment a change is live everywhere.
What is an MX record and why does propagation matter for email?
An MX (Mail Exchange) record tells other mail servers where to deliver email for a domain. Each MX record carries a hostname (the mail server) and a priority number — lower priorities are tried first. When you change email providers, update a custom mail gateway, or migrate to Google Workspace or Microsoft 365, you update your MX records.
MX propagation is one of the most critical DNS changes to verify, because email sent to your domain during propagation may be delivered to the wrong server. Worse, if the old mail server is already decommissioned, messages delivered there bounce. Running a propagation check before decommissioning the old mail infrastructure confirms the switch is safe.
Most MX-related outages happen because admins decommission the old server before propagation completes. This checker shows exactly which resolvers still return the old MX record so you can wait until they all agree before cutting over.
Reading MX record propagation results
The data field for each MX result shows the priority and hostname, for example "10 aspmx.l.google.com." When all resolvers return the same MX set with the same priorities, mail delivery is consistent worldwide. If any resolver still shows the old mail server, messages from senders whose ISP uses that resolver may still go to the old host.
For multi-record MX setups (e.g., a primary and a backup), all records must match across resolvers. This tool compares the full record set, not just individual entries, so a partial MX mismatch will show as records-inconsistent.
FAQ
Common questions about mx record propagation checker
How long does MX record propagation take?
MX propagation time equals the previous MX record's TTL. If your old MX records had a TTL of 3600, expect up to 1 hour. Before a planned email migration, lower the TTL to 300 seconds at least one TTL cycle in advance so the change propagates in minutes after the switch.
Can I receive email during MX propagation?
Yes, but delivery may split between old and new mail servers. Senders whose resolvers still hold the old MX will deliver to the old server; senders with refreshed caches will reach the new server. Both servers should remain active until propagation is complete to avoid bounces.
How do I check MX records for my domain?
Enter your domain in the input field above (e.g., example.com — no www), select MX from the record type dropdown, and run the test query. The results show the mail server(s) and priorities each of the 7 resolvers currently sees.
Why do my MX records show different priorities on different resolvers?
If resolvers return different MX records (not just ordering differences), the change is still propagating. Priority ordering between records of the same value is irrelevant — DNS allows any sort order. But different hostnames or different priority numbers indicate a genuine inconsistency.
I set up Google Workspace MX records but email is not working yet. What do I check?
First confirm MX propagation is complete using this tool — all 7 resolvers should return Google's MX records (aspmx.l.google.com and the alt*.aspmx hosts). Next verify SPF and DKIM are also propagated. Google Workspace requires both to deliver successfully without going to spam.