Resolve the hostname
DNS A, AAAA and CNAME answers show the public destinations and aliases currently visible to this resolver.
Direct answer: A hosting lookup resolves a website's public addresses and CNAMEs, maps those addresses to visible network organizations, and records one HTTP response to identify the serving layer that can actually be observed.
The server resolves the public hostname, sends its visible addresses to the named ASN evidence provider, and makes one bounded HTTP request to the submitted public URL. Result responses are private, uncached and excluded from search indexing. Do not enter passwords or secrets. Read the lookup privacy policy.
What this hosting lookup tells you
No single internet protocol names a website's hosting company. This lookup combines DNS, address-to-ASN network evidence and one HTTP observation to identify the public serving layer while stating when a CDN, reverse proxy or shared platform prevents discovery of the origin server.
- Which public IPv4 and IPv6 addresses currently serve the hostname
- Which CNAME and network organizations are visible from this probe
- Whether the result identifies a direct host, a CDN or only an intermediary layer
The visible address may belong to a CDN or reverse proxy; the DNS records reference explains what A, AAAA and CNAME evidence can establish.
For the registered allocation behind a returned address, continue with the IP WHOIS lookup and keep the exact IP and observation time.
How the evidence is collected
Map the addresses
Each public address is mapped to reported ASN, organization, ISP and network-domain context; this identifies the visible routing layer, not an account holder.
Observe HTTP
One bounded request records the first response status, redirect and Server header without following the redirect or executing page code.
State the limit
If the address belongs to a CDN, proxy or shared cloud edge, the tool reports that layer and leaves the hidden origin unidentified.
Read the fields without overclaiming
| Signal | What it can establish | What it does not prove |
|---|---|---|
| A / AAAA | The public addresses returned for the requested hostname. | A hidden origin behind a proxy or CDN. |
| CNAME | An alias target published in DNS when one is visible. | The legal company operating every service behind that name. |
| ASN / organization | The network reported as routing or serving the visible address. | The website owner, hosting-account customer or origin operator. |
| Server header | A label voluntarily returned by the first HTTP response. | A verified product, company or complete software inventory. |
The addresses map to Cloudflare and no origin is exposed
Report Cloudflare as the visible CDN or reverse-proxy layer, not as proof of the origin host or website owner. Preserve the resolved addresses and time, then use historical or provider-authorized evidence if the hidden origin is genuinely required.
Common mistakes
- Calling a CDN edge the origin server
- Treating an ASN organization as the website owner
- Ignoring CNAME chains and shared addresses
- Claiming the Server header independently verifies a provider
Hosting Lookup FAQ
Which protocol reveals the web host?
There is no single hosting-discovery protocol. DNS finds destinations, RDAP describes IP registration, ASN data describes routing, and HTTP or TLS shows the service that answered.
Why can the origin remain hidden?
CDNs and reverse proxies intentionally publish their own addresses and relay traffic to an origin that is not exposed in public DNS.
Does IP WHOIS name the hosting customer?
Usually not. It commonly names a provider, allocation or network range and may not disclose the customer using a shared address.