Today we are launching the DNS Spy DNS Propagation Checker. It is free. It works on any domain. It shows you what is happening in more places, in more detail, and faster than the tools you have been using.
You can try it right now: dnsspy.io/dns-tools/dns-propagation-checker
Why we built this
DNS Spy already monitors DNS records for thousands of domains. Our customers use us to catch silent DNS changes, broken records, and migrations gone wrong. So when one of them needed a fast way to confirm a new A record had landed in Asia, Europe, and North America, we looked at the free tools out there.
They were fine. Not great.
The leader in the space ranks on Google for "dns propagation checker" with about 21 server locations. No response time data. No TTL data. No DNSSEC info. Heavy ads. Limited record type support.
We knew we could do better. We already had the infrastructure. We have 8 query nodes around the world that watch our customers' DNS. We have a curated database of 40+ public DNS resolvers we already monitor for health and reliability. The hard part was already built. We just needed to point it at a free public tool.
So we did.
What the tool does
You type in a domain. You pick a record type. You hit check.
The tool then queries that record across 40+ public DNS resolvers. Cloudflare, Google, Quad9, OpenDNS, regional resolvers in Asia, Europe, South America, Africa. The query goes out from multiple geographic vantage points at the same time. Results stream back in real time.
For each resolver you get:
The country and city where it lives
The resolver IP and provider name
The actual value it returned
The remaining TTL on the cached record
The response time in milliseconds
A clear status: matched, different, or failed
You see all of it on a world map and in a sortable table. Green dots match the majority. Yellow dots returned a different value. Red dots failed or timed out.
That is the propagation picture you actually need.
Five things this tool does that others do not
1. Forty resolvers, not twenty
Most free propagation checkers query 18 to 22 server locations. We query 40+. That is not just a bigger number for the sake of a bigger number. It is the difference between knowing your record landed in "Asia" and knowing it landed in Tokyo, Singapore, and Mumbai but not yet in Hong Kong.
When you are debugging a migration, more vantage points means a sharper picture.
2. Time to Live, shown
This one is huge and almost no one does it.
When a resolver returns the wrong answer, the question is not "is it broken." The question is "when will it fix itself." That answer is the TTL. We show it next to every result.
A red dot with 47 seconds left on the cache is fine. Wait a minute and refresh. A red dot with 23 hours and 14 minutes left is a different problem. Now you know whether to wait or to escalate.
3. Response times
Not every propagation problem is a propagation problem. Sometimes a resolver is slow. Sometimes it is timing out. Sometimes the route between you and the resolver is bad.
We show response time in milliseconds for every resolver. You can sort by it. You can spot the resolver that is technically returning the right answer but taking 4 seconds to do it. That is real intel.
4. DNSSEC status
If you are running DNSSEC, you need to know whether each resolver validated your signature. We show that. Nobody else does in a free tool.
If your DNSSEC is misconfigured, some resolvers will refuse to return your record at all. That looks like a propagation failure on other tools. With us, you see the actual reason: validation failed.
5. Zero ads
The other tools are covered in display ads. They sell your eyeballs because the tool is the product. Our tool is not the product. DNS Spy is the product. The propagation checker is a clean, fast, ad-free thing we offer because we want you to know we exist.
When you eventually need real DNS monitoring, you will remember which tool did not waste your time.
How it actually works under the hood
The architecture is what makes the data trustworthy.
Most propagation checkers run from one server. They query a list of public resolvers from that one location and report what comes back. That works most of the time. It misses things sometimes.
We use two layers:
Layer one: query nodes. DNS Spy operates 8 query nodes spread across the globe. They sit in different network regions and act as our vantage points.
Layer two: public resolvers. From those query nodes, we send requests out to 40+ public DNS resolvers. Cloudflare in Frankfurt. Google in Singapore. Quad9 in Sydney. Regional resolvers in places single-server tools cannot easily reach.
This means a query asking "what does Cloudflare in Brazil see for example.com" actually originates from a network position close to Brazil, not from a US data center pretending to ask Brazil. The data reflects what real users in those regions would experience.
It also means we can spot resolver-specific weirdness. If 39 resolvers see your new record and one Tier 2 resolver in Eastern Europe still serves stale data 14 hours later, that is a story we can tell you. Other tools cannot.
When you should use a propagation checker
The tool is useful any time you are making changes to DNS. Some real cases:
Website migrations. You moved hosts. Your A record points to a new IP. You want to know which regions have picked it up before you tell users to clear their caches.
Email provider switches. You moved from one email host to another. Your MX records changed. If half the world still sends mail to the old host, your inbox is going to be a mess.
Nameserver changes. You moved a domain to a new DNS provider. NS record changes propagate at the TLD level and can take up to 48 hours. You want to watch the rollout, not guess at it.
SPF, DKIM, and DMARC updates. You added or changed a TXT record for email authentication. You want to confirm receiving servers can validate your mail before deliverability tanks.
DNSSEC rollouts. You are signing a zone for the first time. You want to know which resolvers validate the signature and which do not.
Debugging "it works for me." A user reports a site is down. It loads fine for you. Pull up the propagation checker. If 6 resolvers in their region return a stale IP, you have your answer.
How to read the results
A few things to look for when you run a check.
The summary bar at the top. It tells you how many resolvers match the majority value. "Propagated: 38 of 41 resolvers (92.7%)" is generally healthy. Below 50% means most of the world has not seen the change yet.
Cluster patterns on the map. If your failures are random, they are probably stale caches that will expire on their own. If your failures are clustered geographically, you may have a routing or anycast problem at the upstream level.
TTL on the failed resolvers. Short TTLs will fix themselves. Long TTLs need patience or a TTL reduction next time.
Response times above 1000ms. That is a slow resolver. If it is slow for your users too, your site feels slow even when it is not.
A few tips before you change DNS again
We help customers avoid DNS pain for a living. A few hard-won lessons:
Lower your TTL 24 to 48 hours before any planned change. Drop it to 300 seconds. Wait. Then make the change. Propagation will feel near-instant.
Stagger the rollout. Change one record type at a time when possible. Mixing an A record swap with an MX swap with an NS swap on the same day is how outages happen.
Watch propagation in real time, not on faith. Run the checker. Refresh it. Confirm the world has caught up before you tell stakeholders the migration is done.
Monitor after. A propagation checker tells you what is happening right now. A monitoring service tells you when something silently breaks at 3am next Tuesday. Use both.
Free tool, real product
The DNS Propagation Checker is free. There is no signup. There is no rate limit you will reasonably hit. There are no ads.
If you like it, the rest of DNS Spy is what you get when you take that same idea further. We watch every record on every domain you care about, around the clock, from those same 8 query nodes. When something changes — planned or not — you find out before your customers do.
You can start a free 14-day trial at dnsspy.io. Or just use the propagation checker and bookmark it. Either is a win for us.
