DNS lookup
Enter a domain and select a record type to see live DNS records resolved via Cloudflare DNS-over-HTTPS.
About this tool
DNS is the layer that turns a name into an address, and almost every outage that starts with it works fine, it must be DNS ends with it being DNS. Knowing what each record type does turns guesswork into diagnosis. An A record maps a name to an IPv4 address and AAAA to IPv6. CNAME aliases one name to another and, critically, cannot coexist with other records at the same name — which is why a CNAME at the apex of a domain is invalid and why providers offer proprietary workarounds like ALIAS or ANAME. MX routes mail, with a preference number where lower wins. TXT holds arbitrary text and in practice carries SPF, DKIM, DMARC, and domain-ownership verification. NS delegates a zone, SOA carries its serial and timing parameters, and CAA restricts which certificate authorities may issue for the domain. This tool queries live records for any domain — individually or all types at once — through Cloudflare's DNS-over-HTTPS resolver, so results reflect what a public resolver sees rather than what your local network's cache holds.
- 1
Enter a domain name (e.g. example.com) in the input field.
- 2
Select the DNS record type you want to query: A, MX, TXT, NS, CNAME, etc.
- 3
Click Look Up to fetch live records from Cloudflare DNS.
- 4
Choose 'ALL' to query every supported record type at once.
Verify that your MX records are correct before switching email providers.
Check TXT records to confirm SPF, DKIM, or domain ownership verification.
Look up A and AAAA records to see where a domain currently points.
A record lookup
github.com Type: A140.82.121.4 (TTL 60s)MX record lookup
gmail.com Type: MXPriority 5: gmail-smtp-in.l.google.comTXT record for SPF
google.com Type: TXTv=spf1 include:_spf.google.com ~allA record I just added does not appear
Cause: Caching. Resolvers hold records for the duration of their TTL, and a negative answer is cached too — so a lookup performed before the record existed keeps returning nothing until that negative cache entry expires.
Fix: Wait out the TTL, which is often 3600 seconds. Lowering the TTL before making a change reduces the wait, but only if it is lowered far enough in advance for the old TTL to expire first.
Adding a CNAME breaks mail or the website
Cause: A CNAME must be the only record at its name. Adding one alongside MX or TXT records puts the zone in an invalid state, and resolvers behave inconsistently when they encounter it.
Fix: Never place a CNAME at a name that also needs MX or TXT records, and never at the domain apex. Use an A record, or your provider's ALIAS or ANAME type, at the apex instead.
Results differ from what my computer resolves
Cause: This queries Cloudflare's public resolver. Your machine may use a different resolver with a different cache, a split-horizon DNS setup that serves internal answers, or a hosts file entry that bypasses DNS entirely.
Fix: Compare against your local resolver with dig or nslookup. A difference between public and local results usually points to internal DNS or a stale local cache rather than a problem with the zone.
These answers explain common dns lookup tasks, expected input formats, and edge cases so both visitors and search engines can understand what this tool does.
What DNS record types are supported?
A, AAAA, MX, TXT, NS, CNAME, SOA, CAA, PTR, and ALL (which queries every supported type in one shot and returns only non-empty results).
Which DNS resolver is used?
Queries are resolved via Cloudflare DNS-over-HTTPS (cloudflare-dns.com). This gives fast, privacy-respecting results that reflect global DNS state rather than any one ISP's resolver cache.
Why does my record not appear?
DNS records take time to propagate after a change — typically between a few minutes and 48 hours depending on the TTL. If you just made a change, wait and check again. You can use the DNS Propagation tool to see how far your change has spread.