Tool
DNS Lookup
Query A, AAAA, MX, NS, and TXT records for any public domain. Records come live from Cloudflare DNS-over-HTTPS — the same resolver behind 1.1.1.1.
How it works
Records are fetched live from Cloudflare’s public DNS-over-HTTPS endpoint ( 1.1.1.1/dns). The endpoint returns JSON for the five record types we surface: A (IPv4), AAAA (IPv6), MX (mail), NS (name servers), TXT (free-form). Use the record-type chips above to filter by a specific type.
We don’t cache results — each lookup hits Cloudflare fresh, so you see the current state including very recent changes.
Related tools
Frequently asked
Why use Cloudflare DNS-over-HTTPS instead of a regular DNS query?
DNS-over-HTTPS encrypts the lookup so neither your ISP nor any network between you and the resolver can see which domain you queried. Cloudflare publishes the 1.1.1.1 resolver under their privacy commitment to not log personally identifiable DNS data.
My MX record is missing — does that mean email is broken?
Not necessarily. Some domains route email through a parent zone or rely on the A record fallback (uncommon today). If MX returns empty but the domain is recent, give it a few minutes for propagation.
Can I look up records for a subdomain?
Yes — paste the full subdomain (e.g. blog.example.com) and the resolver will return records for that name. If only the parent has records, the subdomain lookup will look empty.
How fresh are the results?
We don't cache. Every lookup hits Cloudflare directly so the result reflects the resolver's current view, which itself respects the record's TTL. Very recent DNS changes can still take time to propagate across all resolvers — use the DNS Propagation Checker if you need a multi-resolver view.
Last reviewed