IP Location Lookup
Look up the geographic location, ISP, ASN, and timezone of any public IP address.
Looking up IP address...
IP Address
—
—
🏙️
City
—
📍
Region / State
—
🌍
Country
—
🕐
Timezone
—
🌐
ISP / Organization
—
🔢
ASN
—
📐
Latitude
—
📐
Longitude
—
Map will appear here
Full Details
Bulk IP Lookup
| IP Address | City | Country | ISP | ASN |
|---|
What is IP Geolocation?
IP geolocation is the process of determining the physical location associated with an IP address. Every IP address block is registered with a Regional Internet Registry (RIR) and assigned to an organization. By querying geolocation databases that map IP ranges to locations, you can determine the country, region, city, and ISP associated with any public IP address.
IP geolocation is an estimation, not a precise measurement. The location returned is typically where the ISP's network infrastructure is located — which may not match the user's actual physical location, especially for mobile networks, VPNs, or corporate networks with centralized routing.
How to Use This Tool
- Enter a public IP address (IPv4 or IPv6) in the input field, or leave it blank to look up your own IP.
- Click Lookup.
- Results show country, region, city, ISP, ASN, and coordinates.
Information Returned
- Country / Region / City — Geographic location of the IP's registered network block
- ISP (Internet Service Provider) — The organization that owns or operates the IP range
- ASN (Autonomous System Number) — A unique number identifying a network on the internet (e.g., AS15169 = Google)
- Latitude / Longitude — Approximate coordinates, useful for mapping but not precise
- Timezone — The timezone associated with the location
- Proxy / VPN / Tor detection — Whether the IP is a known exit node or hosting provider
Common Use Cases
- Security logging — Enrich server logs with location context for anomaly detection
- Fraud prevention — Flag transactions from unexpected countries or known proxy IP ranges
- Content geo-restriction — Serve region-appropriate content or comply with licensing restrictions
- Network troubleshooting — Verify which ISP or data center an IP belongs to
- OSINT investigations — Gather context about an IP involved in suspicious activity
Frequently Asked Questions
IP geolocation accuracy varies significantly: country-level is ~95–99% accurate, city-level is 50–80% accurate. Common inaccuracies occur because: (1) Mobile networks route traffic through centralized locations far from the user; (2) Corporate VPNs make traffic appear to come from headquarters; (3) ISPs sometimes register IP blocks to a city or region center; (4) Satellite internet (Starlink) may show unexpected locations. The location is where the network infrastructure is registered, not necessarily where the device is.
An Autonomous System (AS) is a collection of IP prefixes under the control of one or more network operators with a common routing policy. Each AS has a unique ASN. BGP (Border Gateway Protocol) uses ASNs to exchange routing information between ASes. Examples: AS15169 (Google), AS16509 (Amazon AWS), AS13335 (Cloudflare). Knowing the ASN of an IP tells you exactly which organization controls that IP range.
VPNs replace your real IP with the VPN server's IP, so geolocation shows the VPN server's location instead of yours. However: (1) WebRTC leaks can expose your real IP in browsers; (2) DNS leaks can reveal your real ISP; (3) Known VPN IP ranges are flagged by many geolocation services; (4) Your VPN provider knows your real IP. For strong anonymity, Tor is more robust (though slower), but even Tor has known weaknesses against traffic correlation attacks.
IPv4 geolocation databases are mature and well-populated — most IPv4 ranges have accurate location data. IPv6 geolocation is less precise because IPv6 adoption is newer and prefix allocations are handled differently. ISPs receive large IPv6 blocks (/32 or larger) and sub-allocate them, making it harder to map individual ranges to specific locations. IPv6 geolocation accuracy is improving but generally less reliable than IPv4 at city level.
No. Private IP addresses (RFC 1918:
10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) are not routed on the public internet and have no geolocation data. They're used inside local networks. Similarly, loopback (127.0.0.1), link-local (169.254.x.x), and other reserved ranges can't be geolocated. Only public (globally routable) IP addresses can be looked up.