CNAME Record Propagation CheckerConfirm your domain alias is live across independent global DNS resolvers
- 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 a CNAME record and why check propagation?
A CNAME (Canonical Name) record creates an alias — it tells DNS that one hostname is actually another hostname. For example, www.example.com might be a CNAME pointing to example.com, or a custom domain on a CDN might be a CNAME pointing to a provider-managed hostname like yoursite.cdn.example.net.
CNAME propagation matters whenever you redirect a subdomain to a new target: switching CDN providers, pointing a custom domain at a SaaS platform (Shopify, Netlify, Vercel, Webflow), or configuring a branded email link tracker. Until the new CNAME value has propagated, some visitors will resolve the alias to the old target.
An important DNS rule: CNAMEs cannot coexist with other records on the same name — known as the "CNAME at apex" restriction. You cannot put a CNAME on the root domain (example.com) alongside A, MX, or TXT records. Only subdomains (www, mail, shop) can hold CNAMEs.
How to interpret CNAME propagation results
This checker queries each resolver for the CNAME record directly. The data field shows the target hostname the resolver currently returns. When all 7 resolvers show the same target (e.g., yoursite.cdn.example.net), the alias has propagated fully.
If resolvers return the old CNAME target, they are still serving a cached answer. If a resolver returns NXDOMAIN, it has no CNAME for that subdomain — this may indicate the record was not saved correctly or the TTL on the negative response is keeping the empty answer cached.
FAQ
Common questions about cname record propagation checker
How long does CNAME propagation take?
CNAME propagation is governed by the TTL of the previous CNAME record (or the negative-cache TTL if there was no CNAME before). Most CDN and hosting platforms set short TTLs (300–3600 seconds) by default. After you update the CNAME and the old TTL expires across all resolvers, the change is complete.
Why can I not put a CNAME on my root domain?
The DNS specification (RFC 1912, 2181) forbids a CNAME on a name that has other record types. Since root domains must have SOA and NS records, a CNAME is not allowed there. Some providers offer "CNAME flattening" or "ALIAS / ANAME" records that simulate a CNAME at the apex while staying standards-compliant.
I updated the CNAME but the old IP still resolves. Why?
Resolvers cache each step of a DNS chain independently. Even after your CNAME propagates, the A record the old CNAME pointed to may still be cached at its own TTL. Once both the CNAME and the underlying A record re-resolve, traffic reaches the new destination.
Can I check CNAME propagation for a subdomain?
Yes. Type the full subdomain into the input field — e.g., www.example.com or shop.example.com — select CNAME from the record type dropdown, and run the test query. The results show the target each resolver currently returns.
What is the difference between a CNAME and an A record for a custom domain?
An A record points to a specific IP address. A CNAME points to another hostname, letting the provider control the underlying IP(s). Custom domains on cloud platforms usually use CNAMEs so the platform can update IPs without requiring action from you.