DNS Checker — Check DNS Records Globally Free

A DNS checker is one of the most useful tools for anyone who manages a website or online service. It queries the DNS records for a domain and displays them in a readable format. You can use it to verify that your DNS configuration is correct, check propagation status, or investigate a domain you do not control.

Our DNS checker goes a step further than a simple lookup. It queries your domain from multiple geographic locations simultaneously and compares the results. This tells you whether your DNS records are consistent worldwide or if different regions see different values.

What a DNS Checker Does

A basic DNS checker performs a lookup for a specific record type and returns the value. Our checker does that for all common record types at once. You get a complete picture of a domain's DNS configuration in a single query.

The checker queries A records (IPv4 address), AAAA records (IPv6 address), CNAME records (aliases), MX records (mail servers), TXT records (text data including SPF and DKIM), and NS records (nameservers). It also returns the SOA record showing the authoritative server and zone serial number.

For each record, the checker shows the TTL value. Low TTLs mean the record changes quickly. High TTLs mean better caching efficiency but slower updates. If you see a TTL that does not match what you configured, the resolver might be overriding it.

Why Multi-Location Checking Matters

DNS is distributed by design. There is no single source of truth that every resolver queries. Different resolvers in different parts of the world can return different results for the same domain. This happens for several reasons.

Anycast DNS routing sends queries to the nearest available server. If you use a DNS provider with anycast, a resolver in Australia connects to a different physical server than a resolver in Brazil. If your DNS records have not fully propagated to all servers, the results will differ.

Geo DNS intentionally returns different results based on the query origin. Many CDNs and global websites use geo DNS to route visitors to the nearest server. A DNS checker that queries from multiple locations reveals which version of your site each region sees.

ISP caching policies vary wildly. Some ISPs honor TTL values. Others cache DNS responses for as long as they want. A multi-location check shows you which ISPs are respecting your TTL settings and which are not.

When to Use a DNS Checker

After making DNS changes, use the checker to confirm the new records are live. Check from at least two or three locations to ensure propagation is progressing. If your primary region shows the change but a different continent does not, you know propagation is still happening.

Before migrating a website, use the checker to document the current DNS configuration. Take a screenshot or save the output. If something goes wrong during the migration, you have a reference to restore from.

When troubleshooting email delivery issues, check the MX and TXT records. Missing SPF, DKIM, or DMARC records are common causes of email rejection. The checker shows you exactly what email authentication records are published.

For investigating suspicious domains, the checker reveals the DNS configuration without making direct contact. You can see where a domain resolves to, what mail servers it uses, and what services it might be running.

For a deeper look at individual record types, try our DNS lookup tool. For tracking propagation over time, use the propagation checker.

Tips for Using a DNS Checker Effectively

Clear your local DNS cache before using the checker. Your computer might cache old records and give you stale results. On Windows, run ipconfig /flushdns. On Mac, run sudo dscacheutil -flushcache.

Check multiple record types, not just A records. Many DNS problems are invisible if you only look at the IPv4 address. A missing MX record causes email failures even when the website loads fine. A missing TXT record can break SPF authentication without affecting browsing.

Compare results across different DNS providers. If Cloudflare's resolver sees different records than Google's, there might be a propagation delay or a configuration issue specific to one nameserver. This is especially important if you use multiple DNS providers for redundancy.

For authoritative checks, query the nameservers directly instead of using a recursive resolver. Use dig with the @nameserver syntax: dig @ns1.example.com example.com A. This bypasses caching and shows exactly what the authoritative server is serving.