Website Hosting Checker

About Website Hosting Checker

Website Hosting Checker works out who is hosting a site by combining its IP address, the network organization that owns that address, the country and city of the server, the Server response header and the domain's nameservers. It names a likely provider, so you can tell at a glance whether a site sits on a major cloud, a shared host or behind a CDN.

How to use it

1. Enter the domain, such as example.com, in the Domain box. A leading www. is stripped.
2. Press Check Hosting. Our server resolves the address and nameservers and sends a HEAD request over HTTPS, falling back to HTTP.
3. Read the Provider line in the Hosting Info card, then the IP Address, ISP / Org, Country and City.
4. Check the Server row for the raw header, and the Nameservers table for the DNS provider.

When to use it

• Finding the host of a competitor or supplier site before you contact their support.
• Confirming that a domain moved to a new host after a migration.
• Telling whether a site is behind Cloudflare or another proxy rather than served directly.
• Gathering evidence of the hosting company for a takedown or abuse report.

Questions about Website Hosting Checker

How is the provider name chosen?

The organization name, the Server header and the nameserver hosts are matched against a built-in list that includes Cloudflare, Amazon Web Services, Google Cloud, Azure, DigitalOcean, Hetzner, Vercel, Netlify and shared hosts. If nothing matches, it shows the network organization instead.

Why do I see a CDN instead of the real host?

The address that DNS returns belongs to whatever fronts the site. When a proxy or CDN sits in front, its address and organization are reported, and the origin server behind it stays hidden.

Where does the location come from?

It is a geolocation lookup on the first IPv4 address found. Like all geolocation it is approximate, and anycast networks can show a location far from the actual machine.

What is sent to your server?

The domain. Our server runs the DNS queries, the web request and a geolocation lookup on your behalf, so nothing is done inside your browser.

Why is this checked less often than other tools?

One press triggers several lookups, so it is capped at 10 per minute. The web request has an overall 8 second budget shared between the HTTPS attempt and the HTTP fallback.

Related tools

• HTTP/2 CheckerCheck if a website supports HTTP/2
• Brotli CheckerCheck if a website supports Brotli compression
• IP LookupLook up information about an IP address
• DNS LookupLook up DNS records for a domain
• WHOIS LookupLook up WHOIS information for a domain
• PingPing a domain or IP address