Live from 60 DNS servers in 47 countries

Check My DNS Propagation Worldwide

Check my DNS records instantly: see whether your changes are live worldwide. Test A, AAAA, CNAME, MX, NS, TXT and more against 60 public resolvers on every continent, with TTLs, response times and a live map.

Global DNS resolver network

60 public resolvers in 47 countries answer your query directly, and nothing is cached on our side. Enter a domain above, or try an example:

60 resolvers 47 countries 10 record types
Try:

Checking…

Querying 60 resolvers…

0 resolved 0 different 0 no answer 0 ms avg. response
  • US
    Mountain View, United StatesGoogle · 8.8.8.8
  • US
    San Francisco, United StatesCloudflare · 1.1.1.1
  • US
    Los Angeles, United StatesCleanBrowsing · 185.228.168.9
  • US
    Cleveland, United StatesCogent · 66.28.0.61
  • US
    Tucson, United StatesCenturyLink (Lumen) · 205.171.2.25
  • CA
    Toronto, CanadaControl D · 76.76.2.0
  • CA
    Ottawa, CanadaCIRA Canadian Shield · 149.112.121.10
  • MX
    Mexico City, MexicoAlestra · 200.76.5.147
  • CO
    Bogotá, ColombiaClaro · 190.85.62.74
  • BR
    São Paulo, BrazilUOL · 200.221.11.100
  • BR
    Goiânia, BrazilDelta Fibra · 168.195.135.67
  • CL
    Santiago, ChileEntel · 190.151.104.178
  • AR
    Buenos Aires, ArgentinaTelecom Argentina · 200.89.142.74
  • GB
    London, United KingdomExponential-E · 167.98.174.81
  • GB
    Prescot, United KingdomVirgin Media · 194.168.4.123
  • FR
    Paris, FranceSFR · 109.5.33.66
  • NL
    Zoetermeer, NetherlandsOdido · 87.213.68.86
  • ES
    Madrid, SpainIDDQD · 213.140.41.194
  • HR
    Zagreb, CroatiaHrvatski Telekom · 195.29.38.138
  • DE
    Frankfurt, GermanyDNS.SB · 185.222.222.222
  • DE
    Berlin, GermanyAS250.net · 194.150.168.168
  • DE
    Munich, GermanyFreifunk München · 5.1.66.255
  • CH
    Zurich, SwitzerlandQuad9 · 9.9.9.10
  • IT
    Arezzo, ItalyAruba · 62.149.128.4
  • CZ
    Prague, CzechiaDNS4EU · 86.54.11.200
  • PL
    Warsaw, PolandOVH · 51.68.139.183
  • SE
    Sundsvall, SwedenTele2 · 212.247.176.202
  • FI
    Turku, FinlandDNA · 85.23.204.137
  • UA
    Kyiv, UkraineUkrtelecom · 213.179.228.4
  • RU
    Moscow, RussiaYandex · 77.88.8.8
  • TR
    Antalya, TurkeyTeknet · 31.7.37.37
  • CY
    Limassol, CyprusAdGuard DNS · 94.140.14.140
  • IL
    Tel Aviv, IsraelO.M.C. · 91.223.106.229
  • MA
    Casablanca, MoroccoONPT · 102.50.253.95
  • SA
    Riyadh, Saudi ArabiaAlibaba Cloud · 8.213.0.112
  • AE
    Dubai, United Arab Emiratesdu · 94.203.136.10
  • GH
    Accra, GhanaGhana Telecom · 197.251.239.245
  • KE
    Nairobi, KenyaLiquid Telecom · 197.155.92.20
  • ZA
    Johannesburg, South AfricaAfrihost · 41.76.214.32
  • PK
    Karachi, PakistanLINKdotNET · 210.2.138.68
  • PK
    Islamabad, PakistanPSEB · 203.215.186.37
  • IN
    New Delhi, IndiaBharat DNS (C-DOT) · 1.10.10.10
  • IN
    Kolkata, IndiaMeghbela Broadband · 103.70.45.141
  • BD
    Dhaka, BangladeshWindstream · 103.187.98.221
  • SG
    Singapore, SingaporeSingNet · 203.125.208.78
  • MY
    Kuala Lumpur, MalaysiaHostinger · 31.97.191.57
  • ID
    Bekasi, IndonesiaAkses Bersama · 103.166.8.228
  • TH
    Bangkok, ThailandAIS Fibre · 58.136.155.82
  • VN
    Ho Chi Minh City, VietnamFPT Telecom · 42.116.255.180
  • NP
    Kathmandu, NepalSubisu · 182.93.84.123
  • HK
    Hong KongAlibaba Cloud · 8.210.22.68
  • TW
    Taoyuan, TaiwanChunghwa Telecom · 60.248.142.199
  • CN
    Hangzhou, ChinaAliDNS · 223.5.5.5
  • KZ
    Astana, KazakhstanKazakhtelecom · 178.88.161.200
  • PE
    Lima, PeruAmerica Movil Peru · 200.62.147.66
  • KR
    Seoul, South KoreaKT · 168.126.63.1
  • JP
    Tokyo, JapanNTT Docomo Business · 60.32.149.50
  • JP
    Osaka, JapanSo-net (Sony) · 92.203.123.235
  • AU
    Sydney, AustraliaVocus · 49.255.4.22
  • AU
    Adelaide, AustraliaAussie Broadband · 159.196.50.130
How it works

Check DNS propagation in three steps

CheckMyDNS sends your query straight to public recursive resolvers across North America, Europe, Asia, Africa, South America and Oceania, then shows what each one answers right now.

1

Enter your domain

Type a domain or hostname such as example.com or mail.example.com. For reverse DNS, enter an IP address and choose PTR.

2

Pick a record type

Choose A for websites, MX for email, NS after a nameserver change or TXT for SPF, DKIM and verification records. Add an expected value to match against.

3

Read the results

Green means a resolver returns the new value, amber means a different answer is still cached, and red means no answer. Share the link or export to CSV.

Check my DNS

Two things people mean by “check my DNS”

The phrase covers two different jobs, and the right tool depends on which one you're after.

My domain's DNS records

You own a domain and just changed where it points: a new hosting IP, a new mail provider, a new set of nameservers. You want to know whether the rest of the internet has noticed. That's what the checker at the top of this page does: it asks resolvers worldwide and shows you every answer.

Check a domain now →

The DNS server my device uses

Your website loads slowly, a page says “server not found”, or you've just switched to a privacy-focused resolver and want proof it worked. That's about the resolver your own computer, phone or router talks to, and you can read it straight off the device in under a minute.

See how on Windows, Mac, Linux, Android and iPhone →

Why CheckMyDNS

More signal than a simple pass/fail

Built for sysadmins, developers and site owners who need to know exactly where a change has landed, and where it hasn't.

60

Resolvers in 47 countries

Google, Cloudflare, Quad9, regional ISPs and national resolvers. Every result tells you who answered and from where.

TTL & response time

See the remaining cache TTL and how fast each resolver replied, so you know when stale answers will expire.

Expected-value matching

Tell us the new value and every location is checked against it, so there is no more eyeballing long lists of IPs.

Auto-refresh mode

Leave the page open and CheckMyDNS re-checks every 30 seconds, updating the map as resolvers pick up your change.

Share & export

Every check has its own link (send it to a client or teammate) or download the full result set as CSV.

Record types

DNS records you can check

Select a card to run that lookup for the domain in the search box.

Propagation time

How long does DNS propagation take?

There is no global “push” for DNS. Each recursive resolver keeps a cached copy of your record for as long as its TTL (time to live) allows, and only asks your nameservers again once that copy expires. That is why some locations update in seconds while others take hours.

  • A, AAAA, CNAME, MX and TXT changes usually propagate within the old record's TTL, often 5 minutes to 4 hours.
  • Nameserver changes can take 24 to 48 hours, because registries such as .com cache NS records for up to two days.
  • Brand-new records can be delayed by negative caching if someone looked them up before they existed (see the SOA minimum TTL).

Pro tip: lower the TTL to 300 seconds a day before a planned migration, make the change, then raise it again once every location here shows the new value.

Want the full story? Read about how long DNS propagation really takes, what TTL does and how to change nameservers without downtime.

Flush your local DNS cache

Windowsipconfig /flushdns
macOSsudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Linuxresolvectl flush-caches
Chrome / Edgechrome://net-internals/#dns

Every platform and browser, with what each command actually does: how to flush your DNS cache.

From the blog

Guides for when DNS gets confusing

Step-by-step articles written for site owners and sysadmins. No jargon without an explanation.

Browse all articles →

FAQ

DNS propagation questions, answered

What is DNS propagation?

DNS propagation is the time it takes for a change to your DNS records (a new IP address, mail server or nameserver) to be seen by DNS resolvers around the world. Resolvers cache answers for the record's TTL (time to live), so each one only picks up your change after its cached copy expires.

How long does DNS propagation take?

Most record changes are visible within minutes to a few hours, depending on the TTL of the old record. Nameserver (NS) changes at the registry can take up to 24 to 48 hours because top-level domains such as .com publish NS records with a 48-hour TTL.

Why do different locations show different results?

Every resolver caches records independently. A resolver that looked up your domain recently will keep serving the old answer until its TTL runs out, while another location that never cached it will already return the new value. Seeing mixed results is normal while a change is propagating.

How do I check if my DNS has propagated?

Enter your domain above, choose the record type (for example A for a website or MX for email) and press Check DNS. CheckMyDNS queries 60 public resolvers in 47 countries at once. When every location returns your new value (or matches the expected value you entered), propagation is complete.

Can I speed up DNS propagation?

You cannot force other resolvers to drop their cache, but you can plan ahead: lower the TTL of the record to 300 seconds a day or two before the change, make the change, then raise the TTL again once it has propagated. Flushing your own computer and browser DNS cache also helps you see the new result sooner.

Why does my website still show the old server after a DNS change?

Your computer, browser or internet provider is probably still using a cached answer. Flush your local DNS cache, try a different network or browser, and check here whether resolvers worldwide already return the new IP address.

What does the “Expected value” option do?

If you know the value your record should have (such as your new server IP), enter it as the expected value. Each resolver is then marked as propagated only when its answer contains that value, so you can see exactly where the old record is still cached.

Is CheckMyDNS free to use?

Yes. CheckMyDNS is completely free, needs no account and works on any device. Beyond DNS propagation you can also run WHOIS, IP address, email blacklist and DMARC checks.