DNS Lookup
Query DNS records for any domain using Cloudflare's DNS-over-HTTPS.
What this DNS lookup tool does
Every domain name on the internet relies on the Domain Name System (DNS) to map human-readable names like example.com to the addresses and configuration records that computers actually use. This tool lets you query those records directly from your browser, so you can see exactly what a domain is publishing without installing command-line utilities such as dig or nslookup.
It is built for developers, system administrators, website owners, and anyone troubleshooting email or hosting problems. Queries are sent over Cloudflare's DNS-over-HTTPS endpoint, which means the lookup is encrypted in transit and resolved by one of the most widely used public resolvers. You type a domain, pick a record type, and the matching records are returned in a sortable table showing the name, type, time-to-live (TTL), and data value.
How to use it
Enter a domain name in the input box (you can paste a full URL with http:// and it will be stripped automatically). Choose the record type you want from the dropdown or the quick-select buttons, then press Lookup or hit Enter. The supported record types are A, AAAA, MX, TXT, CNAME, NS, SOA, PTR, and SRV.
Use A and AAAA records to find the IPv4 and IPv6 addresses a domain points to. MX records reveal which mail servers handle email for the domain, which is useful when diagnosing delivery issues. TXT records often hold SPF, DKIM, and domain-verification strings. NS records list the authoritative name servers, and CNAME records show aliases that point one name at another.
Understanding TTL and propagation
The TTL value shown for each record is the number of seconds a resolver is allowed to cache that answer before checking again. A low TTL (for example 300 seconds) means changes propagate quickly, while a high TTL can keep old data cached for hours. If you have just updated a record and still see the old value, the result you are looking at may be a cached copy somewhere along the chain rather than an error on your part.
Because this tool reads live data from Cloudflare's resolver, the answers reflect what that resolver currently sees, which can differ briefly from other resolvers around the world during a change. Re-running the query after the TTL expires is the simplest way to confirm that an update has fully taken effect.