Instantly verify if your DNS changes have propagated worldwide, we query resolvers across 30+ global locations and plot every answer on a live map.
Type the domain and select the record type you changed, A, AAAA, MX, CNAME, TXT, NS, or SOA.
We simultaneously query DNS resolvers across North America, Europe, South America, the Middle East, Asia Pacific, and Africa.
Each location shows its resolved value on the map and in the list. Instantly spot where your DNS change hasn't landed yet.
Each location returns one of four statuses. Here's exactly what each means and what action to take.
This resolver returns the latest version of your DNS record, the value matches the authoritative reference. Nothing to do.
The resolver returned a value that doesn't match the reference. Usually a cached old record still waiting out its TTL, or, for geo-load-balanced domains, entirely legitimate regional routing.
The resolver returned NXDOMAIN or an empty answer. Either the record doesn't exist yet, is deleted, or hasn't propagated to that region at all.
The resolver didn't respond in time, usually a temporary network hiccup at that location, not a problem with your DNS. Try checking again.
DNS propagation is the time it takes for DNS changes to spread across all DNS servers worldwide. When you update a record, resolvers keep serving their cached copy until its TTL expires.
Time To Live directly controls how long resolvers cache your record. Lower it to 300 seconds a day before planned changes, restore it afterwards.
Some ISP resolvers ignore TTLs and cache longer than they should, the most common cause of stragglers showing old values for hours.
Nameserver changes at the registrar propagate through the TLD zone and typically take the longest, up to 48 hours.
You can't force other people's caches to clear, but you can lower TTLs in advance and flush your own resolver (and public resolvers like Google and Cloudflare offer flush tools).
Typically 1 to 48 hours, driven almost entirely by the record's TTL and how strictly resolvers honor it. Most changes are visible at major public resolvers within minutes.
Either the resolver still has the old value cached, or the domain uses geo-load-balancing (like google.com) and legitimately answers with different IPs per region. Check whether the "different" values look like your old record or a regional variant.
That resolver has no answer for the queried name and type, the record hasn't reached it yet, doesn't exist, or was removed. If it persists everywhere, verify the record exists at your authoritative nameserver.
Yes, every location row queries a real public resolver operated in or serving that region (Google, Cloudflare, Quad9, and national operators). Location labels are representative of the resolver's service region.
A regular lookup asks one resolver; a propagation check asks 30+ resolvers around the world simultaneously and compares every answer to your authoritative value, showing you the rollout, not just one snapshot.
Strengthen your domain security with our free lookup tools.
SenderSignal monitors these signals continuously: 48 blacklists, SPF, DKIM, DMARC, TLS and more, with alerts in Slack, email and signed webhooks.