~/ geoip-lookup
IP Geolocation Lookup
Resolve city, region, country, ASN and timezone for any external IPv4 or IPv6 address. Useful for triaging abuse reports, validating CDN edge selection, debugging GeoDNS, or auditing access logs.
// status
[coming soon] Lookup for arbitrary IPs is a registered-user feature, currently in development.
Your own public IP geolocation is already available on the homepage and via /api/ip.
What the tool will return
- Location: city, region, country, continent, postal code
- Network: ASN and AS organization
- Time: timezone (IANA), UTC offset
- Classification: public / private (RFC 1918) / CGNAT (RFC 6598) / loopback / link-local / multicast / reserved
- Reverse DNS: PTR record where available
Accuracy and limitations
IP geolocation is a probabilistic mapping built from registry data (RIR allocations, ASN announcements), commercial GeoIP databases and BGP routing tables. City-level accuracy is typically 50–80% for residential ISPs and significantly worse for mobile networks (where IPs are allocated regionally and routed centrally), satellite connections, VPNs, Tor exits and cloud providers. Country-level accuracy is usually above 99%. Treat geolocation as a hint, not a fact — and never use it as a security control.
Common use cases
Sysadmins use IP geolocation to investigate suspicious login attempts, score traffic in WAF rules, verify content licensing, debug CDN POP selection, attribute revenue to countries in B2C analytics, or quickly understand the origin of a DDoS source list. Pair the geo data with the ASN and you can often see whether the traffic is coming from a consumer ISP, a hosting provider or a known cloud range.