Domain & DNS

Hosting Provider

Identify the hosting or cloud provider of any site.

IP address Detect whether an IP belongs to a hyperscaler (AWS/GCP/Azure), a CDN edge, a VPS provider, or a residential ISP. Uses ASN + reverse DNS.

Try: 52.94.236.248 142.250.190.78 20.79.156.0 1.1.1.1 144.76.10.10 8.8.8.8

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?

Because they actually host most of the consumer internet. Cloudflare proxies ~20% of all websites; AWS, Azure, and GCP combined run most SaaS products. If you are checking a popular site and the answer is "Cloudflare in front of AWS", that is the modern default architecture — not a missed detection.

How can I find the real origin behind a CDN?

Often you cannot — that is the point of the CDN. Sometimes the origin leaks via: a non-proxied DNS record (try 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.

Why is the verdict "Unknown" sometimes?

When the ASN behind the IP is not in our list of known hosting providers — typically a small regional ISP, an enterprise running its own ASN, or a brand-new provider we have not added yet. In those cases we still show the ASN number and organization name from WHOIS; the missing piece is just the friendly brand label.

Does this detect managed WordPress / shared hosting platforms?

Partially. Big managed-WordPress players (WP Engine, Kinsta, Pressable) are detected by reverse-DNS and infrastructure ASNs. Generic shared hosting (Bluehost, HostGator, Hostinger) is usually identified by ASN. The smaller the host, the more likely we report only the underlying cloud (e.g. "AWS" or "Hetzner") and miss the reseller brand on top.