DNS propagation is the wait while resolvers around the internet drop their cached copy of a record and fetch the new one, which takes up to the record's old TTL. This checker asks six public resolvers for the same record straight from your browser and shows whether they agree and whether the answer matches what your host expects.
| Resolver | Run by |
|---|---|
| Google Public DNS | |
| Cloudflare 1.1.1.1 | Cloudflare |
| Quad9 | Quad9 Foundation |
| Control D (free) | Control D |
| AliDNS | Alibaba Cloud |
| DNS.SB | xTom |
Updated
Type a domain, pick a record type and optionally the value you expect. Each resolver is queried over DNS-over-HTTPS from your own browser, so you see what those services answer right now. Pick a host such as Vercel or Netlify to fill in the expected value.
| Host | Root domain | www | Note |
|---|---|---|---|
| Vercel | A 76.76.21.21 | CNAME cname.vercel-dns.com | Vercel's dashboard may show a project-specific value instead; both work when Vercel shows them. |
| Netlify | A 75.2.60.5 | CNAME <your-site>.netlify.app | Netlify's load balancer address for the root domain; www points at your site's netlify.app name. |
| GitHub Pages | A 185.199.108.153, 185.199.109.153, 185.199.110.153, 185.199.111.153 | CNAME <user>.github.io | All four A records are recommended. |
| Cloudflare Pages | CNAME <project>.pages.dev | CNAME <project>.pages.dev | The domain must use Cloudflare's nameservers for a root-domain CNAME to work. |
All green with the expected value means the change is live for the big public resolvers. Mixed answers mean some caches still hold the old record; their TTL counts down to when they will ask again. No record everywhere usually means a typo in the name, the record was added at the wrong DNS provider, or the domain's nameservers point somewhere else.
For a CNAME, resolvers return the alias and then the final address. The table shows the alias, which is the part your host checks.
Most hosts want an A record for the root domain and a CNAME for www. The values in the host picker come from each host's documentation, but your dashboard is the final word: some hosts show project-specific targets, and they change their recommendations over time.
If your domain uses Cloudflare's proxy (the orange cloud), A record lookups return Cloudflare addresses rather than your host's. That is expected; check the record in the Cloudflare dashboard instead.
It sends one DNS-over-HTTPS query per resolver from your browser to six public resolvers: Google Public DNS, Cloudflare, Quad9, Control D, AliDNS and DNS.SB. It shows each answer, its TTL and how long the resolver took. It does not test resolvers in particular cities or at internet providers, and it cannot see what any one visitor's device has cached.
A page that runs in your browser can only reach resolvers that accept browser requests. Most big public resolvers use anycast, so the request reaches the location nearest to you anyway. That still answers the practical question: have the resolvers most people use picked up the change?
NextDNS, AdGuard, OpenDNS and Mullvad run DNS-over-HTTPS too, but when we tested them their servers did not allow requests from web pages (no CORS header), so a browser cannot read their answers. Rather than fake a result, the page skips them.
Up to the TTL of the record you replaced, which is often 3,600 seconds (one hour) and sometimes 86,400 (a day). Nameserver changes at the registrar can take longer, because the parent zone's NS records often carry a TTL of a day or two.
Hosts often check from their own resolvers on a timer, and some also need a verification TXT record or an SSL certificate to finish issuing. Wait a few minutes and use the host's verify or refresh button.
Related: DNS lookup, How to add a custom domain, Domain vs hosting, Business email setup (MX, SPF, DKIM, DMARC), Redirect checker.
Start for free or see all free tools. We.Inc is free to start, with no card needed. AI building is on paid plans from $20 a month.
We.Inc is an AI-powered website builder you can resell under your own brand. Launch a branded client dashboard, bill on Stripe Connect, and deliver AI-generated websites in minutes. White-label plans start at $99 a month for 25 client sites, with a 7-day free trial and no per-site fees.