IP Address Lookup — What Is My IP

How it works

What we check

• Your public IP address — Leave the box blank and we report the public IP address your connection is presenting to the internet — the address websites and servers actually see, which is usually your router's address, not your device's private one.
• Any IP or domain you enter — Paste an IPv4 address (like 8.8.8.8), an IPv6 address, or a domain (like example.com). Domains are resolved to their IP first, since location and hostname lookups operate on IP addresses, not names.
• Approximate geolocation — We map the IP to an approximate location using our offline IP-location database. This is city- and country-level at best — it reflects where the IP is registered or routed, not a precise street address, and can be off by a city or more.
• Reverse DNS hostname — We do a reverse lookup to find the hostname registered for the IP, if any. ISPs and hosting providers often set these (revealing the network or data center); many home and mobile IPs have none.
• IPv4 vs. IPv6 — We identify the address type. IPv4 is the familiar four-number format (203.0.113.42); IPv6 is the longer colon-separated format (2606:4700:...) that exists because the world ran out of IPv4 addresses.
• Public vs. private detection — We flag private/local-network addresses (like 192.168.x.x or 10.x.x.x). Those only exist inside a home or office network and aren't reachable or geolocatable from the internet — so we label them rather than guess a location.

Common issues we catch

• The location isn't your exact address — IP geolocation is approximate by nature — it's based on where the address is registered or routed, not GPS. It's typically accurate to the country and often the city, but it can place you in a nearby city or your ISP's hub. Don't treat it as a pinpoint.
• Expecting a private IP to geolocate — Addresses like 192.168.1.5 or 10.0.0.2 are private — they're reused inside millions of separate home and office networks and never travel across the internet. They have no public location, so we label them "private / local network" instead of guessing.
• Your device IP isn't your public IP — The address your laptop or phone shows in its network settings is usually a private one handed out by your router. The public IP this tool reports (when the box is blank) is what the outside world sees — they're almost always different.
• VPN, proxy, or mobile network skews the result — If you're on a VPN, a proxy, or a corporate network, the IP and location reflect that exit point, not your physical location. Cellular IPs in particular often geolocate to the carrier's regional gateway, sometimes far from where you actually are.
• No reverse hostname found — Plenty of IPs — especially residential and mobile ones — have no reverse DNS record set. "None found" is normal and isn't an error; it just means the network operator didn't assign a hostname to that address.
• A domain resolves to a different IP than expected — A site behind a CDN or proxy (like Cloudflare) resolves to the CDN's IP, not the origin server — so the location and hostname describe the CDN edge, not where the site is truly hosted. Big sites can also rotate across many IPs.
• IPv6 address where you expected IPv4 — Modern networks may hand out an IPv6 address by default. It's a valid public address and works fine; it just looks unfamiliar. Some lookups have richer data for IPv4 than IPv6 simply because IPv4 has been mapped longer.

Where this matters

• Your own connection ("What is my IP") — Leave the box blank to instantly see the public IP your home, office, or mobile connection presents to the internet, plus its approximate location — the quickest way to answer "what is my IP?"
• IPv4 & IPv6 addresses — Both address families are supported. Enter either format and we detect the type, locate it, and look up its reverse hostname.
• Domains & websites — Enter a domain and we resolve it to an IP first, then show that IP's location and hostname — handy for checking where a site appears to be hosted or which CDN it sits behind.
• VPNs, proxies & CDNs — The tool faithfully reports the IP it sees, which means it reflects VPN exit nodes, proxy servers, and CDN edges. Useful for confirming a VPN is active or seeing which edge a CDN is serving from.
• Hosting & network troubleshooting — Reverse-DNS hostnames and approximate locations help identify whether an IP belongs to a known data center, ISP, or cloud provider — a quick first step when diagnosing connectivity or tracing where a request came from.