How to use the DNS Propagation Checker
- Enter the domain or subdomain you changed (for example
www.example.com). - Pick the record type — A for websites, CNAME for www or Webflow, MX for mail, TXT for verification and SPF.
- Click Check to query Cloudflare, Google, NextDNS, AdGuard and Alibaba DNS plus Google DNS as seen from eight regions.
- If answers differ, wait for the previous record’s TTL to expire and check again.
What “DNS propagation” really is
DNS changes don’t travel across the internet; instead, resolvers cache answers for as long as the record’s TTL (time to live) says. After you change a record, each resolver keeps serving the old value until its cached copy expires. With a TTL of 3600, that’s up to an hour; nameserver changes at the registry can take up to 48 hours because TLD records often have long TTLs.
How this checker works
It queries several large public resolvers over DNS-over-HTTPS and Google DNS with EDNS Client Subnet hints for eight regions (US, Germany, UK, India, Brazil, Japan, Australia, South Africa). Region-specific answers reveal GeoDNS and CDN routing, and resolver differences reveal caches that still hold an old value.
Tips for faster DNS changes
- Lower the TTL in advance — set it to 300 seconds a day before a migration, then raise it again afterwards.
- Webflow: point the root domain with A records to Webflow’s IPs and
wwwwith a CNAME toproxy-ssl.webflow.com(check Webflow’s current values in the hosting settings), then publish. - Flush your own cache if your computer still shows the old site (for example
ipconfig /flushdnson Windows).
Need every record type at once? Use DNS Lookup. Check mail records with the SPF, DKIM & DMARC Checker, registration details with WHOIS Lookup and the new certificate with the SSL Checker.
Tools that pair well with the DNS Propagation Checker
- Website Down Checker — Find out in seconds whether a website is down for everyone or just for you — with status code, response time and troubleshooting tips.
- Ping Test — Measure how fast a server responds: enter a host and get the round-trip latency, jitter and failed attempts over several pings — measured from our server with a TCP ping to the port you choose.
- Port Checker — Test whether a server accepts connections on specific ports — web (80/443), mail (25/587/993), SSH, databases or remote desktop — and see which are open, closed or filtered by a firewall.
- What Is My IP — Your public IP address and everything your browser reveals to the websites you visit — user agent, screen, language, timezone and request headers.