DNS Lookup

Look up DNS records for a domain. Queries are sent to your chosen DNS-over-HTTPS resolver — real results only, never fabricated.

Input

Queries are sent to your chosen DNS-over-HTTPS resolver to perform the lookup — no data is stored.

Results

Raw Response

    

Overview

The DNS Lookup queries the Domain Name System for a hostname and shows the records it returns: addresses (A, AAAA), aliases (CNAME), mail routing (MX), delegation (NS), zone parameters (SOA), free-form text (TXT, used for SPF, DKIM, DMARC and domain verification), service locations (SRV), certificate-authority policy (CAA), and the DNSSEC records DS and DNSKEY. By default it queries every one of these types at once and groups the results.

Use it to confirm that a DNS change has taken effect, to see where a domain's mail and name servers point, to compare what different public resolvers return, or to start troubleshooting a name that will not resolve.

How It Works

Browsers cannot send arbitrary DNS queries, so this site's server function sends your query to a public DNS-over-HTTPS (DoH) resolver on your behalf. You can choose Cloudflare (1.1.1.1), Google (8.8.8.8), or Quad9 (9.9.9.9). These are recursive resolvers: they look the name up, cache the answer, and return it, so what you see is what that resolver currently believes, including cached data counting down its TTL.

DNS has no single "give me everything" query (the old ANY type is discouraged by RFC 8482). The ALL option therefore runs one query per record type, in parallel, and combines the results. A type with no records is a normal outcome, not an error: most domains have no SRV, DS or DNSKEY records, for instance. If a query fails outright (as opposed to returning nothing), the page reports that separately.

The raw JSON returned by the resolver is available under Raw Response for anyone who wants to inspect the exact answer.

How to Use the DNS Lookup

  1. Enter a domain name such as example.com. Underscore names like _dmarc.example.com are accepted for looking up TXT records at those labels.
  2. Leave the record type on ALL for an overview, or choose one type for a focused answer.
  3. Choose a DNS server (Cloudflare is the default) and press Calculate.
  4. Read the grouped tables. Use Raw Response if you need the unprocessed answer, and Copy Results to paste a summary into a ticket.

Worked Example

What does a small domain publish?

You are checking where mail for example.com goes and whether the site has an IPv6 address. The sample below uses reserved documentation addresses.

Input

Domain: example.com
Record type: ALL
DNS server: Cloudflare

Illustrative output

A
Name           TTL   Value
example.com.   300   203.0.113.10

MX
Name           TTL   Value
example.com.   300   10 mail1.example.com.
example.com.   300   20 mail2.example.com.

NS
example.com.   3600  ns1.example.net.
example.com.   3600  ns2.example.net.

TXT
example.com.   300   "v=spf1 mx -all"

No records found for: AAAA, CNAME, PTR, SRV, CAA, DS, DNSKEY.

This output is an illustrative sample to show the layout and meaning of each field. Real results depend on the target and on when you run the check.

The A record maps the name to one IPv4 address. There is no AAAA result, so the site is reachable over IPv4 only. The MX records list two mail servers; the number before each hostname is its preference, and senders try the lowest number first, falling back to the next. The NS records name the authoritative servers for the zone.

The TXT record is an SPF policy (see the SPF, DKIM and DMARC guide). The empty DS and DNSKEY results show DNSSEC is not enabled for this domain. The TTL column is how many seconds this resolver may keep the answer cached.

Interpreting Results

A / AAAA
The IPv4 (A) and IPv6 (AAAA) addresses the name resolves to. Several records mean traffic may be spread across several servers.
CNAME
An alias to another name. A name with a CNAME cannot have other record types, and a CNAME is not allowed at a zone apex.
MX
Mail exchangers with a preference number; lower is tried first. An MX target must be a hostname with an address record, not an IP address.
NS / SOA
NS names the zone's authoritative servers. SOA carries the primary server, the administrator's mailbox, the serial number, timers, and the negative-caching TTL.
TXT
Arbitrary text. In practice: SPF (v=spf1 ...), site-verification tokens, and, at _dmarc. and selector._domainkey. labels, DMARC and DKIM.
SRV / CAA
SRV gives a service's host and port (used by SIP, XMPP, Microsoft services, and others). CAA lists which certificate authorities may issue certificates for the domain.
DS / DNSKEY
DNSSEC records. Their presence indicates DNSSEC is deployed; it does not by itself prove the chain of trust validates.
TTL
Seconds a resolver may cache the record. After a change, old answers can persist for up to the old TTL.

Troubleshooting

"No records found" for a name you expect to exist.
Check spelling and that you queried the right label (www.example.com and example.com are different names). If the name genuinely has no record of that type you get this result. Also try another DNS server; a very recent change may not have reached every resolver's cache.
Cloudflare, Google and Quad9 show different answers.
Usually caching during a change: each resolver holds the old record until its TTL expires. Wait for the old TTL to elapse, or lower the TTL before planned changes. Persistent differences can indicate geo-based or load-balanced DNS.
The lookup failed instead of returning an empty result.
A resolver error (such as SERVFAIL) is different from "no records". Common causes are DNSSEC validation failures, broken delegation (the NS records point to servers that do not answer), or a temporary resolver outage. Retry, switch resolver, and compare with the DNS Security Checker.
"Please provide a valid domain name."
Enter a hostname with a dot and a valid top-level domain, up to 253 characters. IP addresses belong in the Reverse DNS tool.

Limitations and Accuracy

  • Results come from a recursive public resolver, not directly from your domain's authoritative servers, so they may be cached and may differ from what your own network's resolver returns.
  • The tool does not distinguish "the name does not exist" (NXDOMAIN) from "the name exists but has no record of this type" (NODATA); both appear as no records.
  • Queries are made by this site's server and sent to the DNS-over-HTTPS provider you select. See the Data Handling section and the Privacy Policy.
  • It cannot show records inside private or split-horizon DNS views.
  • Requests are rate limited, and internal or private hostnames are refused.

Data Handling

Uses server-side requests. The domain name, the record type(s), and your chosen resolver are sent to this site's server function, which queries the resolver.
Sent to: Cloudflare (cloudflare-dns.com), Google (dns.google), or Quad9 (dns.quad9.net), depending on your choice.

Inputs travel as URL query parameters, so avoid entering confidential internal hostnames or personal data. See the Privacy Policy for how requests are handled.

Frequently Asked Questions

Why use ALL instead of ANY?

ANY is unreliable and discouraged by RFC 8482, and many resolvers return minimal data for it. ALL sends separate, ordinary queries for each type.

How long until my DNS change is visible?

As long as the old record's TTL. Resolvers that cached the old answer keep serving it until the TTL expires; resolvers that have not cached it see the new value immediately.

Why would I query the PTR type here?

Reverse lookups use the special in-addr.arpa and ip6.arpa names, so PTR on an ordinary hostname normally returns nothing. For IP addresses use the Reverse DNS tool.

Where can I learn the troubleshooting workflow?

The DNS troubleshooting guide walks through the decision tree step by step.