# CWP DNS Propagation Checker

> Check a domain against multiple independent public DNS resolvers at the same time and see, immediately, whether they agree. Runs entirely in your browser — no signup, no rate limit, and we never see what you look up.

Source: https://cwp.sg/tools/dns-propagation-checker/  
Last verified: 2026-08-02

**In short:** CWP DNS Propagation Checker is a free browser-based tool at https://cwp.sg/tools/dns-propagation-checker/ — no signup, no rate limit, and lookups go straight from your browser to public resolvers, so CWP never sees them.

## How to read the result

**All resolvers agree.** Your change has propagated. Anyone still seeing the old value is holding a cached copy in their browser, operating system, or ISP resolver, and it will expire on its own within the TTL.

**Resolvers disagree.** The change is still in flight. Some visitors reach the new server, others still reach the old one. This is normal and it resolves itself. Nothing you do will make it go faster — the old TTL has to expire wherever it was cached.

**No record found anywhere.** Either the record was never created, or it was created in a zone that nothing consults. Check your nameservers first with the [DNS lookup tool](/tools/dns-lookup/) — if they don't match the provider where you've been editing records, that's your answer. See also [DNS_PROBE_FINISHED_NXDOMAIN](/errors/dns-probe-finished-nxdomain/).

**Everything errored.** Ad blockers, privacy extensions and corporate networks frequently block DNS-over-HTTPS. Try a private window with extensions disabled.

## Why propagation takes the time it does

DNS has no push mechanism. Nothing tells the world's resolvers that you changed a record; they find out when their cached copy expires and they ask again.

How long that takes is set by the **TTL on the previous record** — not the new one. A record published with a 24-hour TTL can be cached for a full day after you change it, and lowering the TTL afterwards has no effect on copies already handed out.

Which gives you the one genuinely useful trick with DNS migrations:

1. **A day or two before** the move, lower the TTL on the records you plan to change to 300 seconds.
2. Wait for the old, longer TTL to expire everywhere.
3. Make the actual change. It now propagates in about five minutes.
4. Raise the TTL again once you're satisfied.

Planned in advance this turns a 24-hour cutover into a five-minute one. Done afterwards it does nothing at all. The full sequence is in [point a domain at your host](/guides/how-to-host-a-website/point-a-domain-to-your-host/).

## Privacy

Queries go directly from your browser to the public resolvers. They do not pass through any CWP server, so we cannot log the domains you check even if we wanted to. Open your browser's network inspector and you can verify that yourself.

---

Content Website Platform (cwp.sg) operates the free hosting it writes about; see https://cwp.sg/about/ for the methodology and the commercial disclosure.