All Tools

DNS Lookup

Query DNS records for any hostname.

DNS (Domain Name System) is the phonebook of the internet. It translates domain names like example.com into IP addresses that computers use to communicate. Every website visit, email sent, or API call starts with a DNS lookup.

Several record types serve different purposes: A maps to IPv4, AAAA to IPv6, MX routes email, CNAME creates aliases, TXT stores SPF/DKIM data for email security, NS points to nameservers, and SOA holds zone admin info.

This tool queries all key record types for any domain — useful for troubleshooting mail delivery, verifying DNS propagation, and diagnosing connectivity issues.

cloudflare.comnetflix.com
Want the full picture?
Run a free Website Health Check →

Common questions

This tool queries A (IPv4), AAAA (IPv6), MX (mail), TXT, CNAME, and NS (nameserver) records for any domain in real time.

The domain may not have that record type configured, or DNS changes may still be propagating. Try our DNS Propagation Checker to see if updates have reached global resolvers.

Yes. Lookups run in real time with no account required. We do not store your queries or results.

What this DNS lookup checks

This tool queries live authoritative and recursive DNS infrastructure for A (IPv4), AAAA (IPv6), MX (mail routing), TXT (SPF, DKIM, verification strings), CNAME (aliases), and NS (nameserver delegation) records. Results come directly from DNS — not a cached third-party database — so you see what resolvers would return right now.

When to use DNS lookup

  • Verify a new A record points to the correct server IP after deployment
  • Confirm MX records before switching email providers
  • Inspect TXT records for SPF, DKIM, or domain verification tokens
  • Troubleshoot "site works for me but not others" propagation issues
  • Audit nameserver delegation after transferring a domain

How to interpret results

A / AAAA records tell browsers where to connect. Multiple A records may indicate load balancing. MX records include priority numbers — lower numbers are tried first. If email bounces, compare MX here with what your mail provider documents. TXT records often hold SPF (v=spf1), DKIM public keys, or Google/Microsoft verification strings. CNAME chains can add latency; apex domains usually use A records instead. NS records show who controls your DNS — if these are wrong, every other record is suspect.

Common failure cases

  • No records returned — domain may be unregistered, expired, or the record type simply does not exist
  • Unexpected IP — stale A record after migration; purge CDN cache and check TTL
  • Missing MX — email cannot be delivered to the domain
  • SPF permerror — too many include: mechanisms in TXT; combine or flatten SPF
  • CNAME at apex — many DNS providers disallow this; use ALIAS/ANAME or A record instead

Example scenario

A developer deployed a staging subdomain but visitors saw the production site. DNS lookup showed staging.example.com had a CNAME to example.com instead of the staging host. Updating the CNAME target fixed routing without touching application code.

Limitations

DNS results can vary by resolver location and cache TTL. For global propagation status, use our DNS Propagation Checker. We query standard record types only — not DNSSEC chain validation or zone transfers.

Related resources

What Is DNS? · How DNS Propagation Works · DNS, Email & SSL Checklist · Website Health Check