Use a hostname lookup to inspect forward DNS
A hostname lookup translates a name into the records a DNS resolver returns. It helps you investigate where a website name points, whether both address families are published, and whether an alias connects the name to another hostname. Enter the exact name you want to inspect. The apex example.com and www.example.com can have different records and behave differently.
Read more
This hostname lookup sends three separate questions to the selected public resolver: one for A, one for AAAA, and one for CNAME. An A record contains an IPv4 address. An AAAA record contains an IPv6 address. A CNAME describes an alias to another name. The results remain separate because these questions are independent observations, rather than one atomic snapshot of a zone.
To start a hostname lookup, type a domain or hostname without a scheme, path, query string, or port. For example, enter www.example.com instead of a full page URL. The example button fills www.python.org without submitting it. Select Look up hostname when ready. No DNS query starts simply because you open this page or change the input.
Queries pass through our server to your selected public resolver. The name is disclosed to both, and the resolver can contact authoritative servers. An empty EDNS client subnet avoids deliberately attaching part of your address to the DNS query, but does not hide the server’s connection.
Read the hostname lookup evidence
Each hostname lookup response has its own record type, observation time, response code, and DNSSEC AD flag. A result for A can succeed while AAAA fails, or vice versa. Preserve that distinction when sharing a report. An unavailable IPv6 query cannot establish that the domain has no IPv6 record, and an address record does not prove that your browser can connect to it.
Read more
Expand Returned CNAME path in the forward lookup to see the ordered aliases that were actually present in that response. The sequence begins at your requested name. Unrelated records elsewhere in the answer cannot contribute addresses or provider hints to that path. The final name examined is shown even when the response does not establish a usable terminal address.
A Records returned forward lookup result means the requested type was established on the returned path. For a CNAME question, a valid alias itself is the requested answer. For A or AAAA, the tool looks for matching address records at the terminal name. This describes the DNS response, not a guarantee of HTTP service, TLS validity, or application availability.
No record of this type requires a successful response with suitable negative authority evidence. The name can still publish other types. Name does not exist in this response uses NXDOMAIN with appropriate authority evidence; an alias target may be the missing name. Inspect the returned path before deciding which configuration needs attention.
An Alias path only forward lookup result means some aliases were observed but the response did not establish a terminal address or the expected negative evidence. It preserves the useful path while acknowledging what is missing. A timeout, refusal, truncated message, or malformed answer instead leaves that query unavailable; none of these outcomes becomes an automatic “domain offline” conclusion.
Cache time and DNSSEC in a hostname lookup
The DNSSEC field in the forward lookup reports the resolver’s AD flag. A set flag indicates what the resolver asserted about authentication of the response data. MyIP.dog is not independently validating DNS signatures in your browser. A flag that is not set is distinct from a DNS error and does not, by itself, prove that a website is malicious or unreachable.
Understand hostname lookup limits and CDN hints
A forward lookup may reveal aliases that match a documented delivery-provider naming pattern. This tool recognizes selected CloudFront, Fastly, and Akamai suffixes and shows the exact observed target and the relevant provider documentation. These are narrow, inspectable hints. They are not a complete inventory of every CDN, hosting platform, traffic manager, or service a site uses.
Read more
When the forward lookup finds no recognized alias, it does not conclude that no CDN is involved. Flattening can return addresses without exposing the underlying alias as an ordinary CNAME answer. Direct address configurations, provider-specific designs, and services outside this tool’s signature set can also leave no recognized hint. Lack of a match is simply lack of this particular evidence.
Use a hostname lookup in an investigation
If your forward lookup returns records but a connection fails, use the port checker for an explicit public TCP test or ping test for a remote-probe observation. Each tool has a different vantage point and protocol. A successful DNS answer does not guarantee that a firewall permits the port or that an application responds correctly.