IP Lookup / My IP

About this tool

IP Lookup retrieves geolocation and network metadata for any IPv4 address - or detects your own public IP automatically. The metadata includes country, region, city, ISP name, ASN (Autonomous System Number), and organization. This is useful for network troubleshooting, incident response, firewall allowlist verification, and quickly identifying who owns a given address block.

Real example

Input: 8.8.8.8 (Google's public DNS resolver)

Expected result fields:
ip: 8.8.8.8
org: AS15169 Google LLC
city: Mountain View, region: California
country: US, postal: 94043
timezone: America/Los_Angeles

The ASN (AS15169) is the key identifier - it tells you which organization controls this IP block at a routing level, regardless of the imprecise geolocation city data.

Common use cases

• Firewall allowlist verification: If your application only accepts traffic from specific IPs, use "Find My IP" to confirm your current egress address matches the allowlisted entry before debugging a connection failure.
• Incident response and abuse investigation: When reviewing logs during a security incident, look up the source IPs to identify the hosting provider or ISP. Combine with WHOIS Lookup to find abuse contact information.
• CDN and proxy detection: Cloud providers (AWS, Cloudflare, GCP) have well-known ASNs. If traffic from an unexpected ASN appears in your logs, this lookup quickly identifies the source organization.
• Geolocation debugging: If your application serves region-specific content and a user reports seeing the wrong region, look up their IP to see what metadata your geolocation library would return for their address.

How it works

"Find My IP" calls the ipify.org API (https://api.ipify.orgformat=json) to detect the public IP of the browser's current network connection. The IP lookup calls ipapi.co to fetch metadata associated with any IPv4 address. Both calls are made directly from your browser - the results are displayed in the output panel and are not stored by this site.

Common mistakes

• Expecting precise city-level geolocation: IP geolocation is a best-effort estimate based on registration data and network routing. The city shown may be the ISP's headquarters or a major routing hub, not the actual device location. Accuracy varies significantly by provider and region.
• Confusing egress IP with device IP: When behind a NAT router or corporate proxy, your device's private IP (192.168.x.x) is not your public IP. "Find My IP" returns your public egress address - the IP seen by external servers.
• Treating VPN results as real location: If you are on a VPN, the lookup returns the VPN exit node's location and ASN, not your actual location or ISP.

FAQ

What is an ASN
An Autonomous System Number (ASN) identifies a network operated by a single organization under a unified routing policy. Major cloud providers, ISPs, and CDNs each have one or more ASNs. AS15169 is Google, AS16509 is Amazon AWS, AS13335 is Cloudflare.

Why does geolocation show the wrong city
IP geolocation databases map IPs to locations based on ARIN/RIPE registration data and routing analysis. The result is often the ISP's data center city, not the actual user location. For precise location, GPS or user-provided data is needed.

Does this tool store my IP
No. The lookup is performed by your browser and the result is displayed locally. This site does not log or store IP addresses.

Can I look up IPv6 addresses
The tool currently supports IPv4 only. For IPv6 metadata, use a dedicated WHOIS or RDAP lookup via WHOIS Lookup.

What IP geolocation data tells you (and what it doesn't)

IP geolocation is fundamentally an inference, not a measurement. No database knows where a device physically sits — what they know is where an IP address is registered, which organization controls the address block, and from routing data, roughly where that block is announced. The precision varies enormously by context.

Country is usually accurate. Regional Internet Registries (ARIN, RIPE, APNIC, LACNIC, AFRINIC) record the country of the organization that holds the IP block. For most non-VPN, non-proxy traffic, country-level geolocation is reliable enough for legal compliance purposes (GDPR regional checks, content licensing).

City is often wrong. City-level data is derived from routing topology and ISP infrastructure locations, not actual user locations. When a user in Seattle connects through a Comcast backbone that routes through Denver, the lookup may return Denver. Mobile users on carrier networks often resolve to a city where the carrier has a major POP (point of presence), not where the phone is.

VPNs and proxies completely break geolocation. A lookup on a VPN exit node returns the data center location, not the user location. Tor exit nodes return data from wherever the exit node is hosted. This is by design — geolocation is a privacy signal that users have legitimate reasons to obscure.

ASN lookup: what autonomous system numbers reveal

The ASN (Autonomous System Number) identifies the network organization that controls the IP address block. This is often more useful than geolocation for security and infrastructure investigations:

Identifying hosting providers: AS16509 is Amazon AWS. AS14618 is Amazon (different block). AS15169 is Google. AS13335 is Cloudflare. AS8075 is Microsoft Azure. When an IP in a log resolves to one of these ASNs, the traffic originated from a cloud-hosted service or instance, not a residential or office connection.

Spotting datacenter traffic: IPs registered to hosting ASNs making requests that should come from real users are a common bot signal. Legitimate human users almost never have datacenter ASNs — they have residential ISP or mobile carrier ASNs.

Incident investigation: During an incident, knowing whether suspicious IPs belong to a single ASN (coordinated attack from one provider) or many ASNs (distributed botnet) guides response strategy. A single ASN can be rate-limited or blocked at the edge; a distributed source requires different mitigation.

For domain-level investigation alongside IP lookup, see WHOIS Lookup. To resolve a hostname to an IP before looking it up, use Hostname to IP. For subnet context around a flagged IP, see CIDR IP Converter.