Free DNS Propagation Checker

The DNS Propagation Checker is a free online tool that check dns propagation across multiple global resolvers. see if your dns changes have propagated worldwide. It runs entirely in your browser with no installation or sign-up needed.

Typically 1-48 hours depending on TTL values and resolver caching.

Cloudflare (1.1.1.1), Google (8.8.8.8), and Quad9 (9.9.9.9).

Yes, completely free.

Absolutely. The DNS Propagation Checker processes everything client-side in your browser. No data is uploaded to or stored on any server. Your content remains private on your device at all times.

Yes, the DNS Propagation Checker is fully responsive and works on smartphones and tablets. You can use it on any device with a modern web browser -- no app download required.

No account or registration is needed. Simply open the DNS Propagation Checker in your browser and start using it immediately. There are no sign-up walls or usage restrictions.

Simply enter your input in the provided field, adjust any settings to your preference, and the tool will process it instantly. You can then copy the result to your clipboard or download it.

The DNS Propagation Checker works in all modern browsers including Chrome, Firefox, Safari, Edge, and Opera. For the best experience, use the latest version of your preferred browser.

Each resolver keeps its own cache and refreshes records on its own schedule, so right after a DNS edit one resolver may already hold the new value while another is still serving the old one from cache until that cached copy expires. The length of that cache is set by the record's TTL (time to live): a 300-second TTL clears in minutes, while a 24-hour TTL can leave stale answers for a full day. This is exactly why checking a single resolver can mislead you. The tool queries Cloudflare (1.1.1.1), Google (8.8.8.8), and Quad9 (9.9.9.9) side by side and flags any resolver returning a different value as a red Mismatch, so you can instantly see whether a change has spread everywhere or is still rolling out. Enter your domain and pick a record type to compare all three at once.

An A record maps a domain directly to an IPv4 address, so checking it tells you which server a name currently points to — this is what you verify after a web host or server move. A CNAME record is an alias that points one name at another name rather than at an IP, which is common when a subdomain is sent to a CDN or a managed service. The practical difference for propagation: when you change an A record you are watching for a new IP to appear, while with a CNAME you are watching for the new target hostname. Picking the right record type matters because a CDN setup that works correctly may show a CNAME and no A record at the root. The tool lets you check A, AAAA, MX, CNAME, TXT, and NS individually, so select the exact record you edited and run a check.

The single most effective trick is lowering the record's TTL well before you make the actual change. TTL tells resolvers how long to cache an answer, so if you drop it from a common 3600 or 86400 seconds down to 300 seconds a day or two ahead of time, resolvers worldwide will already be refreshing that record every five minutes when your real change goes live. The new value then spreads in minutes instead of hours. After the migration settles you can raise the TTL again to reduce lookup load. You cannot force a cache to clear remotely, but pre-lowering the TTL is the closest thing to it. Once you have made the switch, use the tool to confirm the new value is showing on Cloudflare, Google, and Quad9 — an overall Fully Propagated verdict means every checked resolver now agrees.

NXDOMAIN means "non-existent domain": the resolver looked up the name and the authoritative servers reported that no record of that type exists. It does not always mean the domain itself is unregistered. A common cause is checking a record type the domain genuinely has none of — for example querying an AAAA record on a domain with no IPv6 address, or an MX record on a domain that does not receive email. It can also appear briefly right after creating a brand-new record, before the authoritative servers and caches catch up. If you expect a record to exist, double-check the record type you selected and confirm the value was actually saved at your DNS provider. Run the check across A, MX, TXT, NS, and the other supported types in the tool to see which records are live and which truly return nothing.

Yes. Email and verification changes live in records the tool checks directly. MX records list the mail servers that receive a domain's email, so after switching email providers you check MX to confirm the new servers are answering. TXT records hold text values used for SPF, DKIM, and ownership verification tokens from services like Google Workspace, Microsoft 365, and many others, so a verification that keeps failing is often just a TXT record that has not propagated to every resolver yet. By querying TXT or MX across Cloudflare, Google, and Quad9 at once, you can tell whether a stuck verification is a real configuration mistake or simply caching that time will resolve. Select MX or TXT as the record type, enter your domain, and run a check before re-triggering a verification that may already be on its way.