Amazon Route 53 DNS Propagation CheckerVerify your Amazon Route 53 DNS changes are 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.
How DNS propagation works for Amazon Route 53 domains
Amazon Route 53 is Amazon Web Services's managed DNS service. When you add, update, or delete a DNS record through Amazon Route 53, the change is applied to Amazon Route 53's authoritative nameservers immediately. However, resolvers around the world that have cached the previous record will not see the update until their cached copy expires — a period determined by the record's TTL (Time to Live).
Route 53 allows setting TTL per record, down to 0 seconds for health-checked failover records. The default for most record types is 300 seconds. Records with TTL=0 are served without caching, enabling near-instant propagation but increasing DNS query load.
To monitor propagation in real time, enter your domain in the tool above and select the record type you changed. The check queries 7 genuinely independent DNS networks — not just geographically labelled servers behind the same infrastructure — and shows you exactly which resolvers have picked up the new value and which are still serving the old one.
Amazon Route 53 DNS management and common propagation issues
DNS records are managed in the AWS Console under Route 53 → Hosted zones → [your zone]. Changes propagate through Route 53's global network within 60 seconds; external resolvers then pick up the change at their next TTL expiry.
Route 53 Alias records (used for root domains pointing to AWS resources like CloudFront or ALB) do not have a user-configurable TTL — they follow the target resource's TTL. Alias records are not visible as standard A records to external DNS checkers; they appear as A records with the resolved IP.
FAQ
Common questions about amazon route 53 dns propagation checker
How long does Amazon Route 53 DNS propagation take?
Route 53 pushes changes to its global nameserver network within about 60 seconds. External resolvers then update when their cached TTL expires. With a typical TTL of 300 seconds, most resolvers see the change within 5–10 minutes of the Route 53 change.
How do I check DNS propagation for my Amazon Route 53 domain?
Enter your domain in the input above and select the record type you changed (usually A for host changes, MX for email changes, TXT for SPF/DKIM). Run the test query to see what all 7 independent resolvers currently return. When they all agree on the new value, propagation is complete.
Why is my Amazon Route 53 DNS change not propagating?
The most common reasons are: the TTL on the previous record has not expired yet (resolvers cache the old value until then), the record was saved with an error in the value or hostname, or the change was made to the wrong zone (for example, editing records in Amazon Route 53 when nameservers point elsewhere). Confirm the record is correct in the Amazon Route 53 dashboard, then re-check with this tool after the TTL expires.
How long should I wait before assuming DNS propagation failed?
Wait at least one full TTL cycle beyond when you made the change. For a 3600-second TTL, that means at least 1 hour after saving. If records still differ across resolvers after two full TTL cycles, investigate the DNS configuration at the source rather than waiting longer.
Does this checker show DNS propagation from different countries?
Yes. isPropagated queries 7 independent resolvers operated by different organizations across North America (Google), Europe (AdGuard, DNS.SB), and Asia (Alibaba DNS, DNSPod). When all return the same value, your Amazon Route 53 DNS change is live worldwide — not just in one region.