Use DNS lookup to answer a specific question
A DNS lookup asks a resolver for the records published for a name. Enter example.com, choose a record type and select Look up records. Use a domain or subdomain without a scheme, path or port. The example button fills the field without starting a query, so you can inspect the input first. Internationalized names are converted to their ASCII representation, and a trailing dot is accepted.
Read more
SOA describes zone information, CAA certificate issuance policy and SRV service destinations. DS and DNSKEY expose DNSSEC records. For PTR, enter a public address; the tool constructs its reverse name. The table below explains common record types.
All common records checks eleven supported domain record types, with at most three requests running together. It is a set of focused questions, not a zone transfer or an inventory of every subdomain. Each type retains its own response code and any unavailable outcome. A failed MX query remains visible even when the A query succeeds.
Select Google Public DNS or Cloudflare to inspect that resolver's view. Both requests travel through our server over HTTPS. Switching the dropdown does not change your computer's DNS settings. Avoid entering confidential internal names: the selected resolver receives your query. Google requests use an empty EDNS client subnet; the tool does not forward your visitor address as a subnet parameter.
Understand the DNS record checker result
The summary separates records returned from execution and coverage. A completed query can return no answer records. Partial evidence means at least one query was unavailable, or a response or display limit prevented a complete record view. A provider timeout cannot establish that a name is absent. Stopping cancels the current wait; requests already delivered cannot be recalled.
Read more
Each answer identifies its owner name, type, TTL in seconds and data. Several addresses can legitimately serve one name. An A query may also return a CNAME followed by the destination's addresses. The summary counts distinct answer records across the returned queries, while the details retain their individual context. Authority records, when supplied, are available separately.
NOERROR reports a completed DNS operation without the indicated protocol error. It can still have an empty answer for the requested type. NXDOMAIN reports that the queried name does not exist in that resolver's current view. SERVFAIL describes a resolver failure, which can involve upstream problems or DNSSEC validation. Keep the exact code when asking your DNS provider for help.
TTL is a caching lifetime, not a website uptime measurement. A cached response can show less time remaining than the authoritative record's original TTL. A decreasing value alone does not establish that someone changed your configuration. Compare the record values, resolver and observation time together.
The DNSSEC authenticated-data flag says whether the resolver marked the response authenticated. A missing flag does not prove malicious behavior or even establish that the zone should be signed. An authenticated answer verifies neither the website's content nor its business. Read this as DNS evidence rather than a general security badge.
Troubleshoot changes and recognize the limits
Start with the exact owner name and record type. example.com and www.example.com are separate names; checking one does not automatically describe the other. For email, inspect the relevant MX or TXT name rather than assuming an address answer confirms the whole mail configuration. A TXT record containing a policy is not a complete SPF, DKIM or DMARC validation.
Read more
Next, confirm that you edited the authoritative zone actually delegated for the domain. Updating an unused provider account leaves public answers unchanged. Compare the NS records and your provider's configuration before making another change. If the expected name returns NXDOMAIN, verify its spelling and delegation, then compare a second resolver.
After a change, allow previously cached answers to expire. Lowering the TTL now does not shorten timers on answers already cached elsewhere. Different recursive resolvers can legitimately show different values during that interval. Geographic traffic selection and temporarily inconsistent authoritative servers can also produce differences. This page observes named resolver responses and cannot certify worldwide propagation.
If local browsing still fails, check your operating system's resolver, hosts-file overrides, browser secure DNS settings and any private network rules. This remote query cannot inspect those components. A corporate resolver might intentionally provide an internal answer that a public resolver does not know. A successful address lookup also says nothing about whether the destination accepts an HTTP connection.
Use Copy report to retain the submitted name, source, observation time, response codes and returned records. Review its contents before sharing confidential domain or service names. The result is not published as a private indexable page, and changing the form clears the previous display so it cannot appear to describe a new input.
Method, sources and the next tool
The interfaces and response flags are documented by Google Public DNS and Cloudflare's DNS JSON API. DNS-over-HTTPS JSON is provider-specific rather than a formal common JSON standard. This tool validates returned fields and limits displayed records; unavailable or truncated data remains explicit.
Use hostname lookup for a combined forward-address and alias view, reverse DNS lookup for PTR records, or domain WHOIS lookup for registration evidence. This is not a DNS leak test: detecting resolver exposure requires observing unique names generated by your browser's own test session. Querying a known public resolver through our server answers a different question.
Common DNS record types
| Type | What it shows | Example |
|---|---|---|
| A | IPv4 destination for a name. | example.com → 192.0.2.10 |
| AAAA | IPv6 destination for a name. | example.com → 2001:db8::1 |
| CNAME | Alias pointing to another name. | www.example.com → example.com |
| MX | Mail server and delivery priority. | example.com → 10 mail.example.com |
| NS | Authoritative name servers for a zone. | example.com → ns1.example.com |
| TXT | Text data used for verification and published policies. | example.com → "v=spf1 …" |
Teaching examples only. The lookup report above shows the records actually returned by your selected resolver.