Hosting Checker - Know Who Is Hosting the Website

Hosting Checker

What the hosting checker does

This page looks up information about the network that serves a domain. Enter a domain and the tool resolves it, queries an IP geolocation and hosting data service, and displays the result as summary cards, a detailed table and a map. The goal is to help you understand where a site appears to be hosted, which network announces its address and which organisation owns that network. It is a research aid, not a guarantee of physical location.

How to run a check

Type a domain into the field and press the check button. If the page was opened with a domain or query parameter, it may prefill the value and run automatically. The server resolves the host and queries the external service. Wait for the cards and table to fill. If the domain has several addresses, the result may show one representative address rather than every edge server. Run the check again later if you need a fresh view.

Reading the summary cards

The cards summarise the resolved address, country, organisation or hosting provider and a few network details. In the current build, the field labelled Server IP may repeat the domain name instead of showing the numeric address. Use the detailed table for the actual IP and related fields. A repeated domain is a display quirk, not evidence that the lookup failed.

The detailed table

The table contains the fields returned by the lookup service, including address, country, region, city, postal code, latitude, longitude, timezone, ASN, ISP or organisation and hosting flags. Not every field is populated for every address. A blank field may mean the service has no data, the address is behind a proxy, or the response format has changed. Read the raw values and the table together rather than relying on one card.

Hosting provider versus registrar

A hosting provider runs the servers or network that deliver the site. A domain registrar manages the domain registration. They can be the same company, but they often are not. A site can use Cloudflare for DNS, a cloud provider for compute, a CDN for static assets and a separate registrar for the domain. This lookup sees network data for an address; it does not prove who owns the website or where the business is legally based.

CDNs, proxies and VPNs

Large sites often use a content delivery network or reverse proxy. The address you see may belong to the CDN, not the origin server. Geolocation can point to a data centre that is nowhere near the business or its users. A VPN or privacy proxy can add another layer. Treat the country and city as approximate network hints, not as a statement about the website owner's location.

Cache and freshness

The server caches lookup results for about a day and uses a timeout for the external request. Caching makes repeated checks fast but can hide a recent hosting change. If a site has just migrated, the old network may still appear. Wait for the cache to expire, or check a different domain or subdomain. The page is not a live uptime monitor and does not test whether the site is reachable from your location.

Fallback data

If the primary lookup service is unavailable, the page may use a fallback provider. The fallback can return fewer fields, an incomplete country or a missing map position. An incomplete result is not proof that the domain has no hosting data. Try again later, or query the address with a network tool. The page does not expose a manual API key field, so the primary service's availability affects the result.

What this is good for

Use it to sanity-check where a domain resolves, to see whether a site sits behind a known cloud or CDN, or to gather network context during a security review. It can also help you notice an unexpected country or provider after a migration. It is not enough for attribution, legal evidence or a definitive hosting bill. Combine it with DNS records, certificate data, HTTP headers and the provider's own tools.

Privacy and data sent

The domain you enter is sent to the server, which resolves it and sends the address to an external geolocation service. Do not enter a private URL with credentials, a token in the query string or an internal hostname. The lookup does not log in to the site and does not scan its ports. The external provider may see the queried address and request metadata.

Common problems

If nothing happens, check that the domain is spelled correctly and has a valid public address. If the map is blank, the geolocation fields may be missing or the map library may not have loaded. If the Server IP card shows the domain, use the table. If the result looks stale, wait for the cache or try a subdomain. If the site is behind Cloudflare or another CDN, expect the CDN's network rather than the origin.

What not to do

Do not treat the result as the physical address of a person or company. Do not conclude that a site is malicious because it uses an unfamiliar hosting provider. Do not use the page for port scanning, unauthorized access or bypassing a block. Do not enter credentials or private URLs. Do not rely on a single cached lookup for a time-sensitive security decision.

Shared hosting can put hundreds of sites on one address, so the network owner is not the same as the site owner. Use the result as a network clue, not as attribution.

Frequently Asked Questions