Is it propagated yet?Test Query for Flag Propagation Check
A free DNS checker that compares records and header flags (AD, CD, RA) across independent global networks — confirm your change has propagated worldwide.
- 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 DNS propagation?
DNS propagation is the time it takes for a DNS record change — a new IP address, nameserver, mail record or TXT verification — to reach resolvers around the world. Until every resolver refreshes its cache, different networks can return different answers for the same domain.
A DNS checker helps you see that spread. isPropagated goes further: it runs a single test query for flag propagation check against several independent public DNS networks and compares both the records they return and the response flags they set. When the records match and the flags agree, your change has fully propagated.
Use it after switching hosts, updating nameservers, adding an SPF or DKIM record, or turning on DNSSEC — then re-run the check until every network reports the new value.
How the test query for flag propagation check works
The check sends the same DNS lookup to several independent resolvers at once and lines up the results side by side. Instead of trusting a single server, you compare the records each network returns and the header flags they set — AD (DNSSEC authenticated), CD (checking disabled), RA (recursion available), RD (recursion desired) and TC (truncated).
When every network returns the same record and agrees on the DNSSEC (AD) flag, your change has propagated worldwide. If the records differ, some resolvers are still serving a cached value — re-run the check until they all match. The RA, RD, CD and TC flags are per-resolver transport behaviors and can differ normally without indicating a propagation problem.
FAQ
DNS propagation, flags and this checker
What is a test query for flag propagation check?
It is a single DNS lookup sent to multiple independent resolvers at once to confirm that a record — and its DNS response flags — has propagated consistently. Instead of trusting one server, the test query compares answers across networks so you know a change is truly live everywhere.
What are DNS flags and why check them?
Every DNS response carries header flags: AD (Authenticated Data, meaning DNSSEC validated), CD (Checking Disabled), RA (Recursion Available), RD (Recursion Desired) and TC (Truncated). Comparing these flags across networks reveals DNSSEC or resolver issues that a plain record check would miss.
How long does DNS propagation take?
It depends on the record’s TTL and the resolvers caching it. Many changes appear within minutes, but some resolvers hold cached answers until the previous TTL expires — commonly up to 24–48 hours. Running this DNS propagation checker periodically shows you exactly when each network updates.
How is this different from other DNS checkers?
Traditional DNS checkers query many geographically labelled servers that often sit behind the same anycast network, so they can all return the same cached answer. isPropagated queries genuinely independent operators — Google, Cloudflare, AdGuard, NextDNS, DNS.SB, Alibaba and DNSPod — and compares all five response flags (AD, CD, RA, RD, TC), not just records.
Which DNS record types can I check?
You can run a propagation check for A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, SRV, PTR, DS and DNSKEY records. Choose the record type next to the search box before running your test query.
What does the CD flag option do?
Enabling CD (Checking Disabled) tells resolvers to skip DNSSEC validation and return data even if signatures fail. It is useful when debugging DNSSEC problems — compare a normal query with a CD query to see whether validation is the cause of a resolution failure.
Why do networks sometimes return different answers?
Mismatched answers usually mean the record is still propagating and some resolvers hold an older cached value. It can also be intentional — GeoDNS, load balancing or split-horizon DNS deliberately serve different records to different networks.
Is isPropagated free to use?
Yes. Running a DNS propagation check across every network is completely free, with no sign-up and no ads cluttering your results.