Who hosts this website? How to find any site's hosting provider

Hosting, DNS and the domain registrar are three different things

A website touches up to three companies. The registrar is where the domain name was bought. The DNS provider answers the question "which server is this domain on?" And the host runs the server that actually sends the pages. One company can do all three, but they're often separate: a domain bought at one registrar can use Cloudflare for DNS and point at a server anywhere.

That's why a WHOIS lookup rarely answers "who hosts this site?" WHOIS shows the registrar and registration dates, not where the server lives. Finding the host means looking at the server itself.

Signal 1: the response headers

Every web page arrives with a set of HTTP headers, and many managed hosts stamp their own on every response. Kinsta adds an x-kinsta-cache header, WP Engine identifies itself in x-powered-by, Hostinger sends platform: hostinger, Cloudways' Varnish cache sends cache-provider: CLOUDWAYS-CACHE, and WordPress.com and Pressable send Automattic's x-ac header.

Headers are the strongest signal because they pass straight through a CDN: even when Cloudflare sits in front of the site and hides the server's address, a host fingerprint header still names the company behind it. The HTTP header checker shows every header a site sends, with explanations.

Signal 2: the network that owns the IP address

Every IP address belongs to a network (an autonomous system, identified by an ASN) registered to a company. Look up the site's IP and you learn which network it sits on. When that network belongs to a hosting brand, such as Hostinger's or DreamHost's, the answer is settled.

Many hosts, though, rent capacity from cloud providers: SiteGround and Kinsta run on Google Cloud, Cloudways on DigitalOcean, AWS and others. For those, the network lookup names the infrastructure layer, and the headers or nameservers are needed to name the managed host on top of it.

Signal 3: the nameservers

Shared hosts usually give customers their own default nameservers, such as ns1.siteground.net or the dns-parking.com servers at Hostinger. A domain still using them is very likely hosted there too.

It's a hint rather than proof: a site can move to a new host but keep its old DNS, or use a DNS service that has nothing to do with its hosting. Treat nameservers as supporting evidence, not as the answer on their own.

Other clues worth knowing

A few more signals can help, as long as you know what they really show:

• Reverse DNS: the hostname attached to an IP address (its PTR record) sometimes includes the host's or data center's name.
• The Server header: values like nginx, Apache, or LiteSpeed name the web server software, not the company running it, though some software is typical of certain kinds of hosting.
• Platform fingerprints: hosted platforms such as Shopify, Wix, or Squarespace leave recognizable headers and markup, and the platform is then also the host.
• MX records: these show who handles the domain's email, which is often a different company from the web host.

Sites built on website builders and hosted platforms

For sites made with Shopify, Wix, Squarespace, Webflow, or WordPress.com, the platform is also the host: the site runs on the platform's own infrastructure, and the owner never chooses a server. These platforms usually leave clear fingerprints in headers, markup, or DNS records, such as a CNAME pointing at a platform hostname, so the platform is often the easiest thing to identify. The underlying data centers are the platform's business, and the network lookup may show a CDN or cloud provider the platform uses rather than the platform's own name.

Check it yourself from the command line

Every signal is public, so you can gather it by hand:

1. 1dig +short example.com returns the site's IP address.
2. 2whois followed by that IP address shows the network's owner, usually in an OrgName, org-name, or netname field.
3. 3curl -sI https://example.com prints the response headers, where host fingerprints appear.
4. 4dig +short NS example.com lists the nameservers.

When the host is hidden

Reverse proxies like Cloudflare replace the server's IP address with their own, so an IP lookup only finds the proxy. If no header gives the host away and the nameservers belong to the proxy too, the origin is genuinely hidden, which is exactly what the proxy is designed to do. In that case only the site owner can tell you what's behind it.

If you need to reach the host because a site is hosting phishing or malware, the proxy provider itself accepts abuse reports and can forward them to the host.

Why a hosting lookup can be incomplete

A single domain doesn't always mean a single host. Keep these cases in mind before trusting any one answer:

• Split setups: the bare domain, www, a shop subdomain, and a blog subdomain can each point to a different provider, so check the exact hostname you care about.
• Recent migrations: until DNS caches expire, some lookups still reach the old server. The DNS propagation check shows whether resolvers agree.
• Load balancers and multi-cloud setups: large sites can answer from several networks, and different lookups may return different IP addresses.
• Reseller and white-label hosting: the company the site owner pays may rent its servers from another host, so the network owner and the brand on the invoice differ.

Why people look up a website's host

The common reasons are practical: reporting abuse to the right company, taking over a client's site and needing to know where it lives, checking how a competitor or vendor is set up, or confirming that a migration really moved a site to the new server. For a migration, the hosting checker's server response time also gives a quick before-and-after comparison.