DNS Lookup
Look up DNS records for any domain — A, AAAA, CNAME, MX, TXT, NS, SOA — via Cloudflare's DNS-over-HTTPS.
Look up DNS records online — A, AAAA, CNAME, MX, TXT, NS, SOA and more — for any domain, with TTLs. Uses DNS-over-HTTPS, so results are fast and reliable from anywhere.
How to look up DNS records
Enter a domain name and select a record type such as A, AAAA, CNAME, MX, TXT, NS, or SOA. The lookup returns the record value and TTL from a public DNS-over-HTTPS resolver.
Use A and AAAA records to check IP addresses, MX records to inspect mail routing, TXT records for verification policies, and NS records to identify authoritative nameservers.
Full guide: How to check DNS records (and what each one means)
Lookup: DNS-over-HTTPS via Cloudflare and Google public resolvers.
Example
Look up example.com with type MX and you get a single record, 0 .: a "null MX" (RFC 7505), which says the domain accepts no email. Its TXT record v=spf1 -all says it sends none either. Both were checked at the time of writing. What each record type means: DNS guide.
How to use the DNS Lookup
- Enter a domain name.
- Pick the record type (or All).
- Read the records with their TTL values.
Frequently asked questions
How do I check DNS records for a domain?
Type the domain above and choose the record type — results come straight from authoritative DNS.
What is an A record?
The A record maps a domain to an IPv4 address. AAAA does the same for IPv6.
What is an MX record?
It lists the mail servers that receive email for the domain, with priorities.
What is DNS-over-HTTPS?
The lookup is encrypted and sent to a public resolver, so it works from anywhere and cannot be snooped.
Fun facts about DNS Lookup
- DNS was introduced in 1983 (RFC 882 and 883) to replace HOSTS.TXT, a single file listing every host on the ARPANET that computers downloaded and kept up to date.
- The DNS root zone delegates more than 1,400 top-level domains, from .com and .in to newer ones like .dev and .app.
- DNS caching means that most DNS queries are answered by intermediate resolvers, not the authoritative server — this reduces load and speeds up responses.
- A DNS amplification attack can turn a small query into a large response — attackers use this to overwhelm targets with traffic (DDoS).
- The TTL (Time to Live) value in a DNS record tells resolvers how long to cache the answer — lower TTLs mean faster propagation of changes but more queries.