WebRTCOK
Local IP address is not exposed via WebRTC — the browser masks it.
WebRTC powers calls and data transfer right in the browser, but while setting up a connection it can reveal your local, and sometimes real, address past the tunnel.
Is my VPN working right now
In a couple of seconds, check whether your traffic really goes through the VPN and whether your real address is leaking. We look at your public IP address, network type, WebRTC, IPv6 and time zone — and explain in plain language what each signal means.
The check runs right in your browser. We do not log or store your IP address — location is resolved from a database on our server.
Checking your connection…
Your connection
- Public IP address
- Unavailable
- Network type
- Home provider
Leak signals
IPv6OK
The connection uses IPv4 — your real IPv6 address is not exposed.
Many VPNs tunnel only IPv4. If your provider gives you IPv6, that traffic can bypass the VPN and reveal your real address.
Time zone vs IP countryInfo
Could not match the time zone to the IP country.
When you turn on a VPN in another country, your device time zone usually stays your real one while the IP country changes. A mismatch is an indirect sign of a VPN (but not a fact: travelers and manual clock settings can trigger it).
DNS queriesInfo
This check cannot see which DNS resolver handles your queries; our separate DNS leak test does that. In the LiMP app, DNS queries go inside the encrypted tunnel, so your provider cannot see which sites you open.
A DNS leak is when site names resolve through your provider's DNS around the VPN. The provider then sees the list of domains, even if the traffic itself is encrypted.
With LiMP VPN there are no leaks
The LiMP app routes all traffic — including IPv6 and DNS — through an encrypted tunnel, replaces your real IP address with a secure server address, and closes the usual leak channels.
The check runs on your device plus one request to our server for geolocation. We do not log, store or share your IP address with third parties.
IP Geolocation by DB-IP
What we check
Several independent signals — together they give an honest answer to whether the VPN works and whether your real address is leaking.
Public IP and network type
Your address (IPv4 or IPv6), country and provider by IP, and whether the address belongs to a data center — a typical VPN sign.
WebRTC and IPv6 leaks
We check whether the browser exposes a local address via WebRTC and whether traffic runs over IPv6 past the tunnel.
Time zone vs IP country
We compare your device time zone with the country of your IP address — a mismatch often means an active VPN.
When it helps
Confirm the VPN works
Turned on the VPN? Check that the IP, country and network type really changed instead of staying your own.
Find a leak
VPN on, but something reveals your real address? The check shows whether WebRTC or IPv6 leaks around the tunnel.
Before an important session
Before a stream, call or handling sensitive data, make sure your real city and provider are not visible from outside.
More LiMP tools
Free network, privacy and security checks right in your browser — no install, no sign-up.
- Is a site down for everyone or just me
- Website availability from different countries
- Internet stability test
- Internet speed test
- Password generator
- Password strength and leak check
- Email breach check
- Link and website phishing check
- DNS leak test
- Wi-Fi security check
- Dependency audit & SBOM
- My IP address & footprint
How to tell whether a VPN really works
An active VPN icon in the app does not guarantee that all traffic goes through the tunnel. The most reliable signal is your public IP address: when the VPN works, it changes to the VPN server address, usually from a data center and often in another country. If your IP address, city and provider stay your real ones after connecting, the tunnel did not come up and traffic goes directly.
What a leak is and where it comes from
Even with a working VPN, individual channels can reveal your real address around the tunnel. This most often happens for three reasons.
- WebRTC: the in-browser calling technology can expose a local, and sometimes real, IP address.
- IPv6: many VPNs tunnel only IPv4, and IPv6 traffic slips past the tunnel.
- DNS: site names can resolve through the provider's DNS, so it sees the list of domains you open.
What a WebRTC leak is
WebRTC is a browser-built technology for calls and data transfer. While setting up a connection it can collect your network addresses, including local ones, and hand them to a site around the VPN. Our check shows whether such addresses are visible. Modern browsers often mask the local address (mDNS), and then the result honestly shows “not exposed”.
Why the time zone gives away a VPN
When you connect to a VPN server in another country, your public IP address changes country while your device time zone stays your real one. We compare the two: if they do not match, it is an indirect sign of a working VPN. This is a heuristic, not a fact — travelers or manual clock settings can trigger a false positive.
How LiMP VPN closes leaks
The LiMP app routes all traffic through an encrypted tunnel, including IPv6 and DNS queries, so your provider cannot see which sites you open and sites see the secure server address, not yours. Your real IP address, location and browsing history stay private on Android, Windows and in the Chrome browser.
Common questions about VPN checks and leaks
The most reliable signal is the public IP address: when the VPN works, it changes to the VPN server address, usually from a data center and often in another country. If your IP, city and provider stayed the same after connecting, the tunnel is not working. Our check shows this together with leak signals.
It is when site names resolve through your provider's DNS server around the VPN. Even if the traffic itself is encrypted, the provider sees the list of domains you open. Our DNS leak test shows which resolver handles your queries: it watches them from our own DNS server.
A browser does not tell a site which DNS resolver handles its queries, so DNS is checked separately, in the DNS leak test, where our own DNS server sees the queries. Here we show what is measurable from the browser: WebRTC, IPv6, network type and time zone.
Many VPNs tunnel only IPv4 traffic. If your provider also gave you an IPv6 address, requests over it can slip past the tunnel and reveal your real address. If the check shows the connection uses IPv6 while the VPN does not claim IPv6 support, that is a leak risk.
This happens when the VPN is connected but the tunnel did not actually come up, or the VPN server is in your own country with an ordinary provider address. Reconnect, pick a server in another country and press “Check again”. If the IP does not change, the problem is on the VPN app side.
No. The check runs in your browser, and only one request goes to the server for geolocation of your IP. We do not log, store or share your IP address with third parties.