Hosting Provider
Identify the hosting or cloud provider of any site.
What does each field mean?
Field reference
ASN
See "ASN" under Whois IP. The hosting-provider detector matches the ASN against a curated list of known cloud / VPS / dedicated-server operators (AWS, Google, Azure, OVH, Hetzner, DigitalOcean…).
Organization
Free-form name from WHOIS. Often the strongest signal — "Amazon Technologies Inc." is unmistakably hosting; "Comcast Cable Communications" is unmistakably consumer ISP.
Reverse DNS
PTR pattern (<code>ec2-*.amazonaws.com</code>, <code>*.googleusercontent.com</code>, <code>static.*.hetzner.com</code>) is a strong secondary signal. Consumer ISPs typically have generic patterns like <code>1.2.3.4.adsl.example-isp.net</code>.
Matched rule
The specific signal that classified this IP. ASN-match (highest confidence), Org-name match (medium), RDNS substring match (medium-low). Multiple matches → higher overall confidence.
Confidence
High = exact ASN on the curated list; Medium = WHOIS org name match; Low = only RDNS hint. Treat low/medium as informational — confirm with additional sources for production gating.
Location
Where the IP physically sits, when the dataset knows. For cloud IPs we map ASN → regions (AWS us-east-1 = Virginia, AWS eu-central-1 = Frankfurt). For smaller hosts — geo-IP fallback.
About this tool
Hosting Provider identifies who runs the servers behind a website. We resolve the domain to its current IP addresses, look up the announcing ASN for each one, and match the ASN against a curated list of public clouds (AWS, GCP, Azure, DigitalOcean, Hetzner, OVH, Linode, Vultr, Cloudflare), CDNs (Cloudflare, Fastly, Akamai, CloudFront, Bunny), and known managed-hosting providers. The answer is the provider name with a short verdict on hosting style: dedicated, shared cloud, CDN edge, or proxied.
Because a site can use different providers for different traffic types — origin on AWS, edge on Cloudflare — we resolve A, AAAA, and MX records together and report each provider separately. The tool also flags pass-through CDNs: if Cloudflare or Akamai is in front, you see "served from CDN" prominently, with the origin's provider only if it leaks through the DNS or the SSL certificate.
When to use this tool
- Competitive research. See whether a competitor runs their own infrastructure or rents managed cloud.
- Vendor selection. Check who the popular sites in your niche trust — Cloudflare? Fastly? AWS direct?
- Abuse reporting. Find the right hosting provider to file a complaint with for a phishing or malware site.
- Migration planning. Confirm a domain has finished its DNS cutover to the new provider before retiring the old one.
Limitations
If the site is behind a CDN, the origin provider is hidden unless it leaks through SSL certificate Subject Alternative Names, a misconfigured mail server, or a separate subdomain. Some sites deliberately split —www on Cloudflare, api on the origin's direct IP — and we report both. The "provider" we identify is the BGP origin of the IP, which is reliable; the marketing brand a customer rents from (e.g. a managed WordPress host built on top of AWS) is harder to detect and may be flagged as just "AWS".
Frequently asked questions
Why does almost every site show Cloudflare or AWS?
How can I find the real origin behind a CDN?
mail. or cpanel.); the SSL certificate's SAN list mentioning a hosting-provider name; or historical DNS data showing the pre-CDN A record. Our tool reports any non-CDN providers it finds across A/AAAA/MX; manual digging is required when those all stay behind the CDN.