DNS Checker

The DNS Checker is a free tool that queries any domain's authoritative nameservers directly and returns exactly what they publish — its A, AAAA, MX, TXT, NS, CNAME, and SOA records, grouped and formatted into a readable report. Instead of running separate lookups from a terminal or piecing together results from several different tools, you get every major record type for a domain in one pass, exactly as its nameservers currently report it.

It exists because DNS misconfigurations are one of the most common, and most confusing, causes of a site being unreachable or email silently failing to deliver. Whether you're confirming a migration to a new host actually took effect, verifying a new mail provider's records are set correctly, or diagnosing why a third-party verification isn't completing, seeing the raw records directly — rather than guessing from symptoms — is the fastest way to find exactly what's wrong.

When you submit a domain, the tool sends a separate DNS query for each record type — A, AAAA, MX, TXT, NS, CNAME, and SOA — directly to the domain's authoritative nameservers, the same lookup process any browser or mail server performs before connecting or delivering mail. Each response is parsed and grouped by record type into a readable report, showing exactly what those nameservers currently publish for the domain.

This reflects a live query at the moment you run the check, not a cached or historical snapshot — though DNS itself involves caching at every layer between your request and the authoritative nameserver, governed by each record's TTL (time to live) value. A recent change can take anywhere from a few minutes to 24-48 hours to be visible everywhere, which is why a check run immediately after a DNS update may still show the previous values.

• Check MX records first when email breaks. A missing or misconfigured MX record means incoming mail for the domain will bounce entirely, and it's one of the first things worth ruling out.
• Look at TXT records before assuming a deliverability issue is elsewhere. SPF, DKIM, and domain-verification codes all live in TXT records, and a missing or malformed one is a common, easy-to-miss cause.
• Give DNS changes time to spread before troubleshooting. Because of TTL caching, a fresh DNS change can take minutes to days to be visible everywhere, so don't treat the first check as final.
• Confirm NS records match your intended nameservers after a registrar or host change. A leftover NS record pointing at the old provider is a common, quiet cause of a migration not fully taking effect.