The IPv4 and IPv6 checks ask ipify, a public IP echo service, over each protocol. If IPv6 shows as missing, your network or VPN only uses IPv4.
WebRTC lets web pages discover your network addresses for video calls. With a VPN on, it should only reveal the VPN's address. The test asks two public STUN servers (Google and Cloudflare) which address they see.
Network owner and location come from RIPEstat public routing and geolocation data. Location is approximate: often the city of your ISP's equipment, not your home.
How to use
Open the page
Your public IP appears in the banner as soon as the page loads, with nothing to type. Use the Copy button next to it to paste the address into a support ticket or an allowlist.
Check IPv4, IPv6 and network details
The rows under the banner show your IPv4 and IPv6 addresses, your provider, AS number, approximate location and hostname. If IPv6 says No IPv6 connection, your network or VPN only uses IPv4.
Test your VPN or look up another IP
With a VPN on, run the WebRTC leak test and check that the banner shows the VPN's address. To check any other address, type it into Look up any IP address.
Why What Is My IP Address
- Shows the public IP address websites see, with IPv4 and IPv6 checked separately.
- ISP or network owner, AS number, approximate city and country, and reverse DNS hostname.
- WebRTC leak test and a hosting-network flag help you check that a VPN hides your real address.
- Look up any other IP address too. Nothing on this page is saved.
Public vs private IP addresses
Every device on your network has a private address that only your router knows about. When traffic leaves the network, the router swaps it for your one public address using NAT. That public address is what this page and every website sees. If your router's own WAN address falls in the 100.64 range, your provider uses carrier-grade NAT and you share a public IP with other customers.
The ranges below are reserved for private use, so seeing one of them means you are looking at a local address, not your public IP.
| Range | Type | Where you see it |
|---|---|---|
| 10.0.0.0 to 10.255.255.255 | Private IPv4 | Office networks, some home routers |
| 172.16.0.0 to 172.31.255.255 | Private IPv4 | Office networks, Docker |
| 192.168.0.0 to 192.168.255.255 | Private IPv4 | Most home routers |
| 100.64.0.0 to 100.127.255.255 | Shared (carrier-grade NAT) | Mobile and some broadband providers |
| fc00::/7 | Private IPv6 (unique local) | Internal IPv6 networks |
| fe80::/10 | Link-local IPv6 | Every IPv6 device, local link only |
How the VPN checks on this page work
A VPN should replace your home address everywhere a website can see it. This page looks at the three places where the real address most often slips through, and says plainly which ones it can and cannot test.
- The address in the banner: with the VPN on, it should belong to the VPN provider. The network owner row and the hosting-network flag make that easy to confirm.
- IPv4 and IPv6 separately: some VPNs only tunnel IPv4, so an IPv6 row that still shows your home provider is a leak.
- WebRTC: the leak test shows the address your browser would reveal to a video call or any page that asks. It should match the VPN's address.
- Timezone: sites can compare your browser's timezone with the country of your IP. A mismatch does not leak your address, but it hints that a VPN is in use.
- DNS leaks are not tested here, because detecting them needs a DNS server that logs which resolver asked. Use your VPN provider's own leak test for that.