Ask an exact question
A name and record type form the question. An A lookup does not inspect mail or IPv6.
Direct answer: A DNS lookup returns the selected record types visible through this resolver, together with response errors, TTL context and the exact time of observation.
The server sends the normalized domain and requested record types through its configured recursive DNS resolver. Result responses are private, uncached and excluded from search indexing. Do not enter passwords or secrets. Read the lookup privacy policy.
DNS lookup shows the records a recursive resolver can observe for a specific name and record type. Use it to trace addressing, mail, delegation and policy data while keeping cached answers, authoritative data and registration evidence conceptually separate.
For the meaning and limits of each returned record family, use the DNS records reference.
When several record families must be reviewed together, continue with the multi-record DNS report rather than inferring service health from one answer.
A name and record type form the question. An A lookup does not inspect mail or IPv6.
NXDOMAIN means the name does not exist in that DNS view; NoData means it exists without that record type.
TTL is remaining cache lifetime or authoritative policy, not a guaranteed worldwide propagation timer.
| Signal | What it can establish | What it does not prove |
|---|---|---|
| A / AAAA | Published IPv4 or IPv6 destinations. | The origin server when a CDN or proxy is used. |
| MX | Mail exchangers; lower preference values are tried first. | Proof that every mailbox works. |
| NS / SOA | Delegation and zone authority data. | Registration ownership. |
| TXT / CAA | General text policy data and permitted certificate issuers. | A universal security verdict. |
Treat IPv4 and IPv6 as separate paths. An absent AAAA record is not an IPv4 outage; a published but unreachable IPv6 address can create failures for IPv6-capable clients. Query both, record response codes and test the relevant transport before changing DNS.
They may hold answers cached at different times, use different routing, apply local policy, or reach different authoritative servers.
It is the uneven expiry and refresh of cached data after an authoritative change, not a single network-wide event.
It proves the queried DNS view publishes a token. The relying service decides whether that token satisfies its verification process.