Your public IP, plus the device details sites can see — browser, OS, screen resolution and time zone — all on one clean page.
📍 Location is estimated from your IP address (usually city-level, sometimes off) — it's what any website can see, not your GPS position.
Checks whether your browser exposes an IP address through WebRTC — a known way VPNs can leak your real address.
🔒 Device details are read locally. Only the IP check contacts a public echo API — nothing is stored.
Setting up port forwarding, whitelisting an office IP, or telling IT "my IP is…" — grab it with one click.
Connected to your VPN? Refresh this page — if the IP still shows your real location's address, the VPN isn't working.
Browser, OS, resolution and pixel ratio — exactly the details a developer asks for, ready to copy.
IPv4 (like 203.0.113.7) is the classic format most services still use. IPv6 is the newer, longer format. Many connections have both; if a site asks for "your IP", IPv4 is usually what they mean.
No — an IP maps roughly to your ISP and city area, not your street. Only your ISP can link an IP to a customer, and that requires legal process.
Geolocation databases map IPs to where the ISP registered them, which can be a different city. It's an estimate, not GPS.
WebRTC (used for video calls and P2P features) can reveal IP addresses directly to a webpage, bypassing a VPN in some setups. Run the WebRTC leak test above — if it finds a public IP different from your VPN's, or your real local network address, that's a leak worth fixing in your browser or VPN settings.