DNS Lookup Tool: Check A, AAAA, CNAME, MX, NS, TXT Records
What DNS lookup tells you
A DNS lookup shows how a domain is configured at the DNS layer. It answers questions like: which IP should this domain resolve to, which mail servers handle email, and which nameservers are authoritative for the zone.
For developers and agencies, this is the quickest way to verify that a DNS change has been applied correctly before blaming code, hosting, or SSL. Misconfigurations here cause broken sites, failed email, and slow propagation.
You can run a full DNS lookup here to see A, AAAA, CNAME, MX, NS, and TXT in one go, or use focused tools like our MX lookup or NS lookup when you only care about mail or nameservers.
Common record types and why they matter
A and AAAA records map your domain to IPv4 and IPv6 addresses. They are what browsers and clients use to connect to your server. Wrong or stale A records are a common cause of "site not found" or traffic hitting the wrong host.
CNAME records alias one hostname to another. They are widely used with CDNs, SaaS subdomains, and load balancers. A CNAME chain that points nowhere or loops will break resolution.
MX records route email for the domain. If they are missing or point to the wrong host, incoming mail bounces. Use our MX lookup to verify mail servers, and our SPF checker to validate sender policy.
TXT records store arbitrary text. They are used for domain verification (e.g. Google Search Console), SPF and DKIM for email, and other metadata. Our SPF checker parses SPF from TXT and flags lookup limits.
NS records indicate which servers are authoritative for the domain. If they are wrong at the registrar, no other record will resolve correctly. After changing DNS providers, confirm with an NS lookup and compare resolvers.
How to use this tool
Enter a domain name (e.g. example.com or sub.example.com), select a resolver, and run the lookup. Results include each record type and, where available, TTL so you can estimate how long caches may keep serving old values.
If you are troubleshooting propagation after a change, select "Query all resolvers" to compare results from multiple public DNS servers. Differences between resolvers mean propagation is still in progress.
For deeper email checks after DNS is correct, run an SMTP test against your mail host and validate SPF so deliverability stays high.
Typical issues this catches
Wrong IP after a deployment: the domain still points to the old server or a staging IP. A quick DNS lookup confirms what the world actually sees.
Missing or incorrect TXT verification records for email or search tools. Many services require you to add a specific TXT record; if it is not present or misspelled, verification fails.
Incorrect MX priorities or typos in mail hostnames. That leads to bounces or mail going to the wrong provider. Cross-check with MX lookup and SMTP test.
Unexpected CNAME chains or CNAMEs at the apex (some providers allow it, many do not). The tool shows the full set of records so you can spot invalid configurations.
When results differ across resolvers, you are likely in a propagation window. Wait for TTL to expire and run the lookup again, or keep comparing with "Query all resolvers" until they align.
When to combine with other checks
Once DNS is correct, use an HTTP headers check to confirm your site returns the right status and security headers. For APIs or custom ports, a port checker verifies reachability.
Monitoring uptime and response times after DNS changes helps you catch regressions early and ensures users never hit a broken or slow endpoint.