Private addresses work inside local networks
Home routers commonly assign private IPv4 addresses from ranges reserved for internal networks. These addresses can be reused by millions of separate networks and are not directly routed across the public internet.
The public address represents an internet-facing path
Websites normally see a public address associated with the path carrying your request. Without a VPN this may belong to your ISP or carrier. With a VPN it will usually belong to the VPN exit infrastructure for traffic covered by the tunnel.
Mobile carriers can add another translation layer
Carriers often use carrier-grade NAT, where many customers share public IPv4 infrastructure. IPv6 can also change the picture because devices may have globally scoped addresses. This is why a simple “one device, one IP” model is often wrong.
Use the address type when troubleshooting
If a test shows 192.168.x.x, that is not evidence that your home public address leaked. If it shows a public address, compare ownership and behavior before and after connecting. Test IPv4 and IPv6 where relevant because routing can differ.
Sources & further reading
This guide is general educational material. Platform behavior, provider policies, and network conditions can change. Check current documentation before relying on a specific configuration.
Report an error or suggest a clarification ↗