Hostname lookup

Resolve a hostname to IPv4, IPv6 and CNAME records. Inspect each DNS response and source-linked CDN hints.

Remote DNS query, separate from your device’s DNS path.

A, AAAA and CNAME are queried through the selected resolver from our server. This does not test your device’s DNS path.

Example report

Illustrative data. Run a lookup for live results.

Address records observed

Example report

The A, AAAA and CNAME rows retain their own response codes, alias chains and evidence. Missing address records do not prove a website is offline, and one successful family cannot replace a failed query.

Next step: Read the relevant family and alias chain, then compare the fixed resolver’s observation with the resolver used by your application.

www.example.org

A (IPv4)

  • 192.0.2.10
TTL
300 s
DNS response code
NOERROR

AAAA (IPv6)

  • 2001:db8::10
TTL
300 s
DNS response code
NOERROR

Returned CNAME path

  1. www.example.orgexample.org

CDN hostname hints

No recognized CDN alias was observed in the usable responses. This does not establish that the hostname has no CDN.

Matches use documented CloudFront, Fastly and Akamai CNAME suffixes only. A match does not prove active delivery or reveal the origin. DNS flattening and other providers may leave no recognized hint.

About this result

These are three separate DNS observations. Answers may differ from your local resolver and can change over time. DNS records do not establish reachability, server location or ownership.

Observed at
ResolverCloudflare 1.1.1.1
Observed alias target

A · Records returned

Last name examined
example.org
Resolver DNSSEC AD flag
Not set by resolver
Observed at
2026-01-15T14:23:00.000Z

AAAA · Records returned

Last name examined
example.org
Resolver DNSSEC AD flag
Not set by resolver
Observed at
2026-01-15T14:23:00.000Z

CNAME · Records returned

Last name examined
example.org
Resolver DNSSEC AD flag
Not set by resolver
Observed at
2026-01-15T14:23:00.000Z

Starts only when submitted. Three DNS queries per run; six lookups per minute per connection, with shared service limits.

Three forward DNS questions

  1. Exact hostname

    Normalize the name without silently removing labels.

  2. Our server

    Ask the selected public resolver for A, AAAA and CNAME.

  3. Returned alias paths

    Validate the aliases and records present in each response.

  4. Separate conclusions

    Show addresses, negative evidence, partial paths and missing checks.

A, AAAA and CNAME remain independent observations. This is not a worldwide propagation test.
On this page

Learn more about Hostname lookup

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.

Hostname lookup questions

Is hostname lookup the same as reverse DNS?

No. A hostname lookup starts with a name and inspects forward records. Reverse DNS lookup starts with an address and asks for PTR records in the reverse namespace. These records are maintained separately. A PTR can be absent or point to a name that differs from a website’s name, without contradicting its forward DNS records.

Reverse DNS lookup

Why does hostname lookup return several addresses?

A hostname lookup can receive several addresses because the name publishes an address set or uses delivery infrastructure with multiple destinations. The list is the resolver’s answer at that time, not an exhaustive scan of every possible serving endpoint. This tool displays the returned set and does not choose one to claim it is the site’s unique or permanent server.

Can hostname lookup show a private address?

Yes. Public DNS can return a private or special-use address, and the hostname lookup labels its range instead of contacting it. The result does not prove that the service is accessible from the public internet. It might relate to an internal design, a mistake, or another configuration context. Investigate the domain’s intended use before changing it.

What does stopping a hostname lookup do?

Stopping the hostname lookup aborts waiting and invalidates pending results in this tab. A DNS question already received by the service or resolver may have started processing. Clear also resets the input. Leaving through site navigation or a page lifecycle event invalidates the pending response so that an old result cannot reappear after you have cleared it.

How can I share a hostname lookup responsibly?

Use Copy report to export the hostname lookup evidence as JSON, including individual questions, returned records, times, interpretation, and provider hints. Review the name and records before sharing. Even DNS information can disclose something about a business or a system under investigation. The report should travel with its stated resolver and limitations rather than become an unexplained screenshot of one address.

Where is the hostname lookup method documented?

The hostname lookup queries your selected public resolver through a DNS-over-HTTPS JSON interface. Background references include RFC 1034 for DNS concepts and RFC 2308 for negative caching. Provider hints link to CloudFront, Fastly, and Akamai; Cloudflare’s flattening explanation illustrates why aliases may be hidden. Sources were checked on September 28, 2026.

Google Public DNS JSON interface

RFC 1034

RFC 2308

CloudFront

Fastly

Akamai

Cloudflare’s flattening explanation

Does a hostname query inspect an HTTPS path?

No. DNS owner names do not include URL schemes, paths or ports. Query the relevant hostname first. If the question concerns a redirect or HTTP response, use a web-response tool for that separate layer.

Can the apex domain and www have different results?

Yes. They are different DNS names and can have different A, AAAA or alias records. Query the exact name used by the application rather than assuming one result describes every subdomain of the registration.