What's My IP & Location?

The page runs a client-side HTTPS fetch to the free ipwho.is API from your browser. Whatever network path is active — direct, VPN, or SOCKS5 — the API sees the outbound source IP and returns it along with ASN, ISP, country, region, city, postal code and timezone. The lookup runs entirely from your browser; Best SOCKS5 servers never see the result.

Three common causes: (1) the proxy is set at the system level but this browser is bypassing it, (2) the proxy is configured for a different browser profile, (3) DNS is being resolved before the SOCKS tunnel is used. Configure the SOCKS5 proxy in the same browser that is showing this tool, reload, and confirm the ASN row now shows your provider instead of your ISP.

Yes. There is no signup, no email capture, no API key, and no per-user quota. The upstream ipwho.is service has a fair-use limit of roughly one request per second per IP — well above what a human tester will hit.

Yes. If your connection prefers IPv6 (native ISP or IPv6-enabled proxy), the tool displays your IPv6 address and full IPv6 geo/ASN data. If you want to force one version, disable the other in your OS network settings and reload.

Country accuracy is near-perfect (>99%). City-level accuracy is 60–80% for residential IPs and lower for datacenter IPs, because databases lag proxy provider rotations. The ASN and ISP fields are always authoritative — trust them over the city when they disagree.

The result is snapshot-encoded into the page URL as a compressed query parameter. Click the Share button in the tool header and send the URL — the recipient sees the same IP, ASN and location data you saw, even after your proxy rotates.

No. The IP lookup goes directly from your browser to ipwho.is over HTTPS. Best SOCKS5 receives no request during the lookup and stores nothing.

Yes — check the ISP and ASN fields. Residential exits return consumer ISPs (Comcast AS7922, Deutsche Telekom AS3320, Vodafone AS15169). Datacenter exits return cloud provider ASNs (AWS AS16509, DigitalOcean AS14061, OVH AS16276). ISP-static proxies fall in between: datacenter ASN but consumer-labeled ranges.

For sticky sessions, once at session start and once mid-way is enough. For per-request rotation, spot-check every 20–30 minutes during a job to confirm the pool is actually rotating and not returning the same exit to your account. The Share URL lets you diff two snapshots side by side.

An accurate proxy exit is necessary but not sufficient. Modern anti-bot systems fingerprint headers, TLS, canvas and behavior on top of the IP. Confirm the exit here first, then use the Headers Inspector and WebRTC Leak Test to rule out the other three vectors.

Not directly — this tool only shows the outbound source IP. Combine it with a dedicated DNS leak site (e.g. dnsleaktest.com) opened through the same proxy: if the DNS servers listed are your ISP's resolvers instead of the proxy region's, you have a DNS leak that SOCKS5 alone cannot fix.

Every page load and every manual refresh performs a fresh ipwho.is request. Nothing is cached locally beyond the last-run snapshot embedded in the Share URL, so you always see your current exit — not a stale reading from a previous session.

ipwho.is returns is_eu=true when the exit country is inside the EU/EEA. Scraping through EU exits can subject the operation to GDPR obligations even if the target site is outside the EU. Use non-EU exits when your legal review requires it.

Carrier-grade NAT (CGNAT) recycles mobile IPs across thousands of subscribers, and some ranges are also leased for enterprise VPN gateways. Reputation databases sometimes flag entire mobile carrier blocks as hosting. This is a false positive for consumer mobile traffic — treat ASN + carrier name as the source of truth.