How to Track an IP Address for Free — Exact Location Guide

A small business owner gets a chargeback notification from a "customer" who claims they never placed an order. A freelancer discovers their portfolio photos reposted on a site they've never heard of. A parent receives a threatening message on their child's gaming account. Different situations, same first question: can I find out where this came from?

The answer is usually yes — to a point. Every device that connects to the internet broadcasts an IP address, and that address can be traced to an approximate geographic location, an ISP, and a network type. It won't give you a street address or a name, but it will tell you the country, often the city, and whether the connection comes from a residential ISP, a data center, or a mobile carrier. For many situations, that's enough to act on.

Most guides on this topic either oversell it ("track anyone's exact location!") or undersell it ("IP addresses are meaningless"). Neither is true. This guide covers the five methods that actually work in 2026, with real accuracy data, the modern complications that most guides skip, and practical advice on what to do with the results.

What an IP Address Actually Tells You

An IP address identifies a network connection, not a person and not a precise location. When you look up an IP, a geolocation database maps it to an approximate area based on how internet service providers allocate address blocks to their infrastructure.

Here's what a typical lookup returns:

• Country and city — usually the city where the ISP's equipment is located, not necessarily where the user is sitting
• ISP name — the company providing internet access (e.g., Comcast, Vodafone, Jio)
• ASN (Autonomous System Number) — the network's routing identifier, useful for identifying organizations
• Connection type — residential, business, hosting, or cellular
• Latitude/longitude — approximate coordinates, typically pointing to the ISP's local hub
• Timezone and region — derived from the mapped location

Here's what an IP address does not tell you:

• The person's name, email, or physical street address
• Their exact building or household
• Whether they're the only person using that IP (they usually aren't)

The distinction between "city-level" and "street-level" matters. When a database says an IP is in "Chicago," it could mean anywhere in the greater Chicago metro area — a region spanning thousands of square kilometers.

Real Accuracy Numbers (With Sources)

Most IP tracking guides say geolocation is "approximate" without quantifying what that means. Here are the actual numbers.

MaxMind publishes accuracy statistics for their GeoIP2 City database, measured against known user IP-location pairs. The results vary significantly by country:

The industry-wide consensus, drawing from multiple independent studies, breaks down like this:

A key finding from the ipapi.is comparative study (ongoing since January 2026): the 75th percentile deviation across all major providers ranges from 128 to 288 km. Meaning one in four lookups is off by at least 80–180 miles.

There's also a significant gap between IPv4 and IPv6 accuracy. IPv4 addresses have been mapped for decades and have richer data. IPv6, which is newer and assigned in enormous blocks, is dramatically less accurate — around 40–60% at the country level compared to 90%+ for IPv4.

5 Methods to Track an IP Address

Here are the practical methods, ordered from simplest to most involved.

Method 1: IP Geolocation Lookup (Instant)

Method 2: Email Header Analysis

Method 3: Tracking Links and Pixels

Method 4: Server Logs and Analytics

Method 5: Command Line Tools

Can You Track an IP Address to an Exact Location?

This is the most common question people have about IP tracking, so let’s be direct: you cannot track an IP address to a street address or specific building. But you can often get surprisingly close — depending on the circumstances.

What “exact location” actually means with IP tracking

When geolocation databases return a latitude and longitude for an IP address, that coordinate represents the estimated center of the area the IP serves. Think of it as the middle of a circle, not a pinpoint on a map.

When IP geolocation gets close

Some scenarios produce more precise results than others:

• Static residential IPs in dense urban areas — A home user with a fixed IP in central London or Manhattan will typically geolocate within 5–15 km. ISP infrastructure maps are detailed here because the address blocks are small and well-documented.
• Business fiber connections — Companies with dedicated IP ranges often geolocate very accurately because the ISP has precise records tied to the service address.
• University and corporate networks — Institutional IPs are registered to specific addresses in WHOIS databases, making them among the most accurate to geolocate.

When IP geolocation fails completely

• Mobile/cellular connections — CGNAT means the IP belongs to a cell tower or regional hub, not the user’s location. The reported location could be 50–200 km away.
• VPN and proxy users — The IP belongs to the VPN server. A user in Miami could show an IP in Amsterdam.
• Starlink satellite internet — Traffic routes through whichever ground station has line-of-sight, often in a different state.
• IPv6 addresses — Only 40–60% accurate at the country level. City-level accuracy is even worse.
• Cloud hosting IPs — AWS, Google Cloud, and Azure IPs geolocate to data center locations, not to the person using the service.

The bottom line: treat IP geolocation as city-level or regional, never as a GPS coordinate. For investigations that require precise location data, IP tracking is one signal that must be combined with other evidence.

The Modern Complications Nobody Talks About

Most IP tracking guides were written as if it's 2015. The internet's infrastructure has changed significantly, and several developments have made IP tracking less reliable than it used to be.

VPN usage has gone mainstream

When someone uses a VPN, their IP address belongs to the VPN provider's server — typically in a different city or country entirely. Geolocation returns the VPN exit node's location, not the user's. There's no way around this from the IP alone.

This isn't a niche concern. With roughly a third of global internet users on VPNs, any IP-based analysis needs to account for the fact that a substantial chunk of the data points to VPN servers rather than actual user locations. Tools like our VPN Detector can identify when an IP belongs to a known VPN provider, which at least tells you the location data is unreliable for that user.

Carrier-grade NAT: One IP, thousands of users

Mobile carriers don't assign each phone a unique public IP address. Instead, they use Carrier-Grade NAT (CGNAT), which puts hundreds or thousands of subscribers behind a single public IP. The geolocation for that IP points to the carrier's regional hub, which could be in a different city entirely.

If you're tracking a mobile user in suburban New Jersey, the IP might resolve to a T-Mobile facility in Manhattan. The geolocation is technically "correct" — that is where the IP is registered — but it's useless for locating the actual user.

CGNAT is now the default for most mobile internet worldwide, and it's increasingly used by home ISPs in regions facing IPv4 exhaustion. This means a growing percentage of IPs simply cannot be geolocated to individual users.

Starlink breaks the model entirely

Starlink, with over 5 million subscribers, routes traffic through satellites to whichever ground station has line-of-sight at that moment. A user in Orlando might route through a ground station near Atlanta, and the geolocation will show Georgia instead of Florida.

This is such a systemic problem that APNIC Labs has started overriding Starlink's geolocation data for 20 affected countries. As satellite internet grows, this will only get worse. There's no software fix for the fundamental physics of satellite routing.

MaxMind is returning less data, not more

In a notable shift, MaxMind began blanking out city, subdivision, and postal code data more frequently starting December 2025 for networks where "end users are dispersed all over the country." The industry's largest geolocation provider is essentially admitting that for certain IP ranges, claiming a city-level location would be misleading.

The trend is toward less granular IP geolocation, not more. Databases are getting more honest about their limitations rather than guessing and being wrong.

Legal Considerations: What You Need to Know

Looking up an IP address in a geolocation database is legal everywhere. It's publicly available data, and the lookup itself reveals no personal information — just an approximate location and ISP name.

But the legal landscape gets more complex when you're collecting IP addresses or trying to identify who's behind one.

In the EU: IP addresses are personal data

The European Court of Justice ruled in Breyer v. Germany (Case C-582/14) that even dynamic IP addresses constitute personal data under GDPR when the data controller has the legal means to identify the person — for example, by requesting subscriber information from the ISP. If you operate a website serving EU users and log IP addresses, you need a lawful basis under GDPR (typically "legitimate interests" for security logging, but this requires a documented assessment).

In the US: it depends on context

Under California's CCPA/CPRA, whether an IP address counts as "personal information" depends on context. An IP on its own may not qualify, but combined with other data (browsing behavior, account information), it can. The California Attorney General calls this a "fact-specific and contextual" determination.

Identifying the person behind an IP

This is the critical line: looking up where an IP is located is one thing. Figuring out who is using that IP requires ISP cooperation, which requires a subpoena or court order. Private individuals and companies cannot compel an ISP to reveal subscriber information. Only law enforcement, through proper legal channels, can connect an IP address to a specific person.

This is why IP tracking is useful for understanding where traffic comes from (country, city, ISP), but it's not a way to identify or locate specific individuals.

Making Sense of IP Data

Given all of the above, here's a realistic framework for using IP geolocation effectively:

High confidence: Country identification (92–99% accurate), ISP identification, connection type (residential vs. hosting vs. cellular), VPN/proxy detection.

Moderate confidence: State/region (55–80%), city in well-mapped countries like Germany or Canada.

Low confidence: City-level in poorly-mapped regions, anything below city level, any mobile/Starlink IP, any IP flagged as VPN/proxy.

The practical approach is to treat IP geolocation as one signal among several. Combine it with timezone data, Accept-Language headers, and other contextual information rather than relying on it as a sole source of truth.

For security investigations, the ISP and ASN data is often more valuable than the location data. Knowing that traffic comes from a hosting provider (suggesting a bot or proxy) versus a residential ISP (suggesting a real user) is frequently more actionable than knowing the approximate city.

Free IP Tracking Tools

You don’t need paid software to track IP addresses. Here are the free tools that cover every common use case:

All four tools work in your browser with no account, no download, and no usage limits for standard lookups.

Frequently Asked Questions

Accuracy data cited in this article comes from MaxMind's published GeoIP2 accuracy statistics, IP2Location's accuracy page, the ipapi.is comparative study, AbstractAPI's accuracy research, and WhoisXMLAPI's IPv6 geolocation analysis. All links are provided inline. Data is current as of February 2026.