DNS Lookup
Resolve a domain’s DNS records (A, AAAA, MX, TXT, NS, CNAME and more) using Cloudflare’s public DNS-over-HTTPS resolver.
This guide is not yet available in your language and is shown in English.
Tool guide
What this tool does
DNS Lookup queries Cloudflare’s public DNS-over-HTTPS resolver (1.1.1.1) for a domain’s records of a chosen type, A, AAAA, MX, TXT, NS, CNAME, SOA or CAA, showing each record’s name, type, TTL and value.
DNS translates human-readable domain names into the information systems actually need, IP addresses (A/AAAA records), mail server destinations (MX records), ownership/verification strings (TXT records), and more, each stored as a distinct record type.
This tool queries Cloudflare’s public DNS-over-HTTPS resolver (1.1.1.1) directly from your browser, over an encrypted HTTPS connection rather than traditional plaintext DNS, returning the live records for whichever type you select.
How to use DNS Lookup
- Enter the Domain to look up.
- Choose the Record type (A, MX, TXT, etc.).
- Press Look up and review the results table.
- Copy all results, or check a different record type for the same domain.
Tips for better results
- A records return IPv4 addresses; AAAA records return IPv6 addresses, check both if you’re unsure which a domain uses.
- MX records include a priority number as part of their value, lower numbers are tried first by mail servers attempting delivery.
- TXT records are a general-purpose text field used for many things beyond human-readable notes, SPF/DKIM/DMARC email authentication, domain ownership verification for various services, and more.
- Results come from Cloudflare’s own resolver cache, which may occasionally differ slightly from what your own ISP’s DNS currently has cached, especially right after a DNS change.
Common use cases
- Checking a domain’s current A/AAAA records before or after a DNS change.
- Verifying MX records are correctly configured for email delivery.
- Inspecting TXT records for SPF, DKIM, DMARC or domain verification entries.
- Looking up NS records to confirm which nameservers currently serve a domain.
Common mistakes to avoid
- Checking only A records when troubleshooting email delivery; MX records (not A records) determine where mail for a domain is actually routed.
- Expecting an instant global update after changing a DNS record; propagation across every resolver worldwide can take anywhere from minutes to 48 hours depending on the previous record’s TTL.
- Forgetting that TTL (time to live) controls caching, a long TTL on an old record means resolvers may keep serving the old value for a while even after you’ve updated it.
Frequently asked questions
Which DNS resolver does this query?
Cloudflare’s public DNS-over-HTTPS resolver (1.1.1.1), queried directly over an encrypted HTTPS connection from your browser.
Why might results differ from what my own computer resolves?
Your device likely uses a different DNS resolver (often your ISP’s own) which may have different cached values, especially soon after a DNS record change, until each resolver’s cache (based on the record’s TTL) expires and re-queries.
What does TTL mean?
Time To Live, the number of seconds a resolver is allowed to cache a record before it must re-query the authoritative nameserver for a fresh value.
Can I look up any domain, including ones I don’t own?
Yes, DNS records are public information by design, anyone can query any domain’s published DNS records, the same way any DNS resolver on the internet does routinely.
Feedback & suggestions
Help us improve DNS Lookup. We read every message.