100% Client-Side

DNS Lookup

Query DNS records (A, AAAA, MX, NS, TXT, SOA) via Google DNS-over-HTTPS

Free Client-Side No Login No Storage
Loading tool...
IP Address Tools Subnet calculator, CIDR converter, and IPv4/IPv6 address analysis HTTP Header Parser Parse and analyze raw HTTP request or response headers URL Encoder Percent-encode URLs and query strings for safe transmission

How to Use the DNS Lookup

  1. Enter a domain name (e.g. example.com).
  2. Select the record type (A, AAAA, MX, NS, TXT, etc.).
  3. Click Lookup to query Google DNS-over-HTTPS.

Uses the public dns.google DoH API. No server-side code required.

What is DNS Lookup & Domain Analysis?

The DNS Lookup tool queries public domain name system (DNS) records in real time using client-side DNS-over-HTTPS (DoH) via Google and Cloudflare secure resolvers. Query A, AAAA, CNAME, MX, TXT, NS, SOA, and CAA records directly from your browser without requiring command-line `dig` or `nslookup` tools.

Common Uses

  • Verifying domain DNS propagation after configuring new hosting or CDN records
  • Inspecting email authentication TXT records (SPF, DKIM, DMARC)
  • Debugging website downtime, routing issues, and missing CNAME aliases
  • Auditing SSL certification authority authorization (CAA) and name server (NS) delegations

Frequently Asked Questions

How does this tool perform DNS queries without a backend server?

It uses standard DNS-over-HTTPS (DoH) REST APIs provided by Google Public DNS (`dns.google`) and Cloudflare, allowing your browser to fetch cryptographically secure DNS responses directly over HTTPS.

What is the difference between an A record and a CNAME record?

An A record maps a hostname directly to an IPv4 address (e.g. `93.184.216.34`). A CNAME (Canonical Name) record aliases one domain name to another (e.g. `www.example.com` to `example.com`).

Why do my updated DNS records take time to appear globally?

DNS records are cached by intermediate recursive resolvers worldwide according to their TTL (Time to Live) setting. Until the TTL expires, resolvers serve the cached record.

Notes from this implementation

This is the tool that leaves the browser

Every other tool on the crypto and encoding pages keeps the field contents in the page. This one does not. The lookup sends the hostname and the record type to Google Public DNS over HTTPS, at https://dns.google/resolve. The query string contains the name you typed. Do not look up an internal hostname you would not want a public resolver to see.

The response is the resolver’s answer: A, AAAA, MX, TXT, and the other types in the form, plus a TTL. A missing answer can mean “no such record” or “the resolver could not reach a nameserver.” The page shows the answer section. It does not walk the full trace from the root, and it does not bypass a DNS sinkhole on your network if your browser cannot reach dns.google.

TXT records

SPF and site-verification TXT records are long. The table wraps the data. Copy the data cell, not a truncated view, before you compare it with a registrar page.