IP Geolocation

Find the country, city, region, ISP, timezone and map coordinates for any IPv4 or IPv6 address. Enter an IP or hostname below to get started — free, no sign-up needed.

Enter any IPv4, IPv6 or hostname — or try one of the examples below.
Enter an IP address to get started
Type any IPv4, IPv6 address or hostname above and click Geolocate to see its country, city, ISP, timezone, coordinates and more.
Not stored or logged
Real-time lookup
No sign-up needed

What This Tool Shows You

Enter any IPv4 address, IPv6 address or hostname and this tool returns the full geolocation profile in real time: country, region, city, postal code, latitude and longitude coordinates with an interactive map, timezone with UTC offset, local currency, ISP, organisation, AS number, and connection type flags. Domain names and hostnames are resolved to an IP first via DNS, then geolocated. Results are fetched live on every query — nothing is cached or stored.

Country, City & Region

The geographic location associated with the IP block, with a flag and country code, plus an interactive map pin.

Timezone & Currency

The timezone and UTC offset for the IP's location, plus the local currency — useful for localisation logic.

ISP & ASN

The Internet Service Provider and Autonomous System number that owns the IP block, with a direct link to ASN details.

Connection Type Flags

Whether the IP is a mobile carrier, a known VPN or proxy service, or a hosting and data-centre address.

How IP Geolocation Works

Every public IP address is registered with a Regional Internet Registry and assigned to a specific network operator — an ISP, cloud provider, university or enterprise. Geolocation databases build a mapping from IP ranges to geographic locations by combining RIR registration data, BGP routing table observations, and active network measurement. The result is a probabilistic estimate, not a GPS fix.

Accuracy varies by connection type. Fixed residential broadband IPs are usually accurate to city level. Mobile IPs geolocate to carrier hubs, which may be hundreds of kilometres from the device. VPN and proxy IPs return the exit node's location. Cloud and hosting IPs resolve to the data centre's city. The Proxy / VPN and Hosting / DC flags indicate when these scenarios apply so you know to interpret the location accordingly.

Practical Uses for IP Geolocation Data

Frequently Asked Questions

How accurate is IP geolocation?

Accuracy depends heavily on connection type. Fixed residential broadband is typically accurate to city level, since ISPs register their address blocks against the city where their infrastructure is concentrated. Mobile and satellite connections often geolocate to a carrier routing hub, which may be hundreds of kilometres from the device's actual position. VPN connections display the exit node's location, not the user's physical location. Hosting and cloud IPs resolve to the data centre city.

IP geolocation is a probabilistic inference from network registration data — not a GPS coordinate — so treat city-level results as approximate with a typical accuracy radius of 25–50 km for residential IPs and potentially much larger for mobile and VPN connections. For a precise physical location, browser Geolocation API with explicit user permission is required.

Why does geolocation show a different city than my actual location?

Large ISPs register IP address blocks centrally from their headquarters or regional hub, meaning customers spread across an entire state or country may all geolocate to one city. Mobile carriers do the same — your mobile IP often resolves to the city where your carrier operates its routing hub, not where you physically are. If you use a VPN, the result reflects the exit server's city entirely.

If your IP's geolocation is consistently wrong, your ISP can update their Regional Internet Registry registration to reflect the correct service area — this eventually propagates to third-party databases over weeks to months. There is no way to correct geolocation through your own DNS or server configuration.

What do the Mobile, Proxy / VPN and Hosting / DC flags mean?

Mobile indicates the IP is assigned to a mobile carrier rather than a fixed broadband provider — location accuracy is typically lower for mobile IPs. Proxy / VPN means the IP is associated with a commercial VPN service, proxy, or Tor exit node — the location shown is the exit server's location, not the user's actual location. Hosting / DC means the IP belongs to a cloud or hosting provider rather than an end-user connection.

These flags are used by fraud detection and access control systems to distinguish genuine user traffic from bots, scrapers, and anonymised connections. A hosting flag on a residential ISP connection would be unusual and worth investigating further with our ASN Lookup and WHOIS Lookup tools.

What is the difference between this tool and What Is My IP?

This tool is focused on looking up geolocation for any IP you specify — you enter the IP you want to investigate, and it returns that IP's location data. It is designed for investigating specific IPs from server logs, security alerts, or network diagnostics.

What Is My IP automatically detects and shows your own public IP address on every page load — you do not need to enter anything. It also provides your own location and network details. Both tools use the same underlying geolocation data source, but What Is My IP is the faster choice when you want your own details, while this tool is better for researching any specific IP.

Can I look up a hostname or domain name instead of an IP?

Yes — enter any hostname such as github.com or mail.example.com and the tool resolves it to an IPv4 address via DNS before performing the geolocation. The resolved IP is shown alongside the result so you can confirm which address was looked up.

Note that many domains use CDNs or anycast routing where the resolved IP varies by DNS resolver location — the IP you see here is what our resolver returns, which may differ from what a user in another country would see. Use our DNS Lookup to see all the IP addresses a domain resolves to across different record types before geolocating a specific one.

What is the difference between IP geolocation and GPS?

GPS determines location by triangulating signals from satellites and is accurate to within metres on modern devices. IP geolocation infers approximate location from network registration data and is typically accurate only to city or region level, with no ability to determine the precise address or room of a user.

Websites cannot access your GPS coordinates through your IP address alone — that requires explicit browser permission via the Geolocation API, which triggers a visible permission dialog. IP geolocation is used for coarse-grained tasks like currency selection, content localisation, and regional fraud screening, while GPS enables precise navigation and location-aware mobile applications. IP geolocation is passive and does not require any device permission.

What do the latitude and longitude coordinates represent?

The coordinates shown are an approximate centre point for the identified location — typically the geometric centre of the city or region the IP is associated with, not a specific building, street, or neighbourhood. They are displayed on the map to give a visual sense of where the IP's network operator is based geographically.

For city-level estimates the accuracy radius is typically 25–50 km for residential IPs and can be much larger for mobile or hosting IPs. Do not use these coordinates to infer a precise physical address — they are a network-level estimate derived from registration data, not a real-time location fix. To investigate the network behind the coordinates, use the ASN Lookup link in the Network Information panel.

Is my query stored or logged?

No. The IP address you enter is used only to fetch a live result from our geolocation API and is not written to any database, not linked to a user profile, and not shared with third parties beyond the API call itself. No account is required, and every lookup runs fresh on submission with no cached result tied to your query.

Standard web server access logs record the URL of each page request — which includes the IP you looked up as a query parameter — for security and uptime monitoring purposes. These logs are periodically rotated and are not used for user tracking, profiling or advertising. For a complete IP investigation, combine this with our Reverse DNS, WHOIS Lookup and ASN Lookup — all free and real-time with no sign-up.