dev101.io

DNS Lookup

Resolve any hostname to A, AAAA, MX, TXT, NS, CNAME, SOA, and CAA records — live, via Cloudflare DoH.

Loading tool…

How to use DNS Lookup

  1. Type a hostname (e.g. `example.com`, `mail.google.com`).
  2. Pick a record type from the dropdown — A for IPv4, MX for mail, TXT for verification strings, etc.
  3. Hit "Look up" — answers load in under a second from the nearest Cloudflare edge.
  4. Click "Copy" to grab all answers in tab-separated format (name / TTL / type / data).

DNS Lookup

Resolve any hostname to A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, PTR, or SRV records. Powered by Cloudflare's DNS-over-HTTPS endpoint, queried directly from your browser.

What you can do

  • A / AAAA — which IPs does example.com point to?
  • MX — who handles mail for this domain?
  • TXT — read SPF, DKIM, DMARC, or domain-verification records
  • NS — what nameservers is this domain delegated to?
  • CNAME — what does this alias point to?
  • SOA — zone authority, serial, refresh intervals
  • CAA — which certificate authorities are allowed to issue certs for this domain?

Privacy

DNS queries are issued from your browser to Cloudflare over HTTPS. We never see the hostname you looked up. Our page loads no trackers, no analytics, no third-party fonts. Cloudflare's own 1.1.1.1 privacy notice applies to what they see.

Compared to dig

dig is the gold standard command-line tool — it shows you the entire wire format and handles every record type in the registry. This page is for when you want to look something up from your phone, share a result with a colleague, or avoid opening a terminal. The answers match dig (both use real DNS), just formatted for humans.

Related

  • Is My Website Alive? — check if that IP is actually answering
  • What's My IP? — see the address the internet thinks you are
  • URL Parser — break down a full URL into its parts

Frequently asked questions

Where does the DNS query go?

Directly from your browser to Cloudflare's DNS-over-HTTPS endpoint (`https://cloudflare-dns.com/dns-query`). Our server doesn't proxy it — the fetch leaves your device, hits Cloudflare, and returns. That means Cloudflare sees the hostname you looked up (they publish a privacy-friendly policy at 1.1.1.1/privacy), but we never do.

Which record types are supported?

A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, PTR, and SRV. That covers 99% of day-to-day DNS debugging — IP lookups, mail routing, TXT verifications (SPF, DKIM, DMARC, domain-verification), nameserver changes, and certificate authority pinning. For less common types (NAPTR, DNSKEY, RRSIG), use `dig` on the command line.

Why does TXT come back as one big string?

TXT records are natively chunked into 255-byte segments, each wrapped in quotes in the DoH JSON response. We concatenate the quoted chunks so `"v=spf1 include:" "_spf.example.com ~all"` becomes the single string `v=spf1 include:_spf.example.com ~all` — what you probably want to see. The authoritative raw bytes are still what they are; we're just hiding the wire-format detail.

What does "DNSSEC verified" mean?

Cloudflare's resolver validated the signature chain for the domain you looked up. If you see that badge, the answer is cryptographically vouched for by the zone — nobody tampered with it between the authoritative server and Cloudflare. If the badge is absent, the domain either doesn't use DNSSEC or the chain failed to validate.

Related tools