DNS Lookup
The DNS Lookup tool resolves A, AAAA, CNAME, MX, TXT or NS records for any hostname using DNS-over-HTTPS against Cloudflare's 1.1.1.1 resolver. Each result shows the exact record data returned and its TTL in seconds. It's useful for checking DNS propagation after a change, verifying SPF, DKIM and DMARC TXT records, and tracing CNAME chains for CDNs and email providers.
How it works
Browsers have no built-in API for making a raw DNS query — the only network primitives available to JavaScript are HTTP requests. DNS-over-HTTPS solves that by encoding a normal DNS query inside an HTTPS request, so any client that can make an HTTPS call can also resolve DNS records, without needing direct access to port 53 or a local resolver.
When you look up a hostname, our edge proxy sends a DNS-over-HTTPS request to Cloudflare's 1.1.1.1 resolver, asking for the record type you selected — A and AAAA for IP addresses, CNAME for aliases, MX for mail servers, TXT for arbitrary text data like SPF and DKIM policies, or NS for authoritative name servers. The resolver returns a JSON response listing every matching record along with its TTL, the number of seconds a resolver is allowed to cache that answer before checking again. We display those records and TTLs exactly as returned, without modification.
Because DNS is a public, distributed system by design, this lookup doesn't reveal anything private — it queries the same records any other resolver on the internet would return. Only the hostname and record type you request are sent through our proxy to the resolver, and nothing is stored afterward.
Frequently asked questions
Why does DNS propagation take time after I change a record?
Resolvers around the world cache your old record for as long as its TTL allows, so a lower TTL before a planned change means faster propagation. Until every cache expires, some visitors will keep seeing the old value.
Why are my results different from what I see running dig or nslookup locally?
Different resolvers can return different results temporarily during propagation, or if you're behind a resolver with a stale cache. This tool always queries Cloudflare's 1.1.1.1 resolver directly, bypassing your local DNS cache entirely.
How do I verify my SPF, DKIM or DMARC records are set up correctly?
Look up the TXT records for your domain (SPF and DMARC) or your DKIM selector subdomain (DKIM) and confirm the value matches exactly what your email provider's documentation specifies, including quoting and spacing.
What does a low TTL mean and when should I use one?
A low TTL, like 60 or 300 seconds, makes resolvers re-check the record more often, which is useful right before a migration so you can roll back quickly. Once things are stable, a higher TTL reduces load and speeds up resolution for everyone.
Why does a CNAME lookup sometimes return an A record instead?
Many tools automatically follow a CNAME to its target and show the final A record for convenience. If you need to see the CNAME itself, make sure you've explicitly selected the CNAME record type rather than A.