TXT Record Propagation CheckerConfirm SPF, DKIM, DMARC, and domain verification records are live everywhere
- 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 are TXT records and why verify their propagation?
TXT (text) records store arbitrary text data in DNS. They serve many purposes: SPF records define which servers are allowed to send email for a domain, DKIM public keys enable signature verification, DMARC policies instruct receivers how to handle unauthenticated mail, and domain verification strings prove ownership to Google Search Console, Cloudflare, and other platforms.
TXT record propagation determines when these policies and verifications actually take effect. An SPF record that has not finished propagating means some receiving mail servers may not yet honour it, potentially allowing spam to slip through or causing legitimate mail to fail authentication. A domain verification TXT record that has not propagated will fail the ownership check.
Because TXT records at a single name can stack (multiple TXT values are allowed), checking propagation is especially important after modifying SPF — adding an include or updating an IP address. This tool shows the full TXT record set each resolver returns so you can confirm both the new value is present and the old one is gone.
TXT records and the records-consistent check
TXT propagation is considered complete when every resolver returns the identical set of TXT values for the queried name. If you have multiple TXT records (e.g., SPF plus a Google verification string), all must appear on all resolvers.
A common mistake is adding a second SPF record instead of updating the existing one. DNS allows multiple TXT records, but the SPF specification permits only one "v=spf1" value per name. If this checker shows two different "v=spf1" strings on a resolver, you have a duplicate SPF configuration that will cause mail failures.
FAQ
Common questions about txt record propagation checker
How do I check TXT record propagation for my domain?
Enter your domain in the input field, select TXT from the dropdown, and run the test query. For email-specific TXT records, use the SPF, DKIM, or DMARC quick-buttons below the search box — they pre-fill the correct domain prefix automatically.
Why is my TXT record not showing up on all resolvers?
The most common reasons are: the previous TTL has not expired on some resolvers (wait and re-check), the record was saved with a typo or on the wrong subdomain, or the DNS provider has a propagation delay from its own internal network to authoritative servers. Check that the record appears correctly in your DNS provider dashboard first.
How long does TXT record propagation take?
TXT propagation follows the TTL of the previous record (or the zone's negative-cache TTL for a new record). Most providers default TTLs to 3600 seconds (1 hour). Domain-verification TXT records are typically queried at the moment of verification, so they just need to be present on the authoritative server — not necessarily cached everywhere.
Can I have multiple TXT records on the same domain?
Yes — DNS allows multiple TXT records at a single name. They stack. The exception is SPF: while you can have multiple TXT values, the SPF spec requires exactly one "v=spf1" record. Having two SPF records causes the SPF check to return PermError, which can cause mail to fail.
What is the difference between checking TXT records at the root domain vs a subdomain?
SPF and DMARC live at different names: SPF is a TXT record on the root domain (example.com), DMARC is on _dmarc.example.com, and DKIM is on {selector}._domainkey.example.com. Enter the correct name in the search box, or use the email preset buttons which auto-fill the right prefix.