Website to IP
See the IP address behind a website, who it belongs to, and what is serving it.
How to use the Website to IP
- Paste a website address — a full URL with https:// and a path is fine.
- Click Check.
- Read the addresses, the network they belong to, and which web server answered.
About the Website to IP
This tool takes a website address and shows the IP addresses behind it, along with who those addresses belong to and what actually answered the request. Paste a full URL if you like — the scheme, path and query string are stripped for you, so https://example.com/pricing?ref=x works the same as example.com.
The reason it reports more than the address is that on most sites today the address is not the whole answer. If a site sits behind a CDN, the IP you get back belongs to the CDN's edge network, not to the machine the site runs on — so an address that looks like a hosting company one week and a different one the next may just mean the CDN answered from a different location. This tool names the network from its reverse DNS record and says so plainly when a CDN is in front, rather than presenting an edge address as if it were the origin.
It also connects over HTTPS and reports the web server software, any X-Powered-By header and the status code that came back, which together tell you far more about how a site is built than the address alone. For a plain name-to-address answer with no HTTP request involved, use Domain to IP. For the full DNS picture including MX and TXT records, use DNS Lookup, and to read every response header in detail continue with the HTTP header checker.
Frequently asked questions
Why does this show a different IP than I expected?
Almost always because a CDN such as Cloudflare, Fastly or CloudFront is answering. The address you see is the edge server nearest the person asking, so it changes by location and over time. The tool says which CDN it recognised, so you know the address is an edge and not the origin.
Can it find the real server behind a CDN?
No, and no honest tool can. Hiding the origin address is one of the main reasons sites use a CDN. What you get is what the public internet gets.
How does it know who an address belongs to?
From the reverse DNS (PTR) record the address itself publishes, plus the Server header the site sends. It is not a WHOIS or paid IP-intelligence lookup, so when the record says nothing recognisable the tool leaves the owner blank instead of guessing.
Why can a site have several IP addresses?
For load balancing and redundancy: several machines, or several CDN edges, answer for the same name. An IPv4 address comes from an A record and an IPv6 address from an AAAA record, and a site can publish both. All of them are listed.
Does an IP address tell me where a website is located?
Not reliably. An address tells you which network announces it, which is often a data centre in a different country from the business running the site — and behind a CDN it only tells you where you are. Treat IP-to-city geolocation as a rough hint, never as a fact.