Checks whether your browser is revealing your real IP address through WebRTC, even when you are connected to a VPN. Connect your VPN first, then open this page — if an IP address different from your VPN IP appears in the WebRTC section, your VPN has a leak.
This tool checks for WebRTC IP leaks — a known privacy issue where browsers can reveal your real IP address through the WebRTC API even when a VPN or proxy is active. It works by comparing the IP address visible to external servers (via HTTP) with the IP addresses your browser discloses through WebRTC. If they differ, the VPN is not fully protecting you. Unlike most Alvea Hubs tools, this one requires a network connection to perform the IP lookup.
WebRTC can reveal your real IP address directly to websites, bypassing your VPN or proxy tunnel. This means your real IP can be exposed even when a VPN is active.
Connect your VPN, open this tool. If the WebRTC section shows an IP different from your VPN IP, your VPN is leaking. If only the VPN IP is shown or WebRTC is blocked, you are protected.
Detecting your visible public IP requires asking an outside service. A STUN server is also used to trigger WebRTC disclosure. Neither IP nor any other data is stored by Alvea Hubs.
Disable WebRTC in your browser settings, install an extension like uBlock Origin, or switch to a VPN with built-in WebRTC leak protection. Firefox users can disable WebRTC via about:config.
WebRTC can reveal local (private) addresses like 192.168.x.x. These are less sensitive than your public IP but still reveal your home network setup.
Yes. Without a VPN both sections show your real IP, which is the baseline for comparison when you connect a VPN.
No. Alvea Hubs does not store your IP or any other data from this scan.
Yes, completely free with no sign-up required and no usage limits.
Unlike other Alvea Hubs tools, this one is not fully offline: detection uses a public STUN server and an external IP lookup. Neither your IP nor any other data is stored by Alvea Hubs.