What's My IP Address?

When you connect to the internet, your ISP assigns you a public IP address that every website you visit can see. That address tells servers where to send their responses, but it also reveals your approximate location, your ISP, and the autonomous system you are routing through. This WhatIP tool shows you exactly what websites see when you connect: your IPv4 address, your IPv6 address if your network supports it, the country and city your IP geolocates to, and the network operator behind the address. Knowing your public IP is the starting point for setting up a home server, allowing a friend into a game session, troubleshooting why a website blocked you, or simply confirming that your VPN is actually changing your visible address. We use public lookup endpoints, and the result is read only by your browser. Your IP is not stored or logged on our side, so you can refresh as often as you like to watch a dynamic address change or to verify a new connection.

How to Use This Tool

1. Open the page. WhatIP automatically detects your public IP address and displays it at the top, usually within a second or two, with no button to press.
2. Read your IPv4 address, the familiar four-number format such as 203.0.113.42. If your network supports IPv6, a longer hexadecimal address appears below it.
3. Check the geolocation panel for the country, region, and city that your IP maps to, plus the ISP or hosting provider that owns the address.
4. Note the ASN (autonomous system number), which names the network operator carrying your traffic and tells you whether you are on a home ISP, a mobile carrier, or a corporate network.
5. Copy any value with one click if you need to paste it into a firewall rule, a support ticket, or a game server allowlist.
6. To confirm a VPN or proxy is working, connect it and reload the page. The displayed IP, country, and ISP should all change to the VPN exit point.
7. Refresh at any time to recheck. Because nothing is stored, each load reflects your live connection, which makes it easy to watch a dynamic address change after a router reboot.

A Real-World Example

Maya runs a small Minecraft server on a spare computer in her apartment so her cousins can join after school. Her cousins keep getting a connection error, and she is not sure whether the problem is her router, her ISP, or the address she gave them. She opens WhatIP and sees her public IPv4 address listed as 198.51.100.77, with the location pinned to her city and her ISP named clearly. That tells her the address she handed out last week, 198.51.100.20, is stale: her ISP hands out dynamic addresses, and hers changed after a router reboot two days ago.

She copies the current address and sends it to her cousins, but the error continues. Looking again, she notices the page also reports an IPv6 address while her cousins are on an older IPv4-only network. She realizes her port forward only covers IPv4, so she checks her router and confirms the forward still points at the right internal device. Maya also remembers a friend mentioned that some game guides recommend a static address, so she opens her ISP account page in another tab to see whether a static IP is an option for her plan. It is not included, but the account page does offer a dynamic DNS hostname she can attach to her changing address.

After updating the address her cousins use, confirming the port forward, and noting the dynamic DNS option for later, the connection works. The whole diagnosis took five minutes, and the key insight was simply seeing, in plain language, what the rest of the internet currently sees when it looks at her home connection. Next time the address changes, she will set up the dynamic DNS hostname so she never has to text a new number again.

Tips & Best Practices

• If your IP changes often, your ISP is using dynamic addressing. Ask about a static IP, or use a dynamic DNS service so a fixed hostname always points at your current address.
• A location that looks wrong is normal. Geolocation is an estimate, and mobile or VPN connections often show a distant gateway rather than your true spot.
• Never treat your public IP as a secret password. Many devices behind your router share it, and it is visible to every site you visit.
• Distinguish your public IP from the private 192.168.x.x or 10.x.x.x address your router hands to each device at home. Port forwarding and remote access rely on the public one.
• To hide your real IP, use a trusted VPN, then reload WhatIP to confirm the exit address and country actually changed before you rely on it.