DNS Lookup
Look up any domain's DNS records live: A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, HTTPS, DS and more. Your browser asks Cloudflare's or Google's public resolver directly, and you can compare the two side by side.
DNS Lookup
How this lookup works. When you press Look up, your browser sends the question over encrypted DNS-over-HTTPS to Cloudflare's public resolver (1.1.1.1), or to Google Public DNS (8.8.8.8) if you choose it below. The request goes straight from your device to them. It doesn't pass through ToolFeather: we have no server in the path, so we never see or store the names you look up. Requests are sent without cookies or a referrer. Each resolver has its own privacy policy: Cloudflare · Google.
Results appear here.
Queries your browser sent (0)
These are the exact requests, each one a link. Open one to see the raw JSON answer from the resolver.
Live lookup: your browser asks Cloudflare or Google DNS directly. Nothing passes through ToolFeather.
Scratchpad auto-saved
How it works — in four simple steps
No signup and nothing to install — it all runs in your browser.
Type a domain
A host name, URL, email address or IP address all work.
Pick a record type
Or leave All common types to fetch nine types at once.
Choose a resolver
Cloudflare or Google, or tick compare for both.
Read the results
Each record comes with its TTL and a plain-English meaning. Copy them as a zone file if you need to.
Tick compare to ask Cloudflare and Google together. Different answers right after a change mean one cache hasn't caught up yet.
Features
17 record types
A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, SRV, PTR, HTTPS, SVCB, DS, DNSKEY, TLSA, NAPTR and SSHFP, or every common type at once.
Cloudflare vs Google
Ask both resolvers together and see straight away if their answers differ.
Plain-English meanings
Each record is explained: the mail provider behind an MX, the CA behind a CAA, the service behind a TXT token, DNSSEC key roles.
Zone-file export
Copy the results in BIND zone-file format, handy for migrations and documentation.
DNSSEC and status
Shows NOERROR, NXDOMAIN or SERVFAIL, extended DNS errors and whether the answer was DNSSEC-validated.
Nothing via us
Queries go from your browser to the resolver over HTTPS, without cookies or a referrer. The request log shows each one.
About the DNS Lookup
DNS is the internet's address book. A domain's records say where its website lives (A for IPv4, AAAA for IPv6), which servers take its email (MX), who runs its DNS (NS), which certificate authorities may issue its certificates (CAA), and carry text such as SPF policies and ownership tokens (TXT). A CNAME makes one name an alias of another; the newer HTTPS record (RFC 9460) tells browsers about HTTP/3 support and alternative endpoints before they connect.
This tool sends the question to a public recursive resolver using DNS-over-HTTPS, from your browser to Cloudflare (1.1.1.1) or Google (8.8.8.8). The resolver answers from its cache or asks the domain's authoritative servers. That's why the TTL you see is the time left in the cache: ask twice and it counts down. Turn on compare to ask both resolvers at once. A difference usually means a recent change that one cache hasn't caught up with, or a CDN giving location-dependent answers.
Each answer shows its status code: NOERROR (the name exists), NXDOMAIN (it doesn't) or SERVFAIL (the resolver couldn't get a valid answer, often a DNSSEC or name-server fault). DNSSEC ✓ means the resolver validated the signatures. Because the queries go to public resolvers, internal names (split-horizon DNS, .local, intranet zones) can't be seen from here. Use dig or nslookup on your own network for those.