Response fields
IP, country and code, region, city, postal code, coordinates, timezone, ISP, organization, ASN, plus proxy, hosting and mobile flags where a source provides them. Sources differ in coverage, and missing fields show as “—”.
Geo · ASN · Proxy
Enter an IP or domain to get country, city, coordinates, timezone and network ownership. To validate a proxy, switch to the proxy test and see the handshake result and exit location.
Leave it empty to look up your current IP.
Rotation is automatic, or choose one source.
Switch to the proxy test for handshake and exit.
IP, country and code, region, city, postal code, coordinates, timezone, ISP, organization, ASN, plus proxy, hosting and mobile flags where a source provides them. Sources differ in coverage, and missing fields show as “—”.
The SOCKS5 test follows RFC 1928 and RFC 1929: method negotiation, username/password authentication, then CONNECT. The HTTP test sends a CONNECT request and checks for a 2xx or 407 response. After a successful handshake an IP echo service is reached through the tunnel to confirm the exit.
The details to know before you choose.
No. They are a database estimate of the network location, sometimes an ISP facility or city center, rather than the physical address of a user or device.
IP geolocation is usually city- or region-level; coordinates are an approximate center, not a device's real location.
Results for the same IP are cached for a few hours to spare public sources. A “cached” badge marks such results.
Use the ASN and organization name; some sources also flag hosting networks, though any database can be wrong.
From GEOSK5's checker server, so latency includes the distance between that server and your proxy.
Private and reserved ranges are not publicly routed and have no geolocation.