Skip to content
LookupOwl

Who hosts this website?

Enter a domain to see the host or CDN behind it, who runs its DNS and email, and the proof for each answer.

A domain name or a web address.

More options

Allow one request to the site (HEAD, over https) to read response headers that give away CDNs and platforms. It is only made when the DNS and network data have not already identified the host. Switch off to use DNS and network data alone.

Also look up the abuse contact of the network that serves the site (one registry lookup).

What this checker finds

A website is rarely one thing. The pages might be served by a hosting company, the traffic might pass through a CDN first, the domain's DNS might live with a third company, and email might be handled by a fourth. This page looks at all of them and says which provider is behind each part, instead of making you piece it together from separate tools.

  • The web side. Every address the site points to, the network that owns it, and whether it belongs to a CDN, a hosting platform, a hosting company or a cloud.
  • The DNS provider. Read from the nameservers of the domain.
  • The email provider. Read from the MX records.
  • The abuse contact. The address to report spam, phishing or attacks to, for the network that serves the site.

How to use it

  1. Enter a domain or a web addressA bare domain such as example.com works, and so does a full address with a path. Only the host name is used. IP addresses are not accepted here: the IP lookup answers for those.
  2. Read the verdictThe headline names the provider and says what kind it is: a CDN, a platform, a host or a cloud. A confidence label says how many independent clues agree.
  3. Check the evidenceOpen the evidence tab to see what each finding rests on, such as a CNAME to a provider's domain, an AS number, a published address range or a response header.

When the origin is hidden behind a CDN

A CDN or reverse proxy such as Cloudflare, Fastly or Akamai answers for the site. Visitors connect to the CDN, and the CDN fetches pages from the real server, the origin. That is why the address you see belongs to the CDN, and why no honest tool can tell you who runs the origin from outside. When we see a CDN, we say "behind Cloudflare" and that the origin is hidden.

We do not try to unmask it. Digging out an origin behind a CDN is a way to attack the site by going around its protection, so this page leaves it alone. If you own the site, your hosting account tells you where the origin is. If you need to report a problem with a site behind a CDN, report it to the CDN's abuse team, which can pass it on.

How the answer is worked out

ClueWhat it shows
CNAME chainA name such as example.cloudfront.net or example.netlify.app points straight at a CDN or platform.
Published address rangesSome CDNs publish the ranges they use. An address inside them is theirs.
Network owner (AS number)The organisation that announces the address. Well-known hosts and clouds are recognised.
Response headersHeaders such as cf-ray, x-amz-cf-id or x-vercel-id give away a CDN or platform. They are read only when the clues above did not already settle it, with one request to the site.
Nameservers and MX hostsThe names of the DNS and mail servers point to those providers.

Network owners and countries come from the free DB-IP Lite databases, credited as "IP geolocation by DB-IP". The provider patterns are a short list kept by hand, so a small host may show as an unrecognised network. In that case its organisation name is still shown, and it is usually the hosting company.

Questions people ask

How can I tell who hosts a website?

Look up the website's IP address and see which network owns it, then check whether the site sits behind a CDN. This page does both: it follows the DNS records, names the owner of each address and reads the DNS and mail providers. When a CDN is in front, the real host is not visible, and the page says so.

Why does it say Cloudflare when my host is somebody else?

Because Cloudflare is in front of your host. Visitors reach Cloudflare's servers, and Cloudflare forwards requests to your real server. Both the address and the headers belong to Cloudflare, so the real host cannot be seen from outside. Your hosting account or the site owner knows who it is.

Can I find the real server behind a CDN?

Not here. We deliberately do not try, because finding an origin that a CDN protects is a first step in attacking it. Site owners can always see their own origin in their hosting dashboard. If you need to reach whoever runs the site, use the abuse contact or the domain's registration data from WHOIS.

Is the host the same as the domain registrar?

No. The registrar sells the domain name and keeps it registered. The host runs the server that delivers the pages. They can be the same company, but often are not. A domain registered at one company can point to a site hosted at another and use DNS from a third.

Who do I report phishing or abuse to?

Report it to the abuse contact of the network that serves the site. The page lists the registry's abuse mailbox for that network, and the provider's own report page when it has one. If a CDN is in front of the site, report to the CDN, which can pass the report on to its customer.

How accurate is the result?

When a CNAME, a published address range or a header names a provider, it is very reliable. When the answer rests on the network owner alone, it points to the hosting company or its reseller. The confidence label shows which case you have, and the evidence tab lists every clue so you can check it yourself.

Does the checker contact the website?

Sometimes, once. If DNS and network data already identify a CDN, platform or host, nothing is sent to the site. Otherwise one HEAD request over https asks for response headers, which never include the page. You can switch the request off in More options. For a full look at the headers, use the HTTP headers checker.

Use it from AI, the API or the command line

Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is website_hosting. Please be kind to the rate limits.

curl
curl "https://lookupowl.com/api/v1/tools/website-hosting?q=www.cloudflare.com"
MCP
claude mcp add --transport http lookupowl https://lookupowl.com/mcp