Observe supported DNS types through this server's existing resolver. ALL is not exhaustive; CAA depends on the PHP runtime and returns HTTP 503 when unavailable.
Method, limits and data
DNS service owners such as _sip._tcp.example.com can contain underscores. TTL is a cache interval, not a freshness timestamp or DNSSEC proof. An empty record set is distinct from a failed query. ALL is a bounded observation for the exact owner, not discovery of every record. Support depends on the running PHP; an unavailable CAA lookup for a DNS name returns HTTP 503. Answers may differ from another machine's resolver. Bare IP addresses use PTR. Examples and reference text are illustrative, not current measurements or guarantees of availability, precision or logging practices.
The site uses its existing resolver. Ten inputs are kept in local history; clear history removes them. JSON copy/download includes the returned record data.
How to use
- Enter the exact owner or IP and select a type.
- Read grouped values and TTLs; copy or download JSON and clear history when needed.
203.0.113.10 becomes 10.113.0.203.in-addr.arpa for PTR. TTL 0 and an empty TXT value remain meaningful data.
Why are there zero records?
The selected type may have no answer for that exact owner. A resolver error or timeout must not be presented as a successful empty set.
Invalid or empty input clears the previous answer. A timeout or refusal is a failed observation, not a zero measurement or proof of absence. Changing input discards late answers; retry only when ready.
Reference texts, snapshot 27 October 2026; not a live service check.
DNS Lookup
Observe supported DNS types through this server's existing resolver. ALL is not exhaustive; CAA depends on the PHP runtime and returns HTTP 503 when unavailable.
DNS records for
Popular domains to try
Copied
Copy failed. Select the result and copy it manually.
About DNS Lookup
Observe supported DNS types through this server's existing resolver. ALL is not exhaustive; CAA depends on the PHP runtime and returns HTTP 503 when unavailable.
DNS service owners such as _sip._tcp.example.com can contain underscores. TTL is a cache interval, not a freshness timestamp or DNSSEC proof. An empty record set is distinct from a failed query. ALL is a bounded observation for the exact owner, not discovery of every record. Support depends on the running PHP; an unavailable CAA lookup for a DNS name returns HTTP 503. Answers may differ from another machine's resolver. Bare IP addresses use PTR. Examples and reference text are illustrative, not current measurements or guarantees of availability, precision or logging practices.
The site uses its existing resolver. Ten inputs are kept in local history; clear history removes them. JSON copy/download includes the returned record data.
203.0.113.10 becomes 10.113.0.203.in-addr.arpa for PTR. TTL 0 and an empty TXT value remain meaningful data.
Use Cases
How to use
Enter the exact owner or IP and select a type.
Read grouped values and TTLs; copy or download JSON and clear history when needed.
Press Lookup. The button shows the loading state while the query runs and the answer appears grouped by record type.
Read each group: the value on the left, the priority for MX rows, and the TTL in seconds on the right of every record.
Press Copy to put the full JSON answer on your clipboard, or Export to save it as a .json file named after the domain.
Use the Recent buttons under the search box to re-run any of your last ten lookups without retyping the name.
Pro Tips
- Query the exact owner and supported type through this server’s existing resolver. ALL is a bounded observation, not a zone inventory. CAA can be unavailable with HTTP 503; another resolver may return different data.
- PTR is the one type that needs an IP address, not a domain; the hint under the search box says so as soon as you pick it. Enter 8.8.8.8 rather than google.com.
- Query the exact owner and supported type through this server’s existing resolver. ALL is a bounded observation, not a zone inventory. CAA can be unavailable with HTTP 503; another resolver may return different data.
- The TTL column is in seconds. A 300 means five minutes, 86400 means a day — useful for judging how long a pending change will take to spread.
- Export writes the answer to domain-dns.json exactly as received, so you can diff two exports taken before and after a migration instead of comparing screenshots.
Troubleshooting
The result panel says no records were found even though the site works.
You asked for a type this zone does not publish. A domain with no mail, for example, has no MX record, and many have no SRV or CAA. Switch the type to ALL and press Lookup again to see everything the zone actually answers for.
PTR returns nothing for a domain name.
PTR is reverse DNS: it maps an IP address back to a name, so it has to be queried with the address. Put 8.8.8.8 in the box instead of the domain. The hint below the search field appears as soon as PTR is selected for exactly this reason.
The addresses shown do not match what my computer resolves.
The lookup is performed by this site's server, so you are seeing the public answer, while your machine may still be holding a cached one or using an internal resolver. Wait for the TTL shown here to elapse, or flush your own DNS cache, before assuming the zone is wrong.
Frequently Asked Questions
A DNS lookup gives one observation for an exact owner and selected supported type through this server’s existing resolver. The returned groups and TTLs describe that answer; no set of groups is guaranteed for every name.
This server asks its existing resolver, which can answer from cache or query DNS upstream. The page does not select a named public resolver or establish that every authoritative server was queried.
On Windows use nslookup example.com or nslookup -type=MX example.com; on macOS or Linux use dig example.com MX or host -t MX example.com. Answers may differ from this server’s existing resolver because of caches, query time, configuration or location; identical answers are not guaranteed.
A reverse lookup starts from an IP address and asks which hostname the address owner published for it. That is the PTR record type in the dropdown. Because it takes an address, enter something like 8.8.8.8 instead of a domain name; a hint below the search box reminds you as soon as PTR is selected.
The selectable names are ALL, A, AAAA, CNAME, MX, NS, TXT, SOA, SRV, CAA and PTR. Actual support depends on PHP: CAA for a DNS name returns HTTP 503 when unavailable in the running PHP runtime. There is no alternate resolver fallback. A bare IP uses PTR after a valid type is selected.
A lookup error or timeout is a failed observation, not proof that a name or type is absent. A successful empty answer is different. ALL may return other groups for that owner, but it cannot establish that the whole zone is healthy or that another type is unpublished.
It is how long a resolver takes to walk the hierarchy and return an answer, and it is dominated by caching. A record already cached is answered in a millisecond or two; a cold lookup has to reach the authoritative servers. The TTL each record carries here is the number of seconds resolvers are allowed to keep it cached.
Select ALL for the runtime’s bounded observation of that exact owner. The result is not exhaustive: it does not enumerate every name or every record in a zone. Returned types depend on runtime support and the resolver’s answer. Copy and export preserve only the records actually returned.
Records do not expire on their own; they stay until the zone owner changes or deletes them. What expires is the cached copy, after the TTL in seconds shown next to each record. The SOA record also carries refresh, retry and expire timers, which govern how secondary name servers keep their copy of the zone in step.
Ordinary DNS commonly uses port 53 over UDP or TCP, as described in RFC 1035. DNS over TLS and DNS over HTTPS use other transports. This page does not let you choose those transports; a transport change does not guarantee the same answer as this server’s resolver.
The selected type may have no answer for that exact owner. A resolver error or timeout must not be presented as a successful empty set.