OSINT Free · no signup

IP Geolocation Lookup

Look up the geographic location, ISP, and ASN information of any IP address or domain.

Enter a domain or IP address and the IP Geolocation Lookup resolves it to a physical location — country, region, city, and coordinates — along with the ISP, organization, ASN, and timezone behind it. It answers 'where is this server, and who runs the network?' in one query, drawing on IP-to-location databases. Great for verifying a CDN edge, investigating a suspicious IP, or debugging geo-targeting, with the caveat that IP location is an estimate, not GPS.

Updated Krawly Editorial TeamIn-house engineers, writers & reviewers

Explore More Free Tools

Discover 150+ free tools for web scraping, SEO analysis, OSINT, and more. 30 free uses every day — no signup required.

150+ Free Tools No Signup Required JSON / CSV / Excel 30 Uses / Day
Quick answer

Enter a domain or IP address and the IP Geolocation Lookup resolves it to a physical location — country, region, city, and coordinates — along with the ISP, organization, ASN, and timezone behind it. It answers 'where is this server, and who runs the network?' in one query, drawing on IP-to-location databases. Great for verifying a CDN edge, investigating a suspicious IP, or debugging geo-targeting, with the caveat that IP location is an estimate, not GPS.

What is IP Geolocation Lookup?

The IP Geolocation Lookup resolves any domain or IP address to its estimated physical location and network ownership. It returns the country, region/state, city, and latitude/longitude, plus the Internet Service Provider, hosting organization, Autonomous System Number (ASN), and local timezone. The data comes from IP-to-location databases that map address blocks to registration and infrastructure records. It's a staple for OSINT investigations, server-location verification, fraud checks, and debugging geographic content delivery — while keeping in mind that IP geolocation reflects where a network is registered or routed, which can differ from a user's true position.

How to use IP Geolocation Lookup

  1. 1

    Enter a domain or IP

    Paste an IPv4/IPv6 address, or a domain — the tool will resolve the domain to its IP first, then geolocate that IP. For a domain behind a CDN, remember you're locating the edge server, not the origin.

  2. 2

    Read the location fields

    Country is near-certain; city is a best guess. Use the country and region to confirm a server is where you expect (for compliance or CDN checks), and treat city-level results as approximate.

  3. 3

    Check the ISP and ASN

    The ISP/organization and ASN tell you who actually operates the network. Seeing 'Cloudflare' or 'Amazon' here means the IP belongs to a CDN or cloud provider — often more useful than the geographic city.

  4. 4

    Use the timezone and coordinates

    The timezone helps you reason about when a server or user is active; the coordinates let you plot the location on a map for investigations or visualizing infrastructure spread.

Try it when you need to…

  • Try it when a login or transaction looks suspicious and you want to see what country and network the IP belongs to
  • Try it when you're verifying that your CDN is serving users from a nearby edge rather than a distant datacenter
  • Try it when regional content or pricing is showing wrong and you need to confirm what location an IP resolves to

Use cases

  • Server-location verification — confirm your site's servers or CDN edges are in the expected region
  • OSINT investigation — map the network and rough location behind a suspicious IP or domain
  • Fraud detection — flag logins or orders coming from unexpected countries or known hosting ranges
  • Geo-blocking and geo-targeting debug — understand why users see the wrong regional content
  • CDN verification — confirm requests are being served from the nearest edge node

Key features

Country, region, and city-level location estimates
Latitude/longitude coordinates for mapping
ISP and hosting organization identification
ASN (Autonomous System Number) of the operating network
Local timezone of the resolved IP

Tips & best practices

IP geolocation is not GPS. Country-level accuracy is around 99%, but city-level accuracy is typically only 55-80% and can be off by hundreds of kilometers — treat the city as a hint, not a fact.

A VPN, proxy, or Tor exit node shows the location of that intermediary, not the real user. If the ISP field names a known VPN or hosting provider, the geographic result reflects the VPN's datacenter, not the person.

For a domain on a CDN like Cloudflare, Fastly, or Akamai, the IP you geolocate is the nearest edge server — which is why the same domain can appear in different cities depending on where you query from. It tells you nothing about the origin server's location.

Mobile IPs are especially unreliable. Carriers route large regions through a handful of gateways, so a phone in one city can geolocate to another city or even a different state entirely.

Frequently asked questions

Country-level accuracy is very high, around 99%. City-level is much rougher — typically 55-80% and sometimes wrong by a wide margin. IP geolocation infers location from network registration and routing data, not from GPS, so treat city and coordinates as approximations.

When someone uses a VPN, proxy, or Tor, their traffic exits through the provider's server. Geolocation sees that exit node, so the result reflects the VPN datacenter's location and ISP — not the actual user. The ISP field usually reveals this by naming a hosting or VPN provider.

Both. Enter a domain and the tool resolves it to its IP first, then geolocates that address. Note that for CDN-hosted domains you'll be locating the edge server the domain currently resolves to, not the backend origin.

An Autonomous System Number identifies the network operator that controls a block of IP addresses — an ISP, cloud provider, or large organization. It's often more informative than the city: seeing 'AS13335 Cloudflare' immediately tells you the IP belongs to a CDN, not an end user.

No. At best it narrows to a city or ISP region, and often only to the ISP's routing hub. It cannot pinpoint a street address or a specific individual — that level of detail is not present in public IP-to-location data.

CDNs use anycast, routing you to the geographically nearest edge server. Depending on where the lookup query originates, the same domain can resolve to different IPs in different cities. This is the CDN working as intended, not an error.