Langues

Hosting Checker

Free, no signup. See which public network and edge platform a domain exposes — and the specific DNS or response-header evidence for it.

Built by Patrick Stox

Checks run from our server; we fetch the URL you enter and don't keep the results. This queries public DNS and makes one public web request. A CDN or reverse proxy can hide the origin provider; this tool never treats edge evidence as proof of the origin. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.

Feedback
Report a bug

Found something broken in Hosting Checker? Let us know what happened — this goes straight to a private triage queue, not a public list.

What will be sent 
 No tool inputs, uploads, pasted source, complete results, query parameters, or URL fragments are attached automatically. You can edit or remove the selected passage above. Browser and anti-abuse metadata is processed for spam prevention. 
  
 
  
 
 
  
 
 
  
 
Sample report
Illustrative example — fixed public signals, not a domain lookup
Cloudflare is proxying this site; the origin host is not visible from this public check.
  • Evidence: server: cloudflare and cf-ray were present.
  • IP & network: the displayed addresses belong to the public edge network.
  • DNS & mail: an MX answer is listed separately and is not called the web host.
  • Transfer: Content-Encoding: br means Brotli was observed on this response.
 
 
 
How to use it
  1. Enter a bare domain such as example.com.
  2. Choose Check hosting and read the delivery verdict with its evidence.
  3. Separate the observed IP network, CNAME, and response-header fingerprints from the mail-host MX records.
  4. If a proxy is detected, treat the origin as unknown unless you can verify it through your own account or configuration.
 
 
     
 Local data 
Saved targets, named lists, and recent check summaries remain only in this browser.
 
   
 
     
How to read the result
  • Delivery verdict summarizes the strongest supported edge or ASN evidence.
  • Origin not visible means a proxy or edge platform terminates the public request.
  • IP network is the ASN organization for the observed A/AAAA address, not necessarily the hosting brand.
  • CNAME and MX are raw public DNS answers; MX describes email.
 
Data sources & freshness
The endpoint performs bounded public A/AAAA, CNAME, and MX lookups and one web request. Team Cymru ASN DNS data enriches observed IPs with network organization, registry, and country. A deterministic fingerprint table checks selected headers and CNAMEs for supported edge platforms, while transfer inspection reports compression and only documented protocol hints.
 
Features
  • Public IP, ASN, CNAME, and MX evidence in one report.
  • Supported CDN and edge fingerprints from DNS and headers.
  • Compression and protocol-hint summary.
  • Explicit distinction between delivery network, origin host, and mail host.
 
Limitations
A Cloudflare, Fastly, or similar result describes the public edge and may conceal the origin. ASN country is not a physical server location. Private DNS, multi-CDN routing, geographic answers, reseller relationships, and infrastructure without a supported fingerprint can make the picture incomplete.
 
Frequently asked questions
Can a hosting checker identify the origin host behind Cloudflare?
Usually not. A reverse proxy publishes its own edge IPs and headers while deliberately hiding the origin. The checker reports Cloudflare as the delivery layer and leaves the origin unclaimed.
Is the reported country the server location?
No. Country and registry values come from public ASN data for the observed IP network. They are not proof of the physical datacenter, origin server, or where site data is stored.
Why does the tool show a CDN instead of my web host?
Public DNS and HTTP requests terminate at the CDN or edge proxy when one is configured. That is the infrastructure visible to visitors; the underlying host may not expose a public fingerprint.
Does the MX record show who hosts the website?
No. MX records describe mail delivery. The report lists them separately because email and web hosting are often provided by different companies.
Next stepHTTP Header Checker — verify it with a direct check.

People also explore
ToolDNS CheckerToolWebsite Down CheckerToolDomain ReportArticleCaching for SEOArticleHTTP/2 and HTTP/3ArticleCDN and SEO
 
 
 
Feature requests for Hosting Checker
 

Upvote what you want most. New ideas can be submitted from the floating Feedback menu;
      requests appear here once approved, and the most-wanted rise to the top.

   
Loading…
  
  ➕ Request a feature   
New requests are reviewed before they appear here.
 
     
  
  
 
 
 
 
   
  
À propos de l’outil
Identifiez les signaux publics du réseau et de la plateforme edge d’un domaine, puis comparez-les aux preuves DNS et aux en-têtes de réponse. Le rapport distingue clairement un proxy ou un CDN de l’hôte d’origine et n’invente pas une attribution lorsque les indices sont insuffisants.
Fonctionnalités
  • Résolution du réseau IP public, de l’ASN, du fournisseur edge et des empreintes de réponse.
  • Preuves DNS, hôte de messagerie, compression et en-têtes renvoyés par la cible.
  • Détection des conflits entre signaux DNS, en-têtes, CDN et fournisseur supposé.
  • Rapport exportable avec distinction entre observation publique et attribution incertaine.
Fonctionnement
Le service résout le domaine, examine les réponses publiques et associe les adresses et en-têtes à des preuves de réseau et de plateforme. Le navigateur regroupe les indices, signale les conflits et sépare les faits observés des déductions prudentes.
Limites
  • Un CDN, un reverse proxy ou une couche edge peut masquer l’origine ; le résultat ne révèle pas l’infrastructure privée.
  • Les bases ASN et les signaux de réponse peuvent changer et ne constituent pas une preuve de propriété ou de facturation.
Questions fréquentes
Le vérificateur identifie-t-il le serveur d’origine derrière un CDN ?
Pas nécessairement. Un CDN ou un proxy peut masquer l’origine ; le rapport le signale au lieu de présenter le réseau edge comme l’hébergement réel.
Quelles preuves sont utilisées ?
Le rapport combine résolution DNS, réseau IP, ASN, en-têtes de réponse, compression et indices de plateforme visibles publiquement.
Les résultats prouvent-ils quel fournisseur je paie ?
Non. Ils décrivent des signaux publics observés et peuvent nécessiter une confirmation par la facturation ou la configuration d’infrastructure.
Les domaines sont-ils conservés ?
Non. Le domaine est consulté pour produire le rapport ; une courte cache de périphérie peut accélérer une vérification répétée.