Why You'd Want a Website's IP Address
Every website on the internet is ultimately hosted on a server that has an IP address. The domain name (like example.com) is just a human-readable alias that the Domain Name System (DNS) translates into an IP address behind the scenes. There are many practical reasons to look up a website's IP address:
- Network troubleshooting: Testing whether a domain resolution problem is a DNS issue or a server issue
- Security research: Identifying the hosting provider, data center, or CDN behind a website
- Bypassing DNS blocks: Accessing a site directly via IP if DNS-based filtering is in place
- Checking for shared hosting: Seeing how many domains share the same server IP
- Verifying CDN configuration: Confirming that Cloudflare, Akamai, or another CDN is fronting the origin server
- WHOIS investigation: Using the IP to find the hosting organization via WHOIS lookup
Note that modern websites behind CDNs (like Cloudflare) may return the CDN's IP rather than the origin server's IP. This is intentional — CDNs act as a shield between the public internet and the real server.
Using Ping to Find a Website's IP Address
The simplest way to find a website's IP is the ping command, available on Windows, Mac, and Linux. It resolves the domain to an IP and shows round-trip latency.
On Windows: Open Command Prompt (Win+R, type cmd) and run:
ping google.com
Output example:
Pinging google.com [142.250.80.46] with 32 bytes of data:
Reply from 142.250.80.46: bytes=32 time=12ms TTL=117
The IP address appears in the brackets immediately after the domain name — in this case 142.250.80.46.
On Mac/Linux: Open Terminal and run the same command. To ping just once (instead of continuously on Linux), use ping -c 1 google.com.
You can also use our online ping tool to test connectivity and resolve domain names to IPs without using the command line at all.
Look Up Any IP or Domain
Our free IP lookup tool resolves domains and reveals full network details instantly.
Hide My IP NowUsing nslookup and dig for DNS Resolution
nslookup and dig are dedicated DNS query tools that give you more detail than ping. They're available on all major operating systems.
nslookup (Windows/Mac/Linux):
nslookup github.com
Output:
Server: 192.168.1.1
Address: 192.168.1.1#53
Non-authoritative answer:
Name: github.com
Address: 140.82.114.4
dig (Mac/Linux): The dig command is more powerful and is preferred by network professionals:
dig github.com A
The A flag requests the IPv4 address record. For IPv6, use AAAA. For all records:
dig github.com ANY
On Windows, dig isn't included by default but can be installed via BIND tools or WSL. Alternatively, use our online DNS lookup tool which supports A, AAAA, MX, TXT, CNAME, and NS record lookups without installing any software.
Finding the Real IP Behind a CDN
Many popular websites use Content Delivery Networks (CDNs) like Cloudflare, Fastly, or Akamai. When you query these domains, you'll get the CDN's edge server IP, not the origin server's IP. For example, querying a Cloudflare-protected site returns a Cloudflare IP in the 104.x.x.x or 172.x.x.x range.
To attempt to find the origin IP, try these techniques:
- Check historical DNS records: Tools like SecurityTrails or ViewDNS.info store historical DNS data. If the site wasn't always behind a CDN, you may find the old origin IP.
- Query the MX record: Mail servers are sometimes on the origin hosting provider and may reveal the real subnet:
dig example.com MX - Check subdomains: Subdomains like
mail.example.com,ftp.example.com, ordirect.example.comare often not CDN-protected and may reveal the origin IP. - Look at SSL certificate logs: Certificate Transparency logs (crt.sh) sometimes reveal subdomains that point directly to origin servers.
After identifying an IP, run a WHOIS lookup to identify the hosting provider and datacenter location.
Interpreting What You Find
Once you have a website's IP address, you can extract a wealth of information from it using various tools:
- Geolocation: Use our IP lookup tool to find the physical location of the server — country, city, and data center.
- Hosting provider: The ASN (Autonomous System Number) associated with the IP reveals the hosting company. Large providers include AWS (Amazon), GCP (Google), Azure (Microsoft), Cloudflare, Akamai, and DigitalOcean.
- Reverse DNS: The PTR record for an IP sometimes reveals the server's hostname, which can contain useful identifiers.
- Open ports: Use our port checker to see which services are running on the IP — HTTP (80), HTTPS (443), SSH (22), etc.
This information is invaluable for security research, competitive analysis, and network administration. Always ensure you have authorization before probing ports or services on any IP address you don't own.

Frequently Asked Questions
Does a website's IP address change?
It depends. Small sites on shared or VPS hosting may have stable IPs. Sites behind CDNs return different IPs depending on which edge server is closest to you. Large platforms like Google or Facebook use anycast routing, where many IPs are in use simultaneously. Use DNS TTL (time-to-live) values to see how often records refresh.
Can I browse to a website by IP address instead of domain name?
Sometimes, but not always. If the server hosts multiple websites (virtual hosting), it needs the domain name in the HTTP Host header to know which site to serve. Direct IP access may show a default page, a 403 error, or a CDN splash page instead of the intended website.
What does it mean if a website has multiple IP addresses?
Multiple A records for a domain indicate load balancing — traffic is distributed across several servers to handle high volumes and improve redundancy. Large services like Google can have dozens of IPs. DNS round-robin and anycast routing are common techniques for this.
Is it legal to look up a website's IP address?
Yes, DNS lookups are completely public and legal. When a domain owner publishes DNS records, that information is publicly accessible by design. WHOIS data is similarly public. The information gathered through these lookups is used routinely by network administrators, security researchers, and developers worldwide.
