Has your DNS
propagated yet?
Look up any record against resolvers in 14 countries on 6 continents at once. Every answer carries its TTL and query time, and the verdict is one word: propagated, or still spreading.
One checker for all records
Pick a type in the search bar — or run ALL and get the whole zone in one pass.
Domain → IPv4 address. The record everyone means by “DNS”.
198.51.100.7Domain → IPv6 address, for the modern internet.
2001:db8:4400::7Alias one name to another — www, CDNs, SaaS subdomains.
www → caldmont.comWhere your email gets delivered, in priority order.
10 mail.caldmont.comFree-form text: SPF, site verification, anything.
"v=spf1 include:…"Which nameservers are authoritative for the zone.
ns1.caldmont-dns.comReverse DNS: IP address → hostname.
…100.7 → edge-42.caldmont-cdn.comService locator — host and port for SIP, XMPP, AD.
_sip._tls 443 sip.caldmont…Which certificate authorities may issue your TLS certs.
0 issue "letsencrypt.org"Zone serial and refresh timers — proof your edit landed.
serial 2026070401Why your old record survives
There is no switch that flips. Every resolver keeps your record until its TTL runs out — so a change spreads cache by cache, country by country.
Each answer carries a time-to-live. A resolver that cached your record 40 minutes ago with a 3600 s TTL will keep serving the old value for another 20 — no matter what you do.
Most changes are world-wide within minutes to a couple of hours. The old guidance survives from the dial-up era — and from nameserver changes, which really can take a day.
Your OS and browser cache DNS too. The site “still being broken” on your laptop says nothing about the rest of the world — that’s what the 14 outside opinions are for.
Mail bouncing? Start with DNS.
One wrong MX and your mail goes nowhere. One missing SPF include and your invoices land in spam. This checker covers the two records that live on the domain itself — DKIM and DMARC sit on their own names, so each has a checker of its own:
- MX — where mail is delivered, priorities included. Type MX above and all 14 resolvers answer.
- SPF — which servers may send as you. Type TXT to read it raw, or use the SPF checker to follow every include and count the ten-lookup limit.
- DKIM — your signing keys live at selector._domainkey, so the DKIM checker tries the ten common selectors for you and reads the key.
- DMARC — the policy lives at _dmarc, not on your domain: the DMARC checker parses it.
Email DNS · caldmont.com
example · four checksPrefer dig? Same checks, worldwide.
Every lookup this page runs has a one-line equivalent. The difference: we run it from 14 countries at once.
Six checks before you panic
The order worth trying when you changed your DNS and nothing happened.
If your own nameserver still returns the old value, propagation isn’t your problem: the edit never landed. dig @ns1.caldmont-dns.com caldmont.com
The classic: editing DNS at your registrar while the domain’s NS records delegate to Cloudflare — or the other way round. Run this checker with type NS and compare against where you just made the change.
Caches keep the old record for its full TTL from the moment they fetched it. Run the check: every answer shows its TTL. Next migration, drop the TTL to 300 a day in advance.
Your OS and browser cache DNS too. Mac sudo dscacheutil -flushcache Win ipconfig /flushdns Chrome chrome://net-internals/#dns
GitHub Pages, registrars and site builders show this while their own crawler verifies your records. Confirm the records are right with this checker — if all 14 countries agree, the wait is on their side, not yours.
A few resolvers ignore TTLs and cache for a day or more. You can’t force them. If one region lags long after the rest agree, that’s them — not you. Affected users can switch to 1.1.1.1 or 8.8.8.8 meanwhile.
Common questions
DNS propagation is the time it takes for a DNS change to be seen by resolvers around the world. Because resolvers cache records for the length of the record's TTL, a change is visible in some places before others until every cached copy expires.
As long as the record's TTL: a resolver keeps serving the old value until its cached copy expires, so most changes are worldwide within minutes to a couple of hours. The 24-48 hour figure people still quote applies to one case — nameserver (NS) changes, which the TLD zone caches for up to two days. Lower the TTL a day before a planned change and the switch takes minutes.
Each of our 14 resolvers — one per country, across 6 continents — caches independently. During a change, resolvers that cached the old record still return it while others already see the new one — which is exactly what a "propagating" verdict means.
A, AAAA, CNAME, MX, TXT, NS, PTR, SRV, CAA and SOA — plus an "ALL" mode that queries the common set (A, AAAA, CNAME, MX, TXT, NS, SOA) at once and groups the results.
TTL (time to live) is how many seconds a resolver is allowed to cache a record before it must ask again. A record with a 3600 TTL can be cached for up to an hour, so a change can take up to that long to be seen everywhere.
Yes. Choose the PTR type and enter an IPv4 or IPv6 address instead of a domain. We convert it to the reverse-lookup name and query each resolver for the PTR record.
Yes, completely free and no signup is required. If you need continuous DNS and uptime monitoring with alerts when a record changes or a site goes down, that is what the Uptimia platform is built for.
Live answers by resolver
first answers arriving…Free tools are just the start.
Uptimia keeps your sites healthy.
Uptime, SSL, domain expiry, page speed, transactions — monitored from 171+ locations worldwide. Free for 30 days.