Your public IP address is the address websites and services see when you connect to them. This page looks up that address in your browser using the ipify API, then runs a WebRTC check to see whether your browser also exposes other addresses through ICE candidates. Both checks can help you tell whether a VPN is actually changing the address sites see, and whether WebRTC is leaking a different address on the side.
This page contains no affiliate links. See our affiliate disclosure and how we review. By Impulsblog Editorial. Updated: November 2026
Bottom line: compare the public IP with WebRTC candidates
- The public IPv4 (and, if available, IPv6) lookup uses ipify, a free CORS-friendly API, from your browser.
- The WebRTC panel gathers ICE candidates with Google’s public STUN server and lists any addresses the browser exposes.
- If a VPN is on, you want those public addresses to match the VPN — not a second, real ISP IP.
- This is not a DNS leak test. For DNS, IPv6 routing and kill-switch steps, see how to check if your VPN is leaking.
Public IP and WebRTC check
| Public IPv4 (ipify) | Waiting… |
|---|---|
| Public IPv6 (ipify) | Waiting… |
WebRTC ICE candidates collected with Google’s public STUN server (stun.l.google.com:19302). A short connection test is sent to that STUN service so the browser can discover reflexive addresses. Impulsblog does not see the result.
| Address | Candidate type | Notes |
|---|---|---|
| Waiting… | ||
What the public IP lookup shows
The IPv4 address comes from https://api.ipify.org?format=json. If your network also has IPv6, a second lookup to https://api64.ipify.org?format=json may show an IPv6 address. These requests go to ipify, not to Impulsblog; we do not see your IP from this page. If you are connected to a VPN, the public address should belong to the VPN service, not to your home or mobile ISP. If it still looks like your ISP, the VPN may not be connected, or some traffic may be bypassing it.
What the WebRTC check can reveal
WebRTC is the browser technology behind many video and voice calls. To connect peers, the browser gathers ICE candidates, which can include local network addresses and, when a STUN server is used, your public address as seen by that server. This page uses Google’s public STUN server at stun.l.google.com:19302 to collect those candidates. That means a small connection test is sent to Google’s STUN service — not your browsing history, and not the rest of this page. If a WebRTC candidate shows a public IP that is different from the VPN address ipify reported, that is a classic WebRTC leak. Local addresses such as 192.168.x.x, or hostnames ending in .local, are your LAN or a browser privacy feature (mDNS); they are not the same thing as leaking your ISP’s public IP.
This is not a complete leak test. A thorough check also includes DNS, IPv6 routing, and a look at your VPN’s kill switch, which we walk through in our VPN leak test guide. Browser settings, extensions, or a strict VPN app can hide WebRTC candidates; if the check finds none, that is not a failure of your VPN by itself. For help choosing a VPN after you have tested, start with our best VPN guide.
FAQ
Why does this page call ipify and a STUN server?
Your public IP is fetched from api.ipify.org (and api64.ipify.org for IPv6) because that lookup has to come from a service that can see the address your connection arrives from. The WebRTC check uses Google’s public STUN server to gather ICE candidates. Those requests do not go through Impulsblog, and they are not a browse of the rest of the web.
What is a WebRTC leak?
A WebRTC leak is when your browser reveals a public IP address — often your real ISP address — through WebRTC ICE candidates even though other sites see a VPN address. If a candidate’s public IP does not match the ipify result while a VPN is connected, treat that as a warning and check your VPN app.
If I see a 192.168 or .local address, is my VPN leaking?
Not by itself. Addresses in ranges such as 192.168.x.x, 10.x.x.x, or hostnames ending in .local are local network or browser privacy (mDNS) values. A leak, in this test, is a different public IP than the one ipify reports.
Can this test DNS leaks?
No. A reliable DNS leak test needs resolvers or test domains that we do not operate from this page. Use our VPN leak-test guide for DNS, IPv6 and kill-switch checks.
Why might the WebRTC table be empty?
WebRTC may be disabled, blocked by an extension, or limited by the browser. An empty table is not proof that your VPN works, and it is not a failure of the public IP lookup.
Related guides: How to check if your VPN is leaking · Best VPN (2026) · VPN keeps disconnecting · VPN not working on hotel Wi-Fi · Strong password generator