DNS Propagation Checker Tool Online

Last updated:

Compare live DNS answers across multiple public resolvers to see whether records are consistent, still propagating, or misconfigured before a launch.

Enter a domain and choose the DNS record type:

How the DNS Propagation Checker Works

This tool asks multiple public DNS-over-HTTPS resolvers for the same domain and record type.

  1. Domain validation, the API accepts a domain only, not a URL or path.
  2. Parallel resolver queries, Cloudflare, Google, and AdGuard DNS are queried at the same time.
  3. Record comparison, answers are sorted and compared across resolvers.
  4. Propagation verdict, matching records suggest consistency, while differences suggest propagation or configuration drift.

Why DNS Propagation Matters

DNS mistakes can break websites, contact forms, email delivery, and search visibility during a migration or launch.

  • Website launches, confirm A or CNAME records point to the right hosting platform.
  • Email reliability, check MX and TXT records before changing SPF, DKIM, or DMARC.
  • SEO stability, wrong records can take pages offline and cause crawl errors.
  • Migration safety, use this alongside our DNS records guide.

Common DNS Record Types

TypeUsed forLaunch risk
APoints a domain to an IPv4 address.Wrong value can send traffic to the wrong server.
CNAMEAliases one hostname to another.Common for Vercel and CDN connections.
MXControls mail delivery.Wrong value can stop email.
TXTStores SPF, DKIM, DMARC, verification, and policy values.Mistakes can affect email and platform verification.
NSIdentifies authoritative nameservers.Nameserver changes often take longest to stabilize.

For a single resolver view, use the DNS Lookup Tool.

DNS TTL & Propagation Reference

Propagation takes time because of caching. Every DNS record carries a TTL (time to live), the number of seconds a resolver may keep a cached copy before fetching a fresh answer. When you change a record, resolvers that already cached the old value keep serving it until their TTL expires, which is why different resolvers can show different answers during a change window. Lower TTLs propagate faster; nameserver changes are slowest because the parent zone often uses TTLs measured in days. The table below shows typical TTLs and what to expect.

Record / scenarioTypical TTLPropagation note
A / AAAA300 to 3600 sec (5 min to 1 hr)Updates within minutes to an hour once caches expire. Lower the TTL before a migration for a faster cutover.
CNAME300 to 3600 secBehaves like A/AAAA. Common for CDN and platform connections, where providers often suggest a specific TTL.
MX3600 to 86400 sec (1 to 24 hr)Often higher because mail routing changes rarely. Lower it ahead of an email provider switch to avoid delivery gaps.
TXT (SPF/DKIM/DMARC)3600 sec (1 hr)Plan an hour for verification and policy changes to be seen consistently across resolvers.
NS (nameservers)86400 to 172800 sec (1 to 2 days)Slowest to change. The parent zone publishes long TTLs, so a nameserver switch can take 24 to 48 hours to fully settle.
Lowered TTL before a change60 to 300 sec (1 to 5 min)Set this in advance, then wait one old-TTL window before the real edit so resolvers refresh quickly at cutover.

Planning a launch or migration where DNS, SSL, and email records all change at once? Our website maintenance services handle the cutover so traffic and inboxes never break.

Next steps

DNS Propagation Checker related tools and articles

Continue with the closest follow-up checks and guides based on this tool's topic, crawl intent, and optimization workflow.

DNS Propagation Checker: FAQ

Which resolvers and record types does this propagation check use?
It sends DNS-over-HTTPS queries to Cloudflare, Google, and AdGuard DNS. You can select A, AAAA, CNAME, MX, TXT, or NS. The result lists the returned record strings and any resolver-specific request error.
What does Consistent mean in this report?
Consistent means the three sorted record arrays are identical as returned to this request. It does not prove that every recursive resolver worldwide has the same cache, that the authoritative zone is correct, or that clients can reach the service behind the record.
Why can all three resolvers return no records?
The hostname may not publish that record type, the name may not exist, or a DNS-over-HTTPS request may have failed. Read each resolver error before treating identical empty arrays as a healthy consistent result, then query the authoritative nameserver when the record should exist.
Why do the three resolvers show different values?
They may hold answers cached at different times, receive location-dependent DNS responses, or refresh from different authoritative servers during a change. Compare the record TTL and authoritative answer, then retest after the relevant cache window.
What input format does the tool accept?
Enter an ASCII domain or hostname such as example.com or app.example.com. Full URLs, ports, paths, email addresses, spaces, and single-label names are rejected. Convert an internationalized name to its DNS-compatible punycode form before using this input.
How should I plan a DNS change for faster convergence?
Lower the existing TTL before the cutover and wait at least one old-TTL period so recursive caches learn the shorter value. Make the change, verify the authoritative records, monitor several resolvers, and raise the TTL again only after the new answer is stable.
Does this replace an authoritative DNS check?
No. It samples three recursive resolvers and does not query each authoritative nameserver directly, show delegation data, or validate DNSSEC. Use authoritative queries and registrar checks when diagnosing nameserver, glue, signing, or zone-publication problems.
What data is sent during a propagation check?
The domain and selected record type are sent to the Web Aloha API, which forwards public DNS-over-HTTPS queries to Cloudflare, Google, and AdGuard DNS. The form asks for no credentials or personal information, and the endpoint contains no application-storage step for the query or results.

Free 48-Hour Website Audit

Not sure what to fix first on your own website? We'll review it and tell you, in plain English. Free & non-obligatory.

Need DNS Launch Support?

We handle DNS, redirects, SSL, email records, and Vercel go-live checks so site launches do not break traffic or inboxes.