Email DNS Records Propagation CheckerVerify MX, SPF, DKIM, and DMARC are all live across independent global DNS networks
- 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.
Understanding email DNS records and propagation
Reliable email delivery depends on four DNS record types working together: MX records route incoming messages to the right mail server, SPF TXT records authorize outgoing sending IPs, DKIM TXT records enable cryptographic signing, and DMARC TXT records set policy for authentication failures. Each must be configured correctly and fully propagated before email flows reliably.
When you migrate email providers — from cPanel hosting to Google Workspace, from one SMTP gateway to another — you typically update all four record types at once. The propagation windows overlap but are independent: an MX change might propagate in 30 minutes while your old DKIM record takes an hour to expire. Running propagation checks on each record type separately gives you a clear picture of where you are in the migration.
Use the email record quick buttons (SPF, MX, DMARC, DKIM) below the search box for one-click access to each record type. Enter your domain once, then check each record in turn without re-typing the domain.
Email DNS propagation checklist for a provider migration
1. Before switching: lower TTLs on MX, SPF, and any DKIM records to 300 seconds. Wait one full TTL cycle so resolvers hold the short value. 2. Add new records at the new provider. 3. Update MX, SPF, and DKIM at your registrar/DNS host. 4. Monitor each record type with this checker until all 7 resolvers agree. 5. Only then decommission the old mail server and revoke the old DKIM key.
For DMARC, update the policy after the other three records have propagated and you have verified email is flowing correctly through the new provider. Moving to a stricter DMARC policy (p=quarantine or p=reject) before MX and DKIM propagation is confirmed risks legitimate mail being quarantined.
FAQ
Common questions about email dns records propagation checker
What is the correct order to set up email DNS records?
For a new setup: MX first (to route email), then SPF (to authorize sending), then DKIM (to sign messages), then DMARC (to enforce policy). Verify each one is propagated before moving to the next. For a migration: set up all records at the new provider first, then switch MX, keeping the old server live until propagation is confirmed.
How do I check all my email DNS records at once?
Enter your domain in the input above, then use the quick buttons: click MX for mail routing, SPF for sending authorization, DMARC for policy, and DKIM (with your selector) for signing. Each check runs across 7 independent resolvers giving you a global view of each record's propagation status.
My email stopped working after changing DNS. What should I check first?
Check MX propagation first — if the MX record is wrong or not yet propagated, no mail will be delivered. Then check SPF (look for the "v=spf1" TXT record on your root domain). If MX and SPF are correct, check that your old server is still accepting mail in case some resolvers are still routing to it during propagation.
Can email propagation cause mail to bounce?
Yes. If the old MX server is shut down before MX propagation completes, senders whose resolvers still return the old MX will attempt delivery to a server that no longer accepts connections, resulting in bounces or temporary delivery failures. Keep the old server active during the propagation window.