DNS Lookup

Enter the exact name you need to inspect. A website hostname and its parent domain can have different records. For a DNS lookup of a service-specific name, preserve the full label rather than removing a subdomain because it looks optional. Do not include a browser URL path or port.

Select the record type that answers the question. A and AAAA concern address records; MX concerns mail routing; TXT contains text records used for several purposes. Choosing an unrelated type can legitimately return no answer even when other records exist for the same name.

Run the lookup and inspect the response status before the answers. A successful resolver response with no answers differs from NXDOMAIN, which indicates the queried name was not found. A timeout reaching the provider is a separate failure and is not a DNS answer about your target.

Compare record values and TTLs with the configuration you intended to publish. TTL is expressed in seconds. A recursive resolver may return a cached record with a remaining lifetime, so two observations can show different TTLs without the record value having changed. Preserve the query name, type and timestamp when comparing.

DNS maps names to typed records, and a recursive resolver can cache answers. This DNS lookup uses Google’s DNS-over-HTTPS JSON interface and requests that client-subnet information not be forwarded through the EDNS client-subnet parameter. Google still sees the browser request address. The authenticated-data flag is displayed as reported by the resolver; a missing flag is not a complete security audit of the domain. Similarly, an A record only identifies an address returned for the name. It does not prove that port 443 accepts connections or that an application returns the expected content.

A single DNS lookup cannot demonstrate global propagation. Different recursive resolvers may have different caches and use different authoritative paths. The multi-region DNS checker provides a small comparison sample, but even that does not cover every user or resolver.

Do not paste credentials, API tokens or private internal names into a public resolver query. The tool sends only the requested DNS name and type, but that name itself can reveal infrastructure or an internal project.

DNS changes can take time to appear in caches. Check authoritative configuration and the previously published TTL before repeatedly editing the zone. Rapid, unrecorded changes can make the sequence harder to understand.

Suppose a domain has an A record but no AAAA record. An A lookup can return an IPv4 answer while an AAAA lookup returns no answers with a successful resolver status. That is not the same as the entire domain being absent. Now imagine looking up a misspelled hostname and receiving NXDOMAIN. The name, not merely the requested address family, was reported missing in that response. Keeping query name, type and status together prevents these cases from being collapsed into the same “DNS broken” message.

Keep the question, input, observation time and source together. A bare address, percentage or status code is difficult to interpret later because it omits the connection and measurement context. When comparing two observations, note what changed between them: the target, network, VPN state, selected adapter, record type or remote origin. Change one relevant condition at a time when possible. That makes the comparison easier to explain without inventing a cause from one number.

Save only information you actually need. Network records can reveal infrastructure names and connection details, even when they do not contain a password. Remove unrelated identifiers before sharing a screenshot with another person. Never put private credentials in a domain field or publish an internal hostname as part of a public test. A copied result is a snapshot, not a promise that the same conditions still apply when someone reads it later.

Kepo is a Mac desktop-widget product for repeated checks and small workflows. A labeled troubleshooting note or a supported monitoring widget can keep the relevant context accessible while you work. The download link opens the product workflow; this article does not automatically install a configured diagnostic widget, transfer your network inputs or start a scheduled check. Confirm the actual widget’s capabilities before relying on it for ongoing observations.