With your IP address, someone can find your country, region and usually your city, the name of your internet provider, and the type of connection: home broadband, mobile, business, or data center. They cannot find your street, your apartment, or your name. The address belongs to the ISP, not to you, and only the ISP knows which customer had it at a given moment. Here is what a website or a stranger really sees, where the errors come from, who can connect an address to a person, and how to check your own.

What an IP address is

It is the number the network uses to know where to deliver replies. Your ISP assigns it for the duration of a connection: a home router gets one address and every device behind it shares it. Mobile carriers often put thousands of subscribers behind one address (carrier-grade NAT), so "your" mobile IP is really a shared one.

You can see yours, and what geolocation databases say about it, on the What Is My IP page.

What a website learns from it

Websites do not investigate addresses in real time. They look them up in databases that map address ranges to regions and organizations. From those they get:

  • Country and region. Almost always right.
  • City. Usually right for large cities and home connections; for mobile networks it is often the city where the carrier's gateway is, not where you are.
  • ISP. The company that owns the range.
  • Connection type. Home, mobile, business or data center. The last one is how sites notice you are on a VPN or proxy.
  • Time zone and approximate coordinates. An estimate, not a fact.

Not in any database: your name, home address, phone number, browsing history. A site can know those only from other sources: cookies, your account, your browser fingerprint.

Why geolocation is often wrong

Databases update with delay, and ISPs move ranges between cities. Hence the familiar oddities: you are in Leeds and a site says Manchester; you are home and the weather app shows the next town. Mobile networks are wrong most often because the address is tied to the carrier's gateway. For the site it does not matter; country and rough region are all it needs.

Who can tie the address to a person

Only the ISP, which has a log of which customer used which address when. A website, forum or opponent in a game does not have that log. Getting it from the ISP requires a legal process, not a "lookup."

The practical conclusion: the threat "I'll find where you live from your IP" in an online argument is empty. The most the other person gets is a city and an ISP name.

What actually carries risk

  • Linking to other data. If you comment under your name from one address and under a pseudonym from the same one, a site can connect the two. The IP is not the source of the data; it is the link.
  • A long-lived address. The same home IP for months is a stable identifier that ad networks can use without cookies.
  • DDoS in games. In games with direct peer-to-peer connections, the other player sees your real address and can flood your connection. This is the one scenario where someone knowing your IP has a direct consequence, and the one where a VPN helps most obviously.

Check what yours reveals

  1. Open What Is My IP without a VPN: address, city, ISP. That is what any site sees.
  2. Open the Privacy Checker: it shows what your browser reveals on its own, without the IP, which is often more.
  3. Connect the VPN and repeat step 1: the address and city should be the server's.
  4. Run the WebRTC leak test and the IPv6 leak test: a browser and a network can reveal the real address around the tunnel.

What a VPN changes

With a VPN, sites see the server's address: a different city, a different provider, type "data center." Your real address is known only to the VPN service, and what it does with it is a policy question, covered in what does no logs mean. Everything a site knows about you through your account and browser is unaffected; the network layer is explained in what can my ISP see, the browser layer in browser fingerprinting explained.

404 VPN does not store your source IP address after the connection is established, and DNS stays inside the tunnel; the details are in the privacy policy. Get started here.