A Record Propagation CheckerVerify your IPv4 address record 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.
What is an A record and why does propagation matter?
An A record is the most fundamental DNS record type — it maps a domain or subdomain to an IPv4 address, telling the world which server handles requests for that name. Whenever you move to a new host, update a server IP, or point a domain at a load balancer, you change its A record.
Until every resolver around the world flushes its cache, some visitors will still be routed to the old IP. That gap — from the moment you save the change to the moment every network returns the new address — is A record propagation. Its length depends almost entirely on the previous record's TTL: a TTL of 3600 means resolvers may hold the old value for up to an hour; a TTL of 86400 can delay full propagation by up to 24 hours.
Use this checker after pointing a domain at a new server, migrating to a CDN, or failingover to a standby IP. Re-run it every few minutes until all 7 independent networks agree on the same address.
How to read the A record propagation results
Each resolver card shows the IPv4 address it currently returns, the TTL remaining on that cached answer, and the DNS response flags it set. When all resolvers show the same IP address, your A record has propagated fully.
If resolvers disagree on the IP, the change is still spreading. The resolver still returning the old IP is caching it until its TTL expires. Lowering the TTL before a planned migration to 300 seconds (5 minutes) ensures the old value expires quickly and new resolvers pick up the change fast.
FAQ
Common questions about a record propagation checker
How long does an A record take to propagate?
The propagation time equals the TTL of the previous A record. A TTL of 3600 means up to 1 hour; 86400 means up to 24 hours. Most modern providers default to 3600 or lower, so the majority of A record changes are fully propagated within 1–2 hours in practice.
How do I check A record propagation from multiple locations?
This tool sends the same A record lookup to 7 independent resolvers — Google, Cloudflare, AdGuard, NextDNS, DNS.SB, Alibaba DNS, and DNSPod — covering North America, Europe, and Asia. Enter your domain, select the A record type, and run the test query.
Can I speed up A record propagation?
Before making the change, lower the TTL to 300 seconds (5 minutes) and wait for the old TTL to expire so all caches hold the short value. Then make the change. With a 5-minute TTL, propagation completes in minutes rather than hours. After the change is confirmed, you can raise the TTL back to 3600 or higher.
What if some resolvers return NXDOMAIN for my A record?
NXDOMAIN means that resolver currently has no record for the name. This can happen during propagation if the registrar has not yet pushed the record to authoritative servers, or if the domain itself has no A record configured. Check your DNS provider's dashboard to confirm the record was saved correctly, then re-run the check.
Does the DNSSEC AD flag matter for A records?
Yes, if your zone uses DNSSEC. The AD (Authenticated Data) flag indicates a resolver has verified the A record's DNSSEC signature chain. If some resolvers show AD=true and others AD=false, DNSSEC propagation is still in progress or one resolver is not validating. This checker surfaces those differences so you can catch DNSSEC issues alongside record propagation.