DNS Propagation Checker
Instantly see whether your DNS changes are live worldwide. Check A, AAAA, CNAME, MX, NS, TXT and more against public resolvers on every continent — with TTLs, response times and a live map.
Ready to check 60 DNS servers worldwide
Enter a domain above and pick a record type to start.
-
Mountain View, United StatesGoogle · 8.8.8.8—
-
San Francisco, United StatesCloudflare · 1.1.1.1—
-
Los Angeles, United StatesCleanBrowsing · 185.228.168.9—
-
Broomfield, United StatesLevel3 (Lumen) · 4.2.2.1—
-
Sterling, United StatesUltraDNS (Vercara) · 64.6.64.6—
-
Toronto, CanadaControl D · 76.76.2.0—
-
Ottawa, CanadaCIRA Canadian Shield · 149.112.121.10—
-
Mexico City, MexicoAlestra · 200.76.5.147—
-
Bogotá, ColombiaClaro · 190.85.62.74—
-
São Paulo, BrazilUOL · 200.221.11.100—
-
Goiânia, BrazilDelta Fibra · 168.195.135.67—
-
Santiago, ChileEntel · 190.151.104.178—
-
Buenos Aires, ArgentinaTelecom Argentina · 200.89.142.74—
-
London, United KingdomExponential-E · 167.98.161.41—
-
Prescot, United KingdomVirgin Media · 194.168.4.123—
-
Paris, FranceSFR · 109.5.33.66—
-
Zoetermeer, NetherlandsOdido · 87.213.68.86—
-
Madrid, SpainXtra Telecom · 212.230.255.1—
-
Porto, PortugalNOS · 195.23.236.90—
-
Frankfurt, GermanyDNS.SB · 185.222.222.222—
-
Berlin, GermanyAS250.net · 194.150.168.168—
-
Munich, GermanyFreifunk München · 5.1.66.255—
-
Zurich, SwitzerlandQuad9 · 9.9.9.9—
-
Arezzo, ItalyAruba · 62.149.128.4—
-
Prague, CzechiaDNS4EU · 86.54.11.100—
-
Warsaw, PolandPlay · 94.75.110.66—
-
Sundsvall, SwedenTele2 · 212.247.176.202—
-
Turku, FinlandDNA · 85.23.204.137—
-
Kyiv, UkraineUkrtelecom · 213.179.228.4—
-
Moscow, RussiaYandex · 77.88.8.8—
-
Antalya, TurkeyTeknet · 31.7.37.37—
-
Limassol, CyprusAdGuard DNS · 94.140.14.14—
-
Tel Aviv, IsraelO.M.C. · 91.223.106.229—
-
Cairo, EgyptCity Stars · 84.205.101.37—
-
Riyadh, Saudi ArabiaMobily · 85.194.70.174—
-
Dubai, United Arab EmiratesIPTP Networks · 185.65.175.161—
-
Ughelli, NigeriaMTN · 197.210.211.1—
-
Nairobi, KenyaLiquid Telecom · 197.155.92.20—
-
Johannesburg, South AfricaAfrihost · 41.76.214.32—
-
Karachi, PakistanLINKdotNET · 210.2.138.68—
-
Lahore, PakistanMultinet · 125.209.76.174—
-
New Delhi, IndiaBharat DNS (C-DOT) · 1.10.10.10—
-
Bengaluru, IndiaTata Teleservices · 182.156.93.102—
-
Dhaka, BangladeshWindstream · 103.187.98.221—
-
SingaporeSingNet · 118.201.56.26—
-
Kuala Lumpur, MalaysiaHostinger · 31.97.191.57—
-
Bekasi, IndonesiaAkses Bersama · 103.166.8.228—
-
Bangkok, ThailandNational Telecom · 61.19.251.237—
-
Ho Chi Minh City, VietnamFPT Telecom · 42.116.255.180—
-
Pasig, PhilippinesConverge ICT · 121.58.203.4—
-
Hong KongAlibaba Cloud · 8.210.22.68—
-
New Taipei, TaiwanChunghwa Telecom · 125.229.59.173—
-
Hangzhou, ChinaAliDNS · 223.5.5.5—
-
Shenzhen, ChinaDNSPod (Tencent) · 119.29.29.29—
-
Beijing, ChinaBaidu DNS · 180.76.76.76—
-
Seoul, South KoreaKT · 168.126.63.1—
-
Tokyo, JapanNTT Docomo Business · 60.32.149.50—
-
Osaka, JapanSo-net (Sony) · 92.203.123.235—
-
Sydney, AustraliaVocus · 49.255.4.22—
-
Melbourne, AustraliaTelstra · 203.47.150.183—
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.
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.
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.
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.
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.
Resolvers in 45 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 — 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.
DNS records you can check
Select a card to run that lookup for the domain in the search box.
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–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.
Flush your local DNS cache
ipconfig /flushdnssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderresolvectl flush-cacheschrome://net-internals/#dnsFree DNS & network toolkit
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–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 45 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.