Skip to content
ToolMug

DNS Propagation Checker

After changing an A, CNAME or MX record, check whether the new value is live. The tool asks the domain's authoritative name server for the current setting, compares it with six popular public DNS resolvers, flags any still serving the old record and estimates when their caches expire.

Processed on our server; nothing is stored

How to use

  1. Enter the domain you changed (for example www.example.com) and pick the record type.
  2. Click Check. The first row is the authoritative server's current setting; below are each public resolver's answer and status.
  3. If some show Old record, check again after the time shown, or tick Re-check every minute and wait.

Options explained

Authoritative server
The server your NS records point to, usually your DNS provider. Its answer is what you set in the control panel.
Updated / Old record
Updated means the resolver returns the same value as the authoritative server. Old record means it is still using its cache until the TTL runs out.
TTL
For public resolvers this is the seconds left before the cached answer expires; for the authoritative server it is the TTL you set.

How the answers are compared

The tool compares only the records on the exact name you entered, such as the CNAME on www.example.com or the A records of the name itself. The IP addresses further down a CNAME chain are ignored, because a CDN can legitimately return different ones to different resolvers. Domain names are compared without regard to case and a trailing dot; TXT values are compared exactly.

Status Meaning
Updated Same records as the authoritative server
Old record Different records, still served from the cache
No record The resolver returned nothing for this name
Failed The query timed out or could not be completed

The wait shown for resolvers that still differ is the longest remaining TTL among their answers, so it is an upper bound: some may refresh sooner. If the authoritative server does not answer, the most common answer among the public resolvers is used as the reference instead.

Frequently asked questions

How long does DNS propagation take?

It depends on the old record's TTL. Resolvers keep the cached value until it expires; brand-new records usually appear within minutes. Lower the TTL (for example to 600 seconds) before your next change to make it faster.

Why do resolvers show different IPs but still say Updated?

With a CDN or geo DNS, different locations legitimately get different IPs. The tool compares the record on the name itself (such as where a CNAME points); the final IPs are shown for reference.

Are the Google and Cloudflare results reliable?

Queries are sent from our server in mainland China. For domains blocked there, queries to overseas resolvers may be tampered with and return wrong addresses; ordinary sites are not affected.

Does it test from locations around the world?

No. It compares a few public resolvers with the authoritative server; it is not a multi-location probe. Your ISP's resolver has its own cache too.

Privacy

This tool needs our server: what you enter or upload is sent over HTTPS, processed and then discarded, never stored. Server access logs record IP addresses and request URLs, used only to prevent abuse.

Related tools