Your public IP address is the network address a website typically sees when you connect. It may be assigned to your home connection, your mobile provider or the VPN server you chose.
Clearly labeled evidence • No invented live measurements
ISP-facing public IP
Exit-server public IP
A public IP address can indicate your internet provider and an approximate network location. It does not by itself reveal your exact street address. This page explains the distinction and how to check for IP changes; the actual lookup widget must be validated before launch.
Read the method, check the limits, then use your own connection to confirm the result.
This read-only check runs only when you press the button. We do not save your IP in WordPress.
This is not a DNS or WebRTC leak test. If a reverse proxy is in use, the server may observe a proxy address rather than your direct IP.
A website normally sees the public address used for the connection reaching it. A VPN may change that visible address, but an address alone does not prove that all traffic is protected or that location estimates are accurate.
Visible to contacted services
May take different network paths
Compare before and after connection
| Observation | What it usually means | What not to conclude |
|---|---|---|
| Public address changes when the VPN connects | The visible network exit likely changed for that request | Not proof that DNS, WebRTC or all apps use the tunnel |
| Public address stays the same | The route may be unchanged or the check may be incomplete | Not enough alone to establish a leak diagnosis |
| Approximate country or city looks wrong | IP geolocation records may be outdated or coarse | Not a reliable indicator of physical GPS location |
| IPv4 changes but IPv6 does not | Families may follow different paths | Requires a deliberate IPv6 test and context |
Live IP lookup: Not installed in this draft. This page does not inspect, collect or display your visitor IP address. See the privacy tools hub for how checks should be performed responsibly.
A private address such as 192.168.x.x or 10.x.x.x is typically used inside a local network. Your public-facing address is what remote services use to send responses back toward your connection. Routers and carriers may share one public IPv4 address across several devices.
IPv6 changes the addressing picture, but it does not remove privacy considerations. Your device may have multiple relevant addresses depending on interface and network configuration.
Public address is not your Wi-Fi router’s internal address
IPv4 and IPv6 are different formats
Carrier-grade NAT may share an address
Most websites will see the public address of the VPN exit server for traffic routed through the tunnel. But split tunneling, browser features, unusual network setups or leaks can complicate that picture.
Compare the apparent IP before and after connecting. Then use a dedicated privacy tools guide for DNS and WebRTC leak checks instead of relying on a single IP readout.
Record your baseline IP privately
Connect to the chosen VPN location
Check IPv4, IPv6 and DNS behavior separately
IP geolocation databases make estimates, not precise GPS measurements. Results can show the wrong city, especially on mobile and business networks or when an address block changes hands.
An IP address is still useful metadata. Treat it as personal network information, avoid copying it into public screenshots and remember that services can identify you through logins and cookies too.
Expect approximate location
Treat displayed addresses as private information
Use location data cautiously
IP location databases are estimates and may be stale or based on the network operator’s registration.
Not universally. The exit IP changes for routed traffic, but leaks, split tunneling or logged-in accounts can reveal other information.
Not in this draft. The privacy-aware detection component is pending verification on the production proxy setup.
Related pages chosen for the next decision, not for repeating the same search query.
VPN privacy tools explained: check public IP, understand DNS and WebRTC leaks, and learn what a trustworthy leak test requires.
WireGuard vs OpenVPN explained: speed, UDP/TCP, security design, stability and which VPN protocol to choose for your connection.
How to test VPN speed correctly: download, upload, ping, jitter and packet loss. Learn to compare VPN performance against a fair baseline.
When an observed metric is published, its date, route, protocol, sample size and limitations should travel with it. Product claims and editorial judgments are labeled separately.
Independent VPN research and performance context.