What you are checking
When you connect to a VPN, websites usually see the public IP address of the VPN exit point instead of the public IP address of your local home or Wi-Fi network.
Checking your IP address before and after connecting is a simple way to confirm that web traffic is going through the VPN path.
Basic process
Before connecting to the VPN, open a reputable IP-check website and write down the public IP address shown.
Connect to the VPN. Refresh the IP-check page or open a second IP-check site. If the public IP changed, your browser traffic is likely exiting through the VPN service.
Common confusion
Some apps may cache connections. Some browsers may keep old tabs open. DNS and location databases may show approximate or stale location data. Do not assume every map or location result is exact.
A changed public IP is a practical first check, not a full packet-level audit.
ZBEVPN independent IP test evidence
See a real before-and-after ZBEVPN test using IPLeak and BrowserLeaks. The connected test independently observed ZBEVPN IPv4 and IPv6 egress, and BrowserLeaks reported no WebRTC public-IP leak.
See the same test performed on ZBEVPN
ZBEVPN publishes a real before-and-after public-IP test. Independent services observed the VPN-server IPv4 and IPv6 addresses after connection and BrowserLeaks reported no WebRTC public-IP leak.