DNS propagation checkerCheck DNS propagation worldwide

Ask 33 public resolvers on six continents at once and see which ones already return your new records.

Try
Google (8.8.8.8), Mountain View, United StatesCloudflare (1.1.1.1), San Francisco, United StatesOpenDNS (208.67.222.222), Berkeley, United StatesHurricane Electric (209.51.161.14), New York, United StatesCIRA Canadian Shield (149.112.121.10), Ottawa, CanadaUninet (148.235.82.66), Mexico City, MexicoClaro (200.248.178.54), Santa Cruz do Sul, BrazilNamecheap (198.54.117.10), Dublin, IrelandIONOS (109.228.4.246), London, United KingdomOVH (91.121.62.94), Roubaix, FranceT-Mobile (87.213.100.113), Amsterdam, NetherlandsTelekom Deutschland (195.243.214.4), Oberhausen, GermanySwisscom (195.186.1.111), Zurich, SwitzerlandQuad9 (9.9.9.9), Zurich, SwitzerlandPriority Telecom (212.230.255.1), Madrid, SpainNeustar UltraDNS (156.154.70.1), Rome, ItalyAdGuard (94.140.14.14), Limassol, CyprusTeknet (31.7.37.37), Antalya, TürkiyeSkyDNS (195.46.39.39), Moscow, RussiaYandex (77.88.8.8), Moscow, RussiaGulfNet (85.194.70.174), Riyadh, Saudi ArabiaLiquid Telecom (5.11.11.5), Cape Town, South AfricaCMPak (209.150.154.1), Karachi, PakistanIndian Public DNS (1.10.10.10), New Delhi, IndiaPLDT (121.58.203.4), Manila, PhilippinesExabytes (117.53.152.76), Kuala Lumpur, MalaysiaMicrosoft (13.76.130.172), Singapore, SingaporeIDNIC (203.119.13.77), Jakarta, Indonesia114DNS (114.114.115.115), Xinfeng, ChinaLG Uplus (164.124.101.2), Seoul, South KoreaHiNet (168.95.1.1), Taipei, TaiwanIIJ (public.dns.iij.jp), Tokyo, JapanTelstra (139.130.4.4), Sydney, Australia
  • 33 resolvers in 28 countries

How long DNS propagation takes

Most record changes reach every resolver within minutes to a few hours. A nameserver change can take up to 48 hours.

The old record's TTL sets the pace: a resolver that cached it keeps serving it until the TTL runs out. A record with a 3600 second TTL leaves every honest cache within an hour.

Planning a change? Lower the TTL to 300 a day before, wait for the old TTL to pass, then make the change.

Typical time until every resolver has the change
  • TXT record (SPF, DKIM, DMARC): 5 minutes to 4 hours
  • A or AAAA record: 5 minutes to 24 hours
  • CNAME record: 5 minutes to 24 hours
  • MX record: 1 hours to 24 hours
  • New domain: 12 hours to 48 hours
  • Nameserver change: 24 hours to 48 hours

Still seeing the old site?

When every resolver above already returns the new record but your own browser does not, the old answer is cached on your side. Clear it where it lives:

ipconfig /flushdns

Run it in Command Prompt as administrator. It answers “Successfully flushed the DNS Resolver Cache.”

50+ free DNS, network and security tools

Every tool runs in your browser or on our servers in seconds, without an account.

DNS Tools

Email Tools

Website Tools

Network Tools

IP Tools

Utility Tools

DNS propagation questions

What does a DNS propagation checker do?

It asks many public resolvers at once for the same record and compares their answers. When they all return your new value, your change has reached them. This checker asks 33 resolvers in 28 countries directly, with nothing cached in between.

How long does DNS propagation take?

Usually minutes to a few hours for a record change, and up to 48 hours for a nameserver change. The upper bound is the old record's TTL: a resolver that cached it keeps it until the TTL runs out.

Why is my DNS not propagating?

Resolvers that cached the old record keep it until its TTL expires, and a few ISPs hold answers longer than the TTL says. Check that the new record is saved at your DNS host, that the domain uses the nameservers you edited (check with NS Lookup), then check again after the old TTL has passed.

Why do resolvers return different IP addresses for the same site?

Many sites use a CDN or geographic DNS, which answers each region with a nearby server. Answers that differ by region and never converge are usually that, not a propagation problem.

How can I make DNS changes propagate faster?

Lower the record's TTL to 300 seconds a day or two before the change, wait for the old TTL to pass, then make the change. Afterwards, flush your own caches. Nobody can force other people's resolvers to drop a cached answer early.

What does NXDOMAIN mean?

The resolver was told the name does not exist. For a domain registered minutes ago, the registry may not have published it yet. For an existing domain, check the spelling and its nameservers.

What is the difference between a DNS lookup and a propagation check?

A DNS lookup asks one resolver for a domain's records. A propagation check asks the same question of many resolvers around the world at once, to see whether a change has reached all of them.

Is this DNS propagation checker free?

Yes. It is free, needs no account, and checks A, AAAA, CNAME, MX, NS, PTR, SRV, SOA, TXT, CAA, DS and DNSKEY records.