Public website technology intelligence — one scan, one detailed report.
Website Technology

How to Find Where a Website Is Hosted

Learn how to find where a website is hosted using DNS records, IP lookups, and HTTP headers. Identify AWS, Vercel, Netlify, Cloudflare, and more.

How to Find Where a Website Is Hosted
How to Find Where a Website Is Hosted

To find where a website is hosted, look up the DNS records for the exact hostname, then check the HTTP response headers for the page. A DNS alias pointing to a provider’s deployment domain, such as netlify.app, can give you a strong hosting clue. If you find Cloudflare IP addresses and a CF-Ray header, you’ve identified Cloudflare in the public delivery path. You may need more evidence to identify the infrastructure behind it. Netlify Docs

The exact URL matters. A company might serve its homepage through Vercel, run its customer dashboard on Azure, and deliver product images through Amazon CloudFront. If you only look up the main domain, you can miss the provider responsible for the part of the website you’re working on.

You can start with the WebBuildFinder website technology checker and then verify the result using the DNS and browser checks below. This guide covers what to look for across AWS, Google Cloud, Azure, Vercel, Netlify, and Cloudflare, with examples of what you can confidently put in a hosting audit.

Hosting vs CDN

A hosting provider supplies the environment where a website’s files or application run. That could be a shared hosting account, a cloud virtual machine, a managed application service, or a platform that deploys static sites. A content delivery network, or CDN, serves content through a distributed network of edge locations. It can respond from cache or fetch content from an upstream service, commonly called the origin. Amazon CloudFront

Some providers handle multiple roles. A site deployed to a managed platform can use that platform for builds, static file delivery, and server-side functions. Another website might run the application with one provider and use a separate CDN in front. The public response can reveal one of those relationships or several, depending on how the site is configured.

Consider a WordPress site where example.com returns Cloudflare headers. The owner wants to know where to update the PHP version. The Cloudflare result can help narrow down where public caching and traffic are handled. To find the PHP controls, you need the provider or service running WordPress. If you have access to the client’s hosting dashboard, that is the place to verify the origin.

Hosting also differs from the domain registrar and the DNS provider. The registrar handles domain registration. The DNS provider publishes records that direct traffic. A domain purchased from one company can use DNS from a second company and host its website with a third. Vercel and Netlify both document using domains managed outside their platforms. vercel.com

DNS Analysis

DNS gives you a view of where a hostname points. Start with the name people actually visit. If example.com redirects to www.example.com, look up both names and inspect the final page. If you’re auditing an account portal at app.example.com, check that hostname directly.

DNS recordWhat it revealsHow to use itAAn IPv4 addressLook up the registered network and check whether it belongs to a host, CDN, or another intermediary.AAAAAn IPv6 addressCheck the network serving requests over IPv6.CNAMEAn alias to another hostnameFollow the alias chain and look for the provider’s product or deployment domain.NSThe authoritative nameserversIdentify who handles DNS. Compare this separately with the website’s A, AAAA, and CNAME records.MXMail routing destinationsUse this for email hosting research. The website may use an entirely different provider.

You can use a browser-based DNS lookup tool or run these commands if dig is available. Replace the example hostname with the one you’re checking.

dig +short www.example.com CNAME
dig +short www.example.com A
dig +short www.example.com AAAA
dig +short example.com NS

A provider-specific CNAME is often easier to interpret than an IP address because it can point to a recognizable product. For example, a CNAME from www.example.com to a Netlify deployment hostname points you toward Netlify for that site. A lookup that returns only an IP needs more context. You can use an IP registration lookup to identify the network associated with the address. That organization might be a CDN, a cloud provider, or a network used by a managed hosting reseller. Netlify Docs

If the CNAME lookup is empty, check the other records before drawing a conclusion. A site can point directly to an A or AAAA record. DNS providers can also use CNAME flattening, where the public answer contains resolved IP addresses even though the domain is configured with an alias-like target. An empty CNAME result can therefore be normal, particularly at the root domain. Cloudflare DNS docs

HTTP Headers

DNS shows where the hostname resolves. HTTP headers show what the server or delivery network sent back for a specific request. Comparing the two helps you identify which provider served the page, particularly when the homepage redirects or loads resources from several domains.

In Chrome, open DevTools → Network, reload the page, and select the main document request under Doc. Open Headers → Response Headers and look for the Server header, provider-specific request IDs, and cache headers. Check the request URL before recording the result. A header from a tracking script, font, or image belongs to that resource. developer.chrome.com

You can also use curl to make a regular GET request and print only the headers. The example below follows redirects, so you may see multiple response blocks.

curl -sSL -D - -o /dev/null 'https://www.example.com/'

If the site redirects, record the original URL and where it lands. A domain forwarding service could handle the first response while a deployment platform serves the final page. If you’re figuring out where the homepage runs, focus on the response that actually delivers the homepage.

Generic server names such as nginx or Apache can help identify the software advertised by the response. Pinning down a hosting company usually requires provider-specific DNS or HTTP evidence. For a closer look at those server product names, see How to Identify a Website’s Web Server.

AWS

One of the easiest Amazon Web Services clues to recognize is a DNS target ending in cloudfront.net. AWS assigns that type of hostname to CloudFront distributions, which can serve content under their own domain or under a custom website domain. If the website’s primary hostname points to CloudFront, you can report that AWS CloudFront is involved in public delivery for that hostname. Amazon CloudFront

The important follow-up is to see where that clue appears. Suppose www.example.com points to a deployment platform while media.example.com points to a cloudfront.net distribution. The CloudFront evidence applies to media delivery. If the main site itself points to CloudFront, the CDN could be fetching content from an AWS service or another upstream source configured by the site owner. CloudFront supports multiple origin configurations, so the CDN hostname by itself leaves the application host open. AWS CDK Reference

IP ownership has a similar limit. An address registered to Amazon can support an AWS infrastructure finding. The site owner may pay a managed hosting company that runs on AWS. If you need to know whom to contact for a migration, verify the actual hosting account or deployment dashboard.

Google Cloud

A run.app hostname is a useful Google Cloud clue because Cloud Run gives services a default URL on that domain. A company may also place its Cloud Run service behind a custom domain. If the browser’s Network panel shows a first-party application calling a verified run.app endpoint, you have evidence about where that particular service is deployed. docs.cloud.google.com

Think about how a website uses Google services before attributing its hosting to Google Cloud. A typical site may load Google Analytics, a YouTube video, or a Google font alongside content served from another provider. These requests tell you which integrations the page uses. The main document request and the first-party API calls are the ones to check for the website’s hosting.

Suppose a marketing site returns Netlify evidence, but submitting a search on the page triggers a request to a Cloud Run endpoint associated with the company. Your audit can say the public site is deployed on Netlify and the search service uses Google Cloud Run. That gives a maintainer a better starting point for tracing where the feature is deployed.

Azure

An azurewebsites.net hostname can point to Azure App Service. Microsoft documents this as a default domain for App Service web apps, which can also be made available under a custom domain. If a custom hostname’s DNS chain leads to an App Service domain, or a first-party feature interacts with that hostname, you have a service-specific Azure clue. Microsoft Learn

An azurefd.net hostname points to a different Azure product. Microsoft uses this domain for Azure Front Door endpoints. Front Door can receive the public request and route it to a backend. If you see DNS evidence for Front Door, report that delivery layer and look for separate evidence if you need to identify the upstream application service. Microsoft Learn

You may also find Server: Microsoft-IIS on the response. That is consistent with Microsoft web server software. A customer can run IIS in several hosting environments, so the product-specific Azure DNS target carries more weight when identifying the provider.

Vercel

For Vercel, look for x-vercel-id or x-vercel-cache on the main document response. You may also find a deployment hostname ending in vercel.app, which Vercel assigns to deployments. A DNS or deployment clue that agrees with the HTTP response gives you a stronger basis for attributing the inspected page to Vercel. vercel.com

Check the final document after redirects. If you open a branded domain and the destination returns a Vercel request ID, record the destination URL with that evidence. If only a linked demo or preview is hosted on vercel.app, assign the result to that deployment.

You may also see Vercel alongside Next.js. They describe different parts of the stack. Vercel headers point to the delivery or deployment platform for the response. A Next.js asset path such as /_next/static/ describes the framework that generated those assets. Next.js supports static exports that can be served by other providers, so check for Vercel’s own signals when the goal is hosting detection. vercel.com

Netlify

A CNAME pointing to a netlify.app hostname is a strong Netlify deployment clue for the hostname you’re checking. Netlify’s documentation shows how to point a custom www subdomain at the site’s netlify.app address. It also supports custom domains managed by an external DNS provider. You can therefore find one company in the nameserver records and Netlify in the actual website routing. Netlify Docs

Start by comparing the root domain and www. The root domain may use an address record or a flattened alias, while www exposes a provider-specific CNAME. Follow the URL in your browser to see which hostname actually delivers the page. That comparison is useful during migrations, when one hostname can be updated before the other.

If a Netlify deployment loads blog articles from a separate CMS or sends form submissions to a different API, keep the hosting finding scoped to the public frontend. When the audit concerns the CMS or the form handler, inspect the first-party requests associated with that feature and document them separately.

Cloudflare

You’ll often see Cloudflare through CF-Ray, CF-Cache-Status, or Server: cloudflare. With Cloudflare proxying enabled, DNS can return Cloudflare addresses and the browser connects to Cloudflare’s network. With a DNS-only record, Cloudflare can still manage DNS without proxying HTTP traffic for that hostname. That makes the combination of DNS and response headers more useful than nameservers alone. developers.cloudflare.com

Cloudflare can also be the deployment platform. Cloudflare Pages and Workers deployments can use platform-specific domains or custom domains. If you have evidence connecting the website to one of those services, describe the specific deployment. If you only see a Cloudflare response header on a custom domain, you can report Cloudflare in the delivery path and leave the origin provider unverified. Cloudflare Workers docs

A common mistake is to read CF-Cache-Status: MISS as if the browser connected directly to the host. The header tells you that the response was a miss at the Cloudflare cache. Cloudflare still handled that request. A cache miss can be helpful when diagnosing delivery, but the header alone gives you no additional provider name for the origin. developers.cloudflare.com

Why Hosting Detection Is Often Approximate

Public hosting checks reveal what the selected URL exposes. A managed provider can rent infrastructure from a larger cloud company. A CDN can return a cached page without contacting the origin for that request. DNS can resolve to a shared edge address, and a custom domain can hide the default deployment hostname. These are ordinary arrangements, which is why two website hosting checkers may return different answers for the same site. One may report the network registered to the public IP. Another may recognize the platform from its headers or DNS chain.

Use wording that someone else can verify. “www.example.com points to a netlify.app deployment” is more informative than “The company uses Netlify.” “Cloudflare serves the public homepage. Origin hosting unverified” captures a different finding. If you’re preparing a migration estimate, add the URL, the DNS target or header you observed, and the part of the site it applies to.

For a client-owned website, check the deployment dashboard, hosting account, or infrastructure configuration when the public evidence leaves a gap. Those records can answer questions a browser lookup usually can’t, including who controls the hosting account and where the production application is deployed.

To get started, enter the exact URL into the WebBuildFinder website hosting and technology checker. Compare its findings with the DNS target and the final document headers. If your work touches the homepage, store, and customer portal, check each one before writing a site-wide conclusion.

Need help with your website stack?

Share your current site or a reference build and tell us what you want to create or improve.

Discuss your project