Free Tool · No sign-up · Runs in your browser
See exactly what any website sees about you: your public IP and country, whether WebRTC is leaking your real IP, your browser fingerprint, and whether your timezone matches your IP location. The checks are worked out in your browser and their results aren't sent to our app. You can also look up any other IP's country, ASN and ISP.
Checking WebRTC…
Compare your timezone region to your IP country above.
——————Geolocation and ASN data comes from ipwho.is — your browser contacts them directly, so they see both the IP you type and the IP you're connecting from, under their own privacy policy. It never passes through our app.
Every site you visit sees your public IP. It maps to your rough location (country, city, ISP) and ties requests together across sessions. A proxy replaces it with an IP from our pool so the site sees the proxy, not you.
WebRTC is a browser feature for real-time audio/video. It can reveal your real IP even when you're behind a proxy or VPN, because it talks to STUN servers directly. If the IP shown above differs from your proxy's IP, sites can see your real address.
Timezone, languages, screen size, platform, CPU/memory and User-Agent combine into a fingerprint that can identify you even without cookies. A mismatch — e.g. a US IP with a Shanghai timezone — is a classic proxy tell.
Residential and mobile proxies route you through real consumer IPs so your exit IP, geo and ASN all look organic. Pair a clean IP with a matching timezone and locale and you stop looking like automation. See residential plans →
Connect through your proxy, then reload this page. The "public IP address" should change to your proxy's IP and the country should match where you set the proxy. If your original IP still shows, the proxy isn't applied to your browser (check system vs. browser-level settings).
WebRTC can expose your real IP directly to a website, bypassing your proxy. If the WebRTC-exposed IP above is your real IP (not the proxy's), you have a leak. Disable WebRTC in your browser, use an extension that blocks it, or use a browser/anti-detect setup that spoofs it. Server-side proxies (set at the OS or scraping-client level) are not affected by browser WebRTC.
Anti-bot systems compare your IP's country to your browser's timezone and locale. A US exit IP with an Asia/Shanghai timezone is a strong bot signal. Match your timezone and language to your proxy's location — anti-detect browsers do this automatically.
Free, yes — and the results are worked out in your browser and never sent to our app. But "runs in your browser" doesn't mean "contacts nobody": your IP is read from Cloudflare's edge (our CDN), the WebRTC test talks to a Google STUN server, this site loads Google Analytics like most sites do, and looking up an IP sends it to ipwho.is. Those third parties see that traffic and handle it under their own privacy policies, not ours.
Residential and 4G mobile proxies use real consumer IPs and are hardest to detect. Static ISP proxies give a fixed residential-looking IP that's fast and stable. Datacenter proxies are cheapest but easiest to flag.