Google Workspace DNS Propagation CheckerConfirm MX, SPF, DKIM, and DMARC records for Google Workspace are live globally
- 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 DNS records does Google Workspace require and how long do they take to propagate?
Setting up Google Workspace (Gmail for your domain) requires several DNS records: MX records to route incoming email to Google's mail servers, a TXT-based SPF record to authorize Google's sending IPs, a DKIM TXT record to sign outgoing messages, and optionally a DMARC record to set enforcement policy. All four must be live globally for Google Workspace to work reliably.
The most time-sensitive change is the MX record switch. Until Google's MX records have propagated, incoming mail may still be delivered to your old mail server. Google Workspace recommends keeping the old mail server active until propagation is confirmed. This checker lets you verify MX propagation in real time so you know exactly when it is safe to decommission the old server.
For SPF, the required record is: v=spf1 include:_spf.google.com ~all. For DKIM, Google Workspace generates a key under the "google" selector — look it up at google._domainkey.yourdomain.com. Check each record type separately using the quick buttons or by selecting the appropriate record type.
Google Workspace DNS propagation checklist
Use this tool to verify each required record in order: (1) MX — all 7 resolvers should return aspmx.l.google.com with priority 1 and the alt1–alt4 servers. (2) SPF — confirm the single TXT record containing include:_spf.google.com. (3) DKIM — check the google._domainkey subdomain for the public key. (4) DMARC — verify the _dmarc subdomain if you've set a policy.
Google's DNS setup wizard in the Admin Console confirms each record as it propagates. For independent confirmation outside Google's own systems, use this checker — it queries genuinely separate resolvers to give you an unbiased view.
FAQ
Common questions about google workspace dns propagation checker
How long does Google Workspace DNS setup take to propagate?
MX records typically propagate within 1–4 hours. SPF and DKIM TXT records propagate within 1 hour. Google Workspace itself may take up to 72 hours to activate all features after DNS records are confirmed, but email routing begins as soon as MX propagation is complete.
Google Workspace says my MX records are not set up. What do I check?
First, use this tool to verify the MX records are live on all 7 independent resolvers. If the check shows the records are propagated, Google's verification system may have cached a previous state. Wait 15–30 minutes and re-verify in the Admin Console. If the checker still shows old MX records on some resolvers, propagation is genuinely incomplete.
Do I need a DMARC record for Google Workspace?
DMARC is not strictly required for Google Workspace to function, but it is strongly recommended. Google and Yahoo now require DMARC for bulk senders (2024 requirements). Even for low-volume senders, a p=none DMARC record enables reporting so you can monitor authentication results.
How do I verify Google Workspace DKIM is working after propagation?
After confirming the DKIM TXT record at google._domainkey.yourdomain.com is live using this checker, turn on DKIM signing in the Google Workspace Admin Console (Apps → Google Workspace → Gmail → Authenticate email). Then send a test email to a Gmail account and check the full headers for "DKIM=pass".