What Domain Hosting Checker does
The Domain Hosting Checker resolves the submitted domain to bounded public IPv4 and IPv6 answers. It selects an IPv4 result when available, otherwise the first public address, and queries IP RDAP for the registered network handle, name, country, and address range.
Network registration is not always hosting-company identification. Sites commonly place Cloudflare, Fastly, Akamai, or another reverse proxy in front of the origin, and large providers can allocate address space across many services. Interpret the network record as attribution for the resolved IP, not proof of the physical server, account owner, or origin infrastructure.
How to use Domain Hosting Checker
- Enter a complete public domain name without a URL path.
- Select Inspect hosting to resolve the domain and query IP RDAP.
- Review all returned public addresses and the network record associated with the selected address.
- Check CDN, DNS, and provider documentation before treating the network name as the origin host.
Important details
DNS answers can vary
Geo-routing, load balancing, DNS cache state, and resolver location can return different addresses at different times. The report is a server-side snapshot rather than a complete map of every endpoint.
IP RDAP identifies registered address space
The handle, network name, country, and range come from public IP registration data. They describe who holds or administers the address block, which may differ from the company selling the hosting plan.
CDNs obscure origin infrastructure by design
When DNS points to a CDN or reverse proxy, the visible IP belongs to that edge network. This tool does not attempt to bypass the proxy or discover a protected origin address.
Practical uses
- Identify the public network currently serving a domain during troubleshooting.
- Confirm whether a DNS change appears to point at a new provider or CDN.
- Collect address-range context before escalating an abuse or routing issue.
Privacy and limitations
The domain is sent to PagesTools for DNS resolution and an IP RDAP request. The DNS resolver, RDAP service, and resolved network can receive ordinary query or connection metadata; the JSON response uses no-store cache headers.
The result can reflect a CDN, proxy, shared host, or current load-balanced endpoint. It does not reveal private account details, server location with certainty, or a protected origin address.