What Your IP Address Actually Reveals (And What It Doesn't)

When you connect to any website, server, or online service, your public IP address is visible to the other side. It has to be — without it, responses couldn't find their way back to you. But how much does that actually reveal? The answer is more nuanced than most people realize.

Public vs private IP addresses

Your device almost certainly has two IP addresses: a private one assigned by your router, and a public one assigned by your ISP that the internet actually sees.

Private addresses exist within three reserved ranges (the same ranges used when designing internal subnets):

• 10.0.0.0/8 — used in large corporate and cloud networks
• 172.16.0.0/12 — common in enterprise environments
• 192.168.0.0/16 — what your home router hands out to phones, laptops, TVs

These are not routable on the public internet. Traffic from your device goes to your router, which has a single public IP, and that router handles the translation via NAT (Network Address Translation). Multiple devices share one public IP.

This is why checking your IP on a website shows your public IP, not the 192.168.x.x address your device thinks it has. The private address never leaves your local network.

What a public IP address reveals

Your ISP. IP address blocks are registered to organizations in publicly accessible WHOIS and RDAP databases. Given any IP address, a lookup reveals which ISP or organization owns that address block. This is highly reliable.

Approximate country and region. Geolocation databases map IP blocks to geographic locations based on ISP registration data, BGP routing announcements, and other signals. Country-level accuracy is very high — above 95% for most databases. Region/state-level accuracy drops to around 80%. City-level accuracy is considerably worse, often 50–70% at best.

Timezone. Derived from the geolocation estimate, and subject to the same accuracy limitations.

AS number. The Autonomous System Number identifies the routing entity that owns the IP block — usually the ISP or a large organization with its own network infrastructure.

What it does not reveal

Your physical address. The city shown in a geolocation lookup is typically where your ISP's regional hub is registered, not where you physically are. For mobile networks, this can be hundreds of kilometers off. For home broadband, it might be a nearby city or the ISP's data center city, not your street or building.

Your identity. An IP address is not tied to a person — it's tied to a connection point. Multiple people share public IPs (everyone behind the same home router, or everyone on a corporate network). Identifying a specific person from an IP address requires legal processes and ISP cooperation, not a simple lookup.

Your browsing activity. Knowing someone's IP address does not tell you what they're doing online. That information lives in access logs on the servers they connect to, and in their own connection logs — not in the IP itself.

IPv4 vs IPv6

IPv4 addresses are 32-bit numbers written in dotted-decimal notation: 203.0.113.45. There are about 4.3 billion possible IPv4 addresses, a number that seemed vast in the 1980s and has since been completely exhausted. Network address translation and private address ranges have extended IPv4's lifespan considerably, but the address space is gone.

IPv6 addresses are 128 bits, written in hexadecimal groups separated by colons: 2001:0db8:85a3:0000:0000:8a2e:0370:7334. That's 2^128 possible addresses — enough for approximately 340 undecillion devices. IPv6 adoption has been slow but is accelerating; most modern connections support both.

One significant difference: IPv6 privacy extensions. Because IPv6 addresses can be derived from a device's MAC address, some implementations rotate the interface identifier portion of the IPv6 address periodically to prevent tracking. Most modern operating systems do this by default.

VPNs and what they actually hide

A VPN replaces your public IP with the IP of the VPN server. Websites and services see the VPN server's IP, not yours. This changes the location data they see, can bypass geographic content restrictions, and prevents your ISP from seeing which sites you connect to (though your traffic is now visible to the VPN provider instead).

What a VPN does not do: make you anonymous online. Websites can still fingerprint your browser through cookies, canvas fingerprinting, WebRTC leaks, and behavioral analysis. And the VPN provider itself can see all your traffic — you're trusting them instead of your ISP.

For testing geo-restrictions, verifying infrastructure from different locations, or simply hiding your home IP when connecting to external services you operate, a VPN is useful. It is not a privacy silver bullet.

Using IP lookup in practice

Common reasons developers and sysadmins check their public IP:

• Confirming that a VPN or proxy is active before connecting to a sensitive resource
• Verifying what public IP a cloud server or NAT gateway is using before adding it to a firewall allowlist
• Diagnosing why geo-restricted content isn't loading as expected
• Checking ISP and AS number for a connection that's behaving unexpectedly