IP Geolocation Lookup

City-level accuracy ranges from roughly 50% to 80% depending on the country, ISP, and whether the IP is allocated to a residential or datacenter range. In North America and Western Europe, city-level accuracy is typically 60–80% due to denser RIR allocation granularity. In many regions, the recorded location corresponds to the ISP's central office, aggregation point, or POP rather than the subscriber's premises. The database is updated weekly with the latest IP2Location DB11 LITE dataset.

Common causes: VPN and proxy egress points are geographically unrelated to the client. Mobile carriers use carrier-grade NAT (CGNAT) pools whose IP blocks may be registered in a different city. Large ISPs allocate blocks centrally but serve multiple POPs. Satellite internet (Starlink, etc.) uses ground-station IPs that may not match the subscriber's coordinates. Anycast prefixes (CDN, DNS) announce from multiple geographic locations simultaneously.

An Autonomous System (AS) is a network or group of networks governed by a single routing policy on the BGP-speaking internet. The ASN is the numeric tag attached to BGP announcements. An ISP is the business entity that sells internet access. A single ISP may operate multiple ASNs (e.g., for transit vs. peering), and a single ASN may serve multiple ISPs or be an internal network without public-facing services. ASN data is sourced from iptoasn.com, a free database derived from BGP table dumps and RIR allocations.

An IP address reveals the approximate geographic region and the ISP that owns it, but rarely the exact street address. Websites, CDNs, and ad networks use IP geolocation for regional content delivery, analytics, fraud scoring, and rate limiting. Using a VPN, SOCKS proxy, or TOR exit node replaces the client's real IP with a different one. Private IP ranges (RFC 1918, RFC 4193) are not forwarded by routers on the public internet and are only meaningful within a local network.

RFCs (Request for Comments) are standards-track and informational documents published by the IETF. The RFCs relevant to IP addressing define the structure, allocation, and special-use semantics of address space. Key references: RFC 791 (IPv4 protocol), RFC 8200 (IPv6 protocol), RFC 1918 (private IPv4 ranges: 10/8, 172.16/12, 192.168/16), RFC 4193 (unique local IPv6, fd00::/8), RFC 1122 (localhost 127/8), RFC 3927 (link-local 169.254/16), RFC 6598 (shared CGNAT space 100.64/10), RFC 5737 (documentation prefixes), RFC 5771 (IPv4 multicast 224/4), RFC 4291 (IPv6 addressing architecture), RFC 2375 (IPv6 multicast), and RFC 6890 (special-purpose address registry).

The tool uses the IP2Proxy PX12 Lite database, which classifies IP addresses by usage type derived from threat intelligence feeds and routing data. Classification codes: PUB (public proxy), VPN (VPN tunnel endpoint), DCH (hosting or datacenter), TOR (Tor exit relay), SES (search engine crawler), and -- (residential or unclassified). A fraud score from 0 to 100 is included for risk assessment. This is useful for access control, bot mitigation, and abuse prevention, but should not be used as the sole criterion for blocking traffic.

ASN data is sourced from iptoasn.com, which aggregates BGP table dumps into IP-to-ASN mappings. If a result shows ASN/ISP data as unavailable, the IP may belong to a range not yet announced in BGP, a private range that is not globally routable, a reserved or unassigned prefix, or a newly allocated block that has not propagated. The local database covers approximately 445,000 IPv4 ranges and 118,000 IPv6 ranges. Private and special-purpose addresses (RFC 1918, RFC 4193, RFC 1122, etc.) are excluded from ASN registration by design.