DNS lookup for A, AAAA, MX, TXT, NS, and CNAME records
Query critical DNS record types instantly to confirm that nameservers, mail routing, and application endpoints are correctly configured. This page helps teams validate cutovers and isolate misconfigurations before users are impacted.
Pair record-level checks with DNS Propagation Check to verify regional resolver convergence and SSL Checker to confirm TLS readiness.
What each record type tells you
- A / AAAA: the IPv4 and IPv6 addresses browsers connect to. Wrong address here means the site loads from the wrong server, or not at all.
- CNAME: an alias to another hostname. Useful for www and vendor-hosted services, but invalid at the domain apex, where it silently breaks MX and other records on many providers.
- MX: the mail servers for the domain, tried in ascending priority order. No MX records means most senders fall back to the A record, which rarely runs a mail server.
- TXT: free-form strings, in practice SPF policies, DKIM keys, DMARC policies, and site-verification tokens.
- NS: the nameservers the domain delegates to. Every other record only matters if these point at the DNS host you actually manage.
Watch the TTL column. It is the number of seconds resolvers may cache each answer, so a TTL of 86400 means a mistake can persist for a full day after you fix it. Before planned changes, drop the TTL to 300 first.
Quick FAQ
Which record type should I check first? Start with A/AAAA for website reachability, then validate MX and TXT for email and authentication.
What does NXDOMAIN mean? The name does not exist at all in the zone. That is different from an empty answer, where the name exists but has no record of the type you asked for. NXDOMAIN usually points to a typo in the record name or a missing subdomain entry.
Why do results differ by resolver? Cached answers and TTL timing can cause temporary differences across regions.
Why does one name return several A records? That is round-robin DNS. Clients may pick any of the listed addresses, so every one of them must point at a working server.
One transposed character in a zone file can take a whole domain offline. See common DNS typos that break everything for the mistakes worth double-checking before you save.