Methodology and Limitations
We want the tools to be useful and honest. That means explaining how each result is produced, what is measured locally, and where uncertainty remains.
How IP detection works
Your public IP is read from the request that reaches the server. Depending on the hosting layer, the app may use trusted headers such as x-forwarded-for, x-real-ip, or cf-connecting-ip.
How browser data is read
Browser information such as language, screen size, timezone, and cookie support is read locally in the browser with standard Web APIs. It is used only to show the result on the page.
How WebRTC testing works
WebRTC can expose local or public network addresses through ICE candidates. We use that behavior to check for potential leaks and compare any exposed addresses against the public IP already detected by the server.
Accuracy limits
- IP geolocation is approximate and may point to the ISP's infrastructure rather than your actual location.
- VPN, proxy, and Tor detection are based on signals and provider data, not perfect certainty.
- WebRTC behavior varies by browser, platform, and extension configuration.
- Local browser details are accurate for the current device, but they do not identify who you are.
What we store
The site does not need to permanently store your browser diagnostics to display them. If a configured third-party provider is used for IP enrichment, it receives the queried IP address for the lookup.
Where to go next
Try the What Is My IP tool, then review the privacy policy if you want the implementation details in plain language.