DNS Propagation
Check how DNS records propagate across multiple locations worldwide
Global Propagation Map
DNS Information
Propagation Summary
Propagation Results
| Location | DNS Server | Result | Response Time | Status |
|---|---|---|---|---|
|
No propagation data yet
Run a check to see global results
|
||||
Learn more & FAQ
What is a DNS propagation checker?
When you update a DNS record — pointing a domain at a new server, adding an MX record for email, or switching nameservers — that change doesn't reach every DNS resolver on the internet at once. Resolvers cache answers for as long as the record's TTL allows, so different people around the world can see the old value or the new one depending on which resolver they use and when it last looked your domain up. This tool queries a spread of DNS servers in different regions and shows you, location by location, whether each one is already resolving your updated record.
How to read your results
Each location on the map and in the table is Propagated (returning your new value), Partial (still serving a cached older value), or Failed (no answer, usually a timeout or an NXDOMAIN). The Success Rate card gives you a quick read on how far along the rollout is. If most locations show Propagated and a handful show Partial, you're almost there — give it the remaining time on your record's TTL. If every location shows Failed, double-check the record was actually saved at your DNS provider before assuming it's a propagation delay.
Frequently asked questions
Why hasn't my DNS record propagated everywhere yet?
DNS propagation isn't instant because of caching: every resolver that has already looked up your record keeps the old answer until its TTL expires, and ISPs and public resolvers don't all refresh on the same schedule. A record with a 24-hour TTL can take up to 24 hours to update everywhere, even though the change at your authoritative nameserver was immediate.
How long does DNS propagation usually take?
Most resolvers pick up a change within a few minutes to a few hours. The outer bound is your record's TTL plus a little margin — set TTL to 3600 seconds (1 hour) before making a change and you should see it fully propagated within about an hour. Some resolvers ignore low TTLs and cache longer anyway, which is why a handful of locations can lag behind the rest.
What does "Partial" mean in the results?
Partial means that location's resolver returned a DNS answer, but it doesn't match the value every other resolver is returning yet — usually because it's still serving a cached copy of the old record. It isn't an error; it typically clears up on its own once that resolver's cache expires.
Which record types can I check propagation for?
A, AAAA, CNAME, MX, TXT, and NS records, plus dedicated SPF and DMARC checks that read the relevant TXT record and summarize it for you.
I changed my nameservers — why does propagation take longer?
A nameserver change has to propagate at two levels: first the registry/registrar record pointing to your new nameservers, then every individual DNS record served by those nameservers. The first step can itself take up to 24-48 hours depending on your registrar and the domain's TTL at the parent zone, which is why nameserver migrations often feel slower than a simple record edit.