Your public IP, DNS leaks, HTTP headers, browser fingerprint, TLS grade, connection latency — and a personalized guide to fix what's exposed.
Your public IP can reveal your approximate location (usually city-level), your ISP, and your organization if you're on a corporate network. It can be used for geolocation-based content targeting, rate limiting, or — in rare cases — attempts to identify you through your ISP. It cannot be used to directly access your device or files.
Your public IP is assigned by your ISP and is visible to every website you visit — it's the address of your router on the internet. Your local (private) IP (e.g., 192.168.x.x) is assigned by your router and only visible on your home network. Local IPs can be exposed via WebRTC leaks even when using a VPN.
A VPN hides your IP and encrypts traffic between you and the VPN server, but it doesn't make you fully anonymous. Your VPN provider can still see your traffic. Browser fingerprinting, cookies, and logged-in accounts can identify you regardless of IP. WebRTC leaks can also expose your real local IP. Run this audit with your VPN active to check for leaks.
An ASN is a unique identifier assigned to a network that controls a block of IP addresses. Your ISP has an ASN (e.g., AS7922 for Comcast). Major cloud providers like AWS (AS16509), Google Cloud (AS15169), and Cloudflare (AS13335) have their own ASNs. If your IP resolves to a cloud ASN, it signals you're using a VPN or proxy — many streaming services use this to block VPN access.
IP geolocation is approximate and based on databases that ISPs and registries maintain. Accuracy is typically city-level at best, and can be off by tens or hundreds of miles. Mobile carriers often route traffic through regional hubs, so your detected location may show a city where the carrier's data center is, not where you physically are.