DNS Propagation Checker
Compare a DNS record across global resolvers.
Enter a host name and record type to see what resolvers around the world are returning right now. When you change a DNS record it takes time to reach every resolver, and this check shows whether the new value has spread evenly or is still catching up.
This tool queries the same DNS record from several public resolvers around the world at once and shows you the answer each one returns. It is how you confirm that a change you made, such as a new SPF, DKIM, DMARC, MX or TXT record, has reached the wider internet, and not just your own machine, before you rely on it.
How DNS changes actually spread
When you edit a record at your authoritative DNS host, the change is live there immediately, but resolvers elsewhere may still be serving the previous answer from cache. How long they keep it is governed by the record's TTL (time to live): a record with a TTL of 3600 can be cached for up to an hour. "Propagation" is really these caches expiring at different times, which is why one resolver can show the new value while another still shows the old one. Lowering the TTL before you make a change shortens this window for next time.
Reading the results and fixing mismatches
If every resolver agrees and shows your new value, the change is effectively global and you can proceed to verify it with the relevant checker. If some still show the old value, that is normal caching, so wait for the TTL to elapse and re-check. But if resolvers disagree in a way that does not settle, look for a real fault: a record published on the wrong name, multiple conflicting records, a typo at one of several DNS providers, or a stale secondary nameserver. For authentication records this matters because a verifier might query a resolver that still has the old answer; a half-propagated DMARC, SPF or DKIM record can cause intermittent failures. Once propagation is complete, confirm the value itself is correct with the matching tool. If you would rather not babysit DNS changes, DMARC Engine hosts and manages these records for you.
Frequently asked questions
Why do resolvers show different answers for the same record?
Because each resolver caches its own copy and those caches expire at different times. After you change a record, some resolvers serve the new value straight away while others keep the old one until its TTL runs out. This is normal and resolves itself once the caches expire.
How long does DNS propagation take?
It is bounded by the record's TTL. A record cached with a TTL of 3600 seconds can take up to an hour to refresh everywhere; a TTL of 300 takes about five minutes. There is no single global timer; it is the sum of many caches expiring.
Can I make changes propagate faster?
You cannot speed up a change already in flight, but you can prepare. Lower the record's TTL well before you plan to edit it, wait for the old long TTL to expire, then make the change so the new value spreads quickly. Raise the TTL again once you are settled.
Some resolvers still show the old record after a day. What is wrong?
If it persists far beyond the TTL, suspect a real configuration fault rather than caching: a duplicate or conflicting record, an edit applied at only one of several DNS providers, or a secondary nameserver that has not synced. Check your authoritative records directly.
Why does propagation matter for email authentication?
A receiving mail server may query a resolver that still holds the old answer. During propagation a verifier could read a stale or absent DMARC, SPF or DKIM record, causing intermittent authentication failures until every cache has refreshed.
Does this tool tell me if my record is correct?
No. It only shows what each resolver currently returns, so you can confirm a change has spread. To validate that the value itself is well-formed, run it through the dedicated checker for that record type once propagation is complete.