DNS Diagnostics

Query DNS records for any domain from public resolvers, bypassing your local cache.

Why query from public resolvers

Your operating system caches DNS answers, and your ISP resolver may keep serving stale records during propagation. Asking public resolvers (Cloudflare, Google) directly gives you the authoritative-enough view of what the world sees right now.

Reading each record type

A / AAAA map a hostname to IPv4 / IPv6 addresses; CNAME is an alias; MX lists mail servers in priority order; TXT carries SPF / DKIM / verification strings; NS delegates the zone; CAA restricts which CAs may issue certificates.

Diagnosing propagation

Changed a record but still see the old value? Compare TTLs and query different resolvers here — if Cloudflare shows the new value but Google still shows the old, propagation is simply in flight.

Need the in-depth Chinese version? Read the full guide.

Related articles

More in the blog index

Frequently asked questions

Why does the result differ from nslookup on my machine?

Your local resolver caches answers for the TTL duration, and some ISPs override answers. This tool queries public resolvers directly, so it shows what independent resolvers see.

What is a CAA record for?

CAA declares which certificate authorities are allowed to issue certificates for the domain. It is a hardening measure; absence of CAA does not prevent issuing certificates.

Can I check email deliverability here?

Partly — MX, SPF (TXT) and DKIM selectors are visible. For deep diagnostics use a dedicated mail-testing service.