Free DNS Propagation Checker
Changed a DNS record and not sure it has spread? Type a domain, pick a record type and see what 23 public DNS resolvers in 4 regions answer right now. Each one is marked green when it agrees with most of the others and amber when its answer is different, and the answers appear as they arrive.
How to read the result
Matches
That resolver returns the same answer as most of the others. When every row matches, the change has reached everyone we ask.
Different answer
That resolver returns something else: the old value still cached, or a different address handed out on purpose by a site on several servers. Look for the new value in the answers list instead of counting marks.
No reply
That resolver did not answer within 3 seconds, or refused. It says nothing about your DNS. Check again in a moment.
Look at the answers, not only the marks. The list above the resolvers shows each distinct answer and how many resolvers return it. Mid-change you will see two: the old value and the new one. When the old one reaches zero, the change has propagated.
"No records" and "No such domain" are answers too. A resolver that says the name has no record of that type, or that the name does not exist, is answering, and is compared with the others like any other answer. It is a different thing from No reply.
Some differences are normal. Large sites and content networks give different callers different addresses on purpose, and a resolver that filters malicious domains may refuse to return a flagged name. See the questions below for how to tell a slow change from a permanent difference.
The 23 resolvers we ask
Public resolvers from different operators, countries and networks, in this order. The list is fixed, and you cannot point the checker at any other address. The country is where the operator is based.
| Region | Resolver | Based in | Address |
|---|---|---|---|
| North America | Google Public DNS | United States | 8.8.8.8 |
| Cloudflare | United States | 1.1.1.1 | |
| Cisco OpenDNS | United States | 208.67.222.222 | |
| Lumen (Level 3) | United States | 4.2.2.1 | |
| Verisign Public DNS | United States | 64.6.64.6 | |
| Comodo Secure DNS | United States | 8.26.56.26 | |
| Hurricane Electric | United States | 74.82.42.42 | |
| UltraDNS Public | United States | 156.154.70.1 | |
| CleanBrowsing Security | United States | 185.228.168.9 | |
| Control D | Canada | 76.76.2.0 | |
| CIRA Canadian Shield | Canada | 149.112.121.10 | |
| Europe | Quad9 | Switzerland | 9.9.9.9 |
| AdGuard DNS | Cyprus | 94.140.14.140 | |
| DNS.SB | Germany | 185.222.222.222 | |
| DNS.WATCH | Germany | 84.200.69.80 | |
| DNS4EU | European Union | 86.54.11.100 | |
| Yandex DNS | Russia | 77.88.8.8 | |
| Asia | AliDNS | China | 223.5.5.5 |
| DNSPod | China | 119.29.29.29 | |
| 114DNS | China | 114.114.114.114 | |
| KT | South Korea | 168.126.63.1 | |
| HiNet | Taiwan | 168.95.1.1 | |
| South America | Oi | Brazil | 200.221.11.100 |
Several of these (Google, Cloudflare, Quad9 and others) are anycast: one address is served from many sites worldwide and our request reaches the nearest. They show what that network's resolver returns, not what a particular internet provider's customers see.
TTL: how long a resolver may keep an answer
The TTL on a record is the longest a resolver may keep its copy, so it is also the longest you wait for a change to reach it.
| TTL (seconds) | Time | Typical use | Wait after a change |
|---|---|---|---|
| 60 | 1 minute | A record you are about to move, or a failover address | A minute or two |
| 300 | 5 minutes | Busy sites and records that change now and then | About 5 minutes |
| 3600 | 1 hour | The usual default at most DNS hosts | Up to an hour |
| 14400 | 4 hours | Mail (MX) and other records that rarely change | Up to 4 hours |
| 86400 | 24 hours | Stable records, and some registrars' defaults | Up to a day |
| 172800 | 48 hours | Name server (NS) records held by the registry | Up to 2 days |
Planning a move? Lower the TTL to 300 or 60 seconds at least one old TTL before you change the record, change it, confirm here that every resolver returns the new value, then raise the TTL again. A lower TTL means more lookups to your name servers, so there is no reason to keep it low once the move is done.
Moving mail? Mail servers retry for days, so a short overlap is rarely a problem, but keep the old mail server running until the MX check above shows only the new one. The MX record lookup shows the mail setup, and the SPF record checker and DMARC checker show whether the records around it are right.
Frequently asked questions
What is DNS propagation?
It is the time it takes for a change to a DNS record to be seen everywhere. Nothing is pushed out. When you change a record at your DNS host, the new value is available at once from your domain's own name servers. DNS resolvers, the servers that internet providers, companies, Google and Cloudflare run to answer lookups, each keep a copy of every answer they gave for as long as the record's TTL allows, and ask again only when it runs out. Propagation is those copies expiring at different moments around the world.
What is TTL, and why does it matter?
TTL (time to live) is the number of seconds a resolver may keep an answer before it asks again. You set it per record at your DNS host: 3600 means one hour. A resolver that fetched the old value a minute before your change keeps serving it for almost the whole TTL. In the A and AAAA results above, the TTL shown is how many seconds that resolver says are left on the copy it holds, so it counts down each time you check again.
Why do some resolvers show a different answer?
Five common reasons. Their copy of the old answer has not expired yet. Your DNS host gives different callers different answers on purpose (round robin, load balancing or answers by location), which is normal. A resolver that filters malicious domains blocks or rewrites the answer for a name it flags. One of your own name servers still holds old data, which shows as a split that never closes. Or that resolver simply did not reply in time, which is shown as No reply rather than as a different answer.
How long does DNS propagation take?
For most changes, about as long as the old record's TTL: a few minutes at 300 seconds, an hour at 3600, up to a day at 86400. Changing the name servers of a domain at your registrar takes longer, often up to 48 hours, because the old name servers are cached at the registry. A record that never existed before usually shows up quickly, but a resolver that was asked earlier and was told there was none may keep that answer for a while (negative caching, set in the domain's SOA record).
The TTL has passed but one resolver still shows the old answer. Why?
Check, in this order: the TTL you actually had on the old record (a TTL you lowered only applies to copies fetched after you lowered it); whether every one of your name servers carries the new value (look at the NS records here, and confirm the new value in your DNS host's dashboard); whether that resolver is one that keeps answers longer than the TTL asks; and whether the result came from our 30 second cache, in which case Check again after half a minute.
Can I make DNS propagate faster?
Not after the fact, but you can plan for it. Lower the TTL of the record to 300 or 60 seconds at least one old TTL before the change, make the change, and raise it again afterwards. Google Public DNS and Cloudflare each offer a page that flushes a single name from their cache. And flush your own computer's DNS cache (on Windows, ipconfig /flushdns), because the box in front of you has a cache of its own.
Does this show what my own computer sees?
No. It shows what each public resolver returns when we ask it from our servers. Your computer asks the resolver your network hands out, usually your router or your internet provider's, and keeps its own cache and hosts file as well, so it can differ. Several of the resolvers listed (Google, Cloudflare, Quad9 and others) are anycast: one address is served from many sites around the world and we reach the nearest one. The country shown is where the operator is based, not a promise of where the answering machine is. Internet provider resolvers that only answer their own customers cannot be checked from outside.
Which resolvers does it ask?
23 public resolvers run by different operators in different countries and networks, listed in the table above. The list is fixed: you cannot add a resolver or point the checker at any other address, and it only ever asks about the domain you type.
Which record types can I check, and how do I check DKIM or DMARC?
A, AAAA, CNAME, MX, NS and TXT. DMARC, DKIM and SPF all live in TXT records: for DMARC, check the TXT record of _dmarc.yourdomain.com; for a DKIM key, check selector._domainkey.yourdomain.com, with your own selector. The tool accepts names that start with an underscore for exactly this reason.
Is my domain saved?
No. The check runs when you press the button. We keep the answers in memory for 30 seconds so that a repeat check does not ask the resolvers again, and to apply its hourly limit we keep a counter against your address for up to an hour. We count how many checks are run by record type, never which domain.
Is the DNS propagation checker free?
Yes: no signup, no software to install and no charge. To keep it fair it allows 30 checks an hour from one address.