DNS Lookup

// query A, AAAA, MX, TXT, NS, CNAME & SOA records for any domain

A AAAA MX TXT NS CNAME SOA CAA
NameTypeTTLData

What does this tool check?

It queries Google's public DNS-over-HTTPS resolver (dns.google/resolve) directly from your browser and shows every DNS record of the selected type for the domain you enter — the same kind of answer your computer gets when it resolves that domain, but visible and inspectable.

How to use this tool

  • Enter a domain and pick a record type, then click Lookup
  • A / AAAA — the IPv4/IPv6 address(es) a domain resolves to
  • MX — which mail servers handle email for the domain
  • TXT — verification tokens, SPF/DKIM/DMARC policy strings
  • NS — which nameservers are authoritative for the domain

Why DNS lookups matter for debugging

Most "site is down" or "email isn't arriving" problems trace back to DNS. If a domain's A record points at the wrong IP, visitors hit nothing. If MX records are missing or misconfigured, inbound mail silently bounces or gets rejected. If a TXT record for SPF/DKIM/DMARC is wrong, outbound mail gets flagged as spam even though the mail server itself works fine.

DNS changes also don't take effect everywhere instantly — each record has a TTL (time-to-live) in seconds, and resolvers cache answers until that TTL expires. A DNS lookup tool run from a resolver you don't control (like this one, via Google's public DNS) is a quick way to check what's actually propagated, independent of your own machine's local DNS cache.

Frequently Asked Questions

Where does this data come from?+
Google's public DNS-over-HTTPS API at dns.google/resolve — the same infrastructure behind Google's 8.8.8.8 public resolver, queried securely over HTTPS instead of plain UDP.
Why do I see different results than "dig" or "nslookup" on my machine?+
Your machine likely uses a different DNS resolver (your ISP's, or a local cache) which may have older cached answers. This tool always asks Google's resolver directly, so it's useful for confirming what's actually propagated versus what's stuck in a local cache.
What does an empty result mean?+
It means that record type doesn't exist for the domain — not necessarily an error. For example, most domains have no CAA record, and a domain using a subdomain redirect may have no MX record at all if it doesn't handle email.

Related tools

NPM Package Inspector → URL Encoder → JWT Decoder → Domain Availability Checker → All tools →