Popular tools

Theme

DNS propagation checker Check DNS propagation worldwide

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

Try
  • 34 resolvers in 28 countries
  • Select a dot for details

Your connection

IP details

Results worldwide

34 resolvers
Skip the resolver list

  • Google DNS

    From your browser

  • United States

    Google

  • United States

    Cloudflare

  • United States

    OpenDNS

  • United States

    Hurricane Electric

  • Canada

    CIRA Canadian Shield

  • Mexico

    Alestra

  • Brazil

    Claro

  • Ireland

    Namecheap

  • United Kingdom

    IONOS

  • France

    OVH

  • Netherlands

    Odido

  • Germany

    Telekom Deutschland

  • Switzerland

    Swisscom

  • Switzerland

    Quad9

  • Spain

    Priority Telecom

  • Italy

    UltraDNS

  • Cyprus

    AdGuard

  • Türkiye

    Teknet

  • Türkiye

    Netlen

  • Russia

    SafeDNS

  • Russia

    Yandex

  • Kuwait

    Gulfnet

  • South Africa

    Liquid Telecom

  • Pakistan

    CMPak

  • India

    Bharat Public DNS

  • Philippines

    PLDT

  • Malaysia

    Exabytes

  • Singapore

    Azure-hosted

  • Indonesia

    IDNIC

  • China

    114DNS

  • South Korea

    LG Uplus

  • Taiwan

    HiNet

  • Japan

    IIJ

  • Australia

    Telstra

A DNS checker that asks the whole world at once

When you change a DNS record, the new value does not reach everyone at the same moment. Resolvers around the world keep the old answer in their cache until it expires. This DNS propagation checker asks 34 public resolvers at the same moment, global services such as Google, Cloudflare, Quad9 and OpenDNS, and the resolvers of ISPs, hosting companies and public DNS services in 20+ countries, and asks Google Public DNS from your own browser too, so you see exactly who already returns your new record.

Run this DNS propagation test after you point a domain at a new server, move email to a new provider, add a verification TXT record or change nameservers. For one resolver's complete answer, use DNS Lookup.

DNS propagation checker results for dnsrobot.net: resolvers on a world map and in a list, all returning the same A recordDNS propagation checker results for dnsrobot.net: resolvers on a world map and in a list, all returning the same A recordDomain and record typeType a domain or paste a URL, pick the record you changed and press Check. An IP address switches the check to its PTR record.The world mapOne dot per resolver. An ISP's resolver sits where it answers from; global services such as Google, Cloudflare and Quad9 answer from their site nearest our server, so their dot marks the company. Green agrees with most others, amber differs, red returned no record or an error. Hover or tap a dot for its answer.Google DNS from your browserThe same lookup sent by your own browser to Google Public DNS, so Google answers for your location. Your ISP's resolver, which most devices use, can still hold an older answer.The tallyHow many resolvers agree, differ, have no record or did not answer. Propagation is complete when every resolver agrees on your new value.
A live check on the DNS propagation map: each dot is a public resolver, green when it returns the same answer as most others. Select a marker to see what each part shows.

How to check DNS propagation

  1. 1

    Enter a domain

    Type a domain or paste a URL. Enter an IP address to check its reverse DNS (PTR) record instead.

  2. 2

    Pick the record type

    A for a website's IPv4 address, AAAA for IPv6, MX for email, TXT for SPF, DKIM and verification codes, NS for nameservers, and seven more.

  3. 3

    Read the map and the list

    Green resolvers return the same answer as most others, amber ones differ, red ones returned no record or an error. Google DNS from your browser shows what Google answers for your location; your ISP's resolver can differ.

What is DNS propagation?

DNS propagation is the time it takes for a change to your DNS records to replace the old version in every resolver's cache. Nothing is pushed out: your DNS host has the new record the moment you save it, and each resolver picks it up only when its cached copy expires.

How long a resolver may keep a record is set by the record's TTL (time to live), in seconds, as defined in RFC 1035. With a TTL of 3600, a resolver that fetched the old record a minute before your change can serve it for almost an hour. That is why two people in the same city can see different versions of a site for a while.

Your DNS host
Has the new record the moment you save it
Resolvers worldwide
Keep their cached copy until its TTL runs out
Visitors
Get whatever their resolver has cached
New recordOld record, still cachedEach resolver refreshes on its own schedule, so global DNS propagation happens in pieces, not all at once.

How long does DNS propagation take?

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 cache that follows the rules within an hour. The ranges below assume common TTLs, from 300 seconds to 24 hours; nameserver changes and new domains also wait on the registry.

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 – 24 hours
  • A or AAAA record: 5 minutes – 24 hours
  • CNAME record: 5 minutes – 24 hours
  • MX record: 5 minutes – 24 hours
  • New .com or .net domain: 5 minutes – 15 minutes
  • Nameserver change: 5 minutes – 48 hours

DNS propagation time by provider

A record change reaches every resolver within about one TTL, so your DNS host's default TTL is the number to know. These are the defaults each provider documents for new records (for Porkbun, its minimum); you can lower most of them.

Each value is from the provider's own documentation: Cloudflare, Route 53, Porkbun, Namecheap, GoDaddy, Network Solutions and Hostinger.

DNS hostDefault TTLA record change reaches every resolver in about
Cloudflare300 s (Auto)5 minutes
Amazon Route 53300 s5 minutes
Porkbun600 s (minimum)10 minutes
Namecheap1,800 s (Automatic)30 minutes
GoDaddy3,600 s1 hour
Network Solutions7,200 s2 hours
Hostinger14,400 s4 hours

How to speed up DNS propagation

No one can make every resolver in the world drop a cached answer early. You can plan the change so caches expire fast, and you can refresh the resolvers that serve the most people.

  1. 1

    Lower the TTL first

    A day or two before the change, set the record's TTL to 300 seconds. Resolvers will then keep the record for five minutes at most.

  2. 2

    Wait out the old TTL

    Resolvers that cached the record before you lowered the TTL keep it for the old TTL: a full day if it was 86400.

  3. 3

    Make the change where it counts

    Edit the record at the DNS host your nameservers point to. Not sure which one that is? Check with NS Lookup.

  4. 4

    Ask Google and Cloudflare to refresh

    Both let anyone drop a cached record: Google Public DNS Flush Cache and Cloudflare 1.1.1.1 Purge Cache.

  5. 5

    Clear your own caches

    Your computer, browser and router keep their own copies. The commands are just below.

  6. 6

    Check, then raise the TTL

    When every resolver above shows the new value, set the TTL back to 3600 or higher so your DNS host answers fewer queries.

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.”

Where an old answer can hide

  1. Your browser

    Keeps its own DNS cache and the old page. A hard refresh (Ctrl+Shift+R, or Cmd+Shift+R on a Mac) reloads the page but doesn't clear that DNS cache: the Chrome and Firefox steps above do.

  2. Your computer

    The system DNS cache answers every app. Flush it with the command for your system.

  3. Your router

    Caches answers for every device on your network. Restarting it clears them.

  4. Your ISP's resolver

    You cannot flush it. Wait out the TTL, or switch your device to 1.1.1.1 or 8.8.8.8 for a while.

  5. A CDN or page cache

    If DNS is right everywhere but the page is old, purge your CDN or your site's caching plugin.

Why is my DNS not propagating?

If resolvers still show the old record long after the TTL has passed, one of these is usually the cause:

What a check looks like mid-change, and once it is done

The same DNS propagation check once complete: every resolver on the map and in the list agrees on the new addressThe same DNS propagation check once complete: every resolver on the map and in the list agrees on the new addressDNS propagation check of example.com mid-change, resolvers: 24 of 34 return the new address, ten still return the old oneDNS propagation check of example.com mid-change, resolvers: 24 of 34 return the new address, ten still return the old one
Drag the handle. Mid-change, resolvers whose answer differs from most others show as Differs; once every cache has expired, all 34 agree.

What do you see?

Nothing changes, however long you wait

Likely cause

The change was made at the wrong DNS host

Records only count at the DNS host your nameservers point to. If your domain uses Cloudflare's nameservers, edits at your registrar change nothing.

Check your nameservers
Some resolvers still return the old value

Likely cause

The old TTL has not run out

Resolvers may keep the old answer for the TTL it had before your change. The result's Lowest TTL is the shortest time left on any answer, not the longest wait. For a resolver still on the old value, ask it directly with its address from its details, such as dig @8.8.8.8 example.com A: the number before IN is the seconds its copy has left.

Look up the record's TTL
Resolvers answer “no record” for a name you just added

Likely cause

Resolvers still say the name does not exist

A resolver that asked before the record existed remembers “no such name” for the zone's negative-caching time, often 5 minutes to an hour. RFC 2308 sets it: the lower of the SOA record's TTL and its minimum field.

Run a DNS lookup
Some resolvers fail with SERVFAIL since you moved to a new DNS host

Likely cause

Validating resolvers fail after moving nameservers

Usually DNSSEC: a DS record at your registrar still points to the old DNS host's keys, so resolvers that validate (Google, Cloudflare, Quad9) return SERVFAIL while others still answer. Remove it or replace it with the new host's. Check the DS record type above, or run the DNS Health Check.

Check the registrar
Different addresses by region, and they never settle

Likely cause

Answers differ by region and never match

Sites on a CDN or geo-DNS answer each region with a nearby server. That is expected: with three or more different answers and none held by most resolvers, the checker counts them all as resolved; with only two, the smaller group shows as Differs even though nothing is changing.

Find the CDN or host
Mail bounces or still lands at the old server

Likely cause

Email bounces after an MX change

Some senders still use the old MX until it expires. Keep the old mail server running, and check SPF, DKIM and DMARC for the new provider.

Check MX records

50+ free DNS, network, security and utility tools

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

DNS Tools11

DNS Tools

Email Tools10

Email Tools

Website Tools16

Website Tools

Network Tools14

Network Tools

IP Tools15

IP Tools

Utility Tools18

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 DNS checker asks 34 resolvers directly, with nothing cached in between, and asks Google Public DNS from your own browser too.

Why does a site load on mobile data but not on Wi-Fi?

Because each network asks a different resolver, and each resolver keeps its own cache. On Wi-Fi your device usually asks your router, which asks your home ISP's resolver; on mobile data it asks your carrier's. Either can still hold the old record until its TTL runs out. Restart the router and flush your computer's DNS cache; your ISP's resolver can't be flushed, so if it holds the old copy, wait out the TTL.

Why does my DNS host show the new record when resolvers don't?

Because your DNS host's nameservers are authoritative: they answer from the zone itself, so they have the change the moment you save it. Resolvers answer from their cache and ask the zone again only when the TTL runs out. DNS Lookup asks the zone's own servers beside Google and Cloudflare, so you can tell a change that wasn't saved from one that is still cached.

Can I check my records at a new DNS host before switching nameservers?

Yes: ask the new host's nameservers directly. dig @ns1.newhost.example example.com A, with your new host's nameserver and your domain, returns the zone's own answer with no cache in between, so it is right as soon as you save. Hosting DNS Lookup does this for 14 hosts. Once every record matches, the switch waits only on the registry's delegation.

How fast does Cloudflare DNS propagate?

Records on Cloudflare default to a 300-second TTL, so a change usually reaches every resolver within about 5 minutes. A proxied record (orange cloud) always returns Cloudflare's addresses, so pointing it at a new server needs no propagation, and this checker shows Cloudflare's IPs rather than yours. Moving a domain to Cloudflare's nameservers is a nameserver change: the registry's delegation TTL sets its pace, not Cloudflare.

Why can't the checker ask my own ISP's resolver?

Because a web page can't send a DNS query to the resolver your device uses: browsers give pages no way to do it. So the Google DNS row asks Google Public DNS over HTTPS, over your connection, instead. To see your own resolver's answer, run nslookup example.com on your computer, which asks the DNS server your system is set to use. The DNS Leak Test names the resolvers behind your connection.

Why do some resolvers show “No answer”?

A resolver that doesn't reply within 4 seconds, or whose connection fails, counts as No answer, never as a different answer. It says nothing about your record: the resolver or the path to it was slow or down at that moment. Run the check again a minute later; if the same resolver stays silent while every other one agrees, your change has reached them.

Is there a limit, and can I share or automate a check?

It is free and needs no account, for up to 20 checks a minute from one IP address; each check asks all 34 resolvers. Copy link gives a link that runs the same domain and record type for whoever opens it. For scripts, API v2's GET /api/v2/dns/propagation returns every resolver's answer and TTL as JSON, with its own 20 calls a minute; see the API docs.

Missing something?Suggest a feature or a new tool