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.
The address shown here is your public IP — the one your router presents to the internet, assigned by your internet provider. It is shared by every device on your network, because network address translation multiplexes them all behind a single public address and keeps track of which internal device each connection belongs to.
Your device's own address is different and private, typically starting 192.168., 10. or 172.16. through 172.31.. Those ranges are reserved by RFC 1918 and are not routable on the public internet, which is why every home network can use 192.168.1.1 without conflict. A website cannot see your private address.
Most residential connections use a dynamic public address that changes periodically — on router restart, on lease renewal, or at the provider's discretion. A static address usually costs extra and is mainly needed for hosting services or for allowlisting at a fixed address.
Geolocation from an IP address works by looking it up in a database mapping ranges to locations, populated from registry records and provider data. Accuracy at country level is high, typically well above 95 percent. City level is considerably less reliable, and the precise coordinates some services display are usually the centroid of a region rather than a real position — which has caused genuine harm where a default centroid pointed at a specific house.
It does not reveal a street address, and no website can obtain one from an IP alone. Your provider holds the subscriber record linking the address to an account, and that requires legal process to obtain. Mobile connections, satellite links and providers using carrier-grade NAT are frequently located hundreds of kilometres from the user.
What it does reveal is your provider, your approximate region, and a stable-enough identifier to correlate visits. Combined with browser fingerprinting — screen size, fonts, time zone, hardware details — it contributes to tracking that works without cookies. A VPN replaces the visible address with the VPN server's, which moves the trust rather than removing it: the VPN operator sees what your provider otherwise would.
IPv4 provides about 4.3 billion addresses and ran out — the central pool was exhausted in 2011, and regional registries followed. NAT is the workaround that kept it functioning, at the cost of making inbound connections awkward and complicating peer-to-peer protocols.
IPv6 uses 128-bit addresses, giving roughly 3.4 × 10³⁸ of them, which is enough to assign a globally unique address to every device without translation. Adoption is now substantial, and many connections run dual-stack, holding both an IPv4 and an IPv6 address simultaneously — which is why you may see two addresses here.
IPv6 raised a privacy question, since early designs derived the address from the hardware MAC address, making a device trackable across networks. Privacy extensions, now standard, generate temporary randomised addresses that rotate periodically, which resolves it. If you are working out network boundaries and prefix lengths, the subnet calculator handles both protocols.
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.
No. Geolocation is accurate to country level and unreliable at city level, and displayed coordinates are often a regional centroid rather than a real position. Only your provider holds the subscriber record, which requires legal process.
Your connection is probably dual-stack, holding both an IPv4 and an IPv6 address. Sites may report either depending on which protocol the connection used.