- Home
- Domain, DNS and IP
- Hosting Checker
Hosting Checker
Find out where a site runs, and on what infrastructure.
DNS resolution then a query to the regional IP address registries, completed by reading the name servers and the MX records. No usage limit.
What this tool is for
Knowing where a site runs answers very concrete needs. You are taking over a site and nobody knows who hosts it. You have to report unlawful content, and the host is the only legally competent recipient. Or you are sizing up a competitor and want to understand their infrastructure.
The identification rests on the fact that IP address ranges are allocated publicly by regional registries. By resolving the domain to its address, then the address to its owner, you get back to the operator.
One limit has to be known up front: if the site goes through a delivery network, it is that network that appears and not the origin server. That is precisely its reason for existing. The name servers and MX records then remain the best clues.
An often forgotten use: checking that your own site really is where you think it is. After a migration, some traffic sometimes keeps pointing at the old server for weeks.
How to read the results
The owner of the IP range is the most reliable piece: it comes from the regional registries and is kept up to date. That is the name to note for a report.
The server’s country has lost all importance for rankings. Google goes by the domain extension and the content, not where the machine sits. It stays relevant for latency and for questions of jurisdiction.
The name servers reveal who runs the DNS zone, which is not necessarily the host. When a delivery network hides the origin, they are often the best clue left.
The MX records show the mail provider. They often reveal infrastructure different from the site’s — mail at a large provider, site at a local host.
The number of domains on the same IP distinguishes shared from dedicated. The reverse IP lookup sets out that neighbourhood.
Common mistakes
Confusing the registrar with the host. The first sells the domain name, the second runs the site. They are often two different companies, and addressing the wrong one wastes time.
Concluding too fast in front of a delivery network. Seeing a CDN operator’s name says nothing about the real server. Carry on with the name servers and the MX records.
Believing the server’s country influences local ranking. Hosting in a country does not lift you in that country’s results. The extension, the language and the content do that.
Reporting content to the wrong party. The host is the legally competent recipient, not the registrar and not the delivery network. Identifying correctly avoids a report that goes nowhere.
Neglecting the neighbourhood on shared hosting. Sharing an IP address with hundreds of sites exposes you to their reputation, notably where mail blacklists are concerned.
Going further
- Domain to IPResolves a domain to an IP address
- Reverse IP LookupSites sharing the same address
- DNS LookupA, MX, TXT, NS records and full DNS configuration
- Whois LookupRegistration, expiry and ownership details of a domain name
Frequently asked questions
Why does the tool show Cloudflare and not my real host?
Because a delivery network sits between visitors and your server. That is its job: it hides the origin address to protect the server from direct attacks. In that case only the name servers and the MX records still give clues about the real infrastructure.
What is knowing a site’s host good for?
Three common uses. Taking over a site whose access has been lost and finding where it runs. Reporting unlawful content to the host, the only legally competent recipient. And sizing up a competitor: a fast site on high-end infrastructure is not facing the same constraint as a site on entry-level shared hosting.
Does the host affect rankings?
Indirectly, through server response time, which governs the LCP. A saturated shared host taking a second to answer makes a good LCP nearly impossible. The server’s geographic location, on the other hand, has not counted for a long time: Google goes by the domain and the content, not where the machine sits.
How do I tell a name server from a host?
They are two distinct functions, often handled by different parties. Name servers run the DNS directory; the host runs the site. You can perfectly well buy the domain from a registrar, run the DNS with a third party, and host somewhere else again.
Can I tell whether a site is on shared hosting?
The best clue is the number of domains sharing the same IP address. An address hosting hundreds of sites indicates shared hosting; an address dedicated to a single domain suggests a dedicated server or a cloud instance. The reverse IP lookup gives that information directly.
Is the information shown always accurate?
It is reliable on the identity of the owner of the IP range, which is public and up to date. It is less so on the final provider: a reseller can rent addresses from a large operator, and it is the operator’s name that will appear, not that of the party you deal with.