Developer Tools
JSON FormatterBase64 Encoder / DecoderHTML Minifier & BeautifierMarkdown PreviewerRegex TesterDNS LookupView all 25

DNS Lookup

Look up A, AAAA, MX, TXT, NS, and CNAME records for any domain, all at once.

Runs in your browserNo sign-up required

Every Record Type, One Lookup

Rather than checking one record type at a time, this queries every common type simultaneously — A, AAAA, MX, TXT, NS, CNAME, and SOA — through a public DNS-over-HTTPS resolver, useful for a quick full picture of how a domain is actually configured.

How to Use This Tool

  1. 1Enter a domainAny registered domain, with or without "www.".
  2. 2Get every record type at onceA, AAAA, MX, TXT, NS, CNAME, and SOA, checked simultaneously.
  3. 3Read the resultsEach record's value and TTL (how long it's cached before a resolver re-checks it).

Good to Know

  • Lookups run through a public DNS-over-HTTPS resolver rather than your own network's DNS, so results reflect what most of the internet currently sees — useful when checking if a DNS change has actually propagated.
  • TXT records commonly hold domain-verification codes (Google Workspace, SPF, DKIM) — an empty TXT result on a domain that should have email authentication set up is worth investigating.
  • A missing MX record means the domain isn't configured to receive email at all, which is expected for many domains that only serve a website.
  • DNS changes can take anywhere from a few minutes to 48 hours to fully propagate depending on the record's TTL — a lookup shortly after making a change may still show the old value.

Frequently Asked Questions

Why do I see different results than "nslookup" on my computer?

This tool queries a public DNS-over-HTTPS resolver rather than whatever DNS server your device or network is configured to use — results can briefly differ from your own machine's cache while a change is still propagating.

What does the TTL number mean?

Time-to-live, in seconds — how long a DNS resolver will cache that record before checking again. A record with a low TTL (like 60) updates quickly across the internet after a change; a high TTL (like 86400, one day) takes longer to propagate.

Why does a domain show no A record but still resolves in a browser?

The domain may only have an AAAA (IPv6) record, or the specific subdomain checked (like a bare domain vs. "www") may be configured differently — try both forms if results look incomplete.

Is this free to use?

Yes, completely free, with no account and no limit on how many lookups you run.