DNS Lookup

One input per line. Output is numbered to match the input order.
Pinned tools are listed in your favourites on the home page.Copies a link to this tool that carries your current input, so it opens ready to run.Gives you an iframe snippet for putting this tool on your own site.

DNS lookup via Google DNS-over-HTTPS. Results may be cached by your browser.

Ctrl+Enter Run  · Ctrl+Shift+C Copy  · Esc Clear

Understand DNS Lookup

Queries live DNS records — A, AAAA, MX, TXT, NS, CNAME, and SOA — for any domain and shows the values with their TTLs.

How it works

The query goes to Google's public resolver over DNS-over-HTTPS, which returns JSON instead of the binary wire format, so a browser can ask a question that normally requires a UDP socket. Choosing "ALL" issues six parallel lookups (A, AAAA, MX, TXT, NS, CNAME) and merges the answers. The TTL beside each record is not the value the zone author configured — it is the seconds remaining before that resolver discards its cached copy, so it counts down between refreshes and resets to the authoritative value when the cache expires.

When to use it

  • Verifying that MX, SPF, DKIM, and DMARC records exist and read correctly before blaming a mail provider for deliverability
  • Confirming that a new A or CNAME record has actually published after a registrar or DNS-provider change
  • Finding which nameservers a domain currently delegates to when a transfer looks incomplete
  • Checking whether a hostname resolves to IPv6 at all before debugging a client that prefers AAAA

Watch out for

  • This is one vantage point, not the world. A record can be live in Google's resolver and still be cached stale in your ISP's — a clean answer here does not prove global propagation.
  • A CNAME cannot coexist with other records at the same name, and it is not allowed at a zone apex. If `example.com` needs to point at a load balancer, the answer is an A record or a provider-specific ALIAS/ANAME, not a CNAME.
  • A single TXT string is capped at 255 bytes, so long DKIM keys and SPF records are published as several quoted strings that concatenate. A record that looks truncated may just be chunked.
  • DNS-over-HTTPS routes the query to a third party. The domains you look up here are visible to Google's resolver, which is the tradeoff for being able to query DNS from a web page at all.

Frequently Asked Questions

How to look up DNS records?

Enter a domain name and select a record type (A, AAAA, MX, TXT, NS, CNAME, SOA, or PTR). The tool queries Google DNS-over-HTTPS and returns the current records with TTL values. No installation required — results reflect the live public DNS state.

What is DNS propagation?

DNS propagation is the time (up to 48 hours) for updated DNS records to spread across global resolvers. Lower TTL values propagate faster. Use this tool against multiple nameservers to check if propagation is complete in specific regions.

How do I check if my email DNS records are correct?

Query MX records to verify your mail server is listed. Check TXT records for SPF (v=spf1...), DKIM (_domainkey subdomain), and DMARC (_dmarc subdomain). Missing or misconfigured SPF/DKIM/DMARC records cause emails to land in spam.

How to Use DNS Lookup

  1. Paste or type your input in the input area above.
  2. The tool processes your input automatically or click Run.
  3. Copy or download the result using the action buttons.
  4. Use Ctrl+Enter to run quickly from the keyboard.