How to check if a VPN is working

To check if a VPN is working, connect to your VPN, then compare your visible IP address, DNS results, browser leak results, IPv6 behavior, and app status before and after connection. If the VPN is working, websites should see the VPN server's IP address rather than your normal network IP, and your traffic should follow the protected VPN route.

The checks below are practical and quick. They also help you tell the difference between a real leak, a browser setting, a split tunneling rule, or a VPN app that simply is not connected.

Is my VPN working? The quick VPN test checklist

Start with a simple checklist before you dig into advanced leak tests. The box above shows the IP address and location that this page can currently see. That makes it useful for a quick before and after comparison.

1. Disconnect your VPN. Refresh the page and note the IP address in the box above. You do not need to memorize it, but check the first few numbers and the displayed location.
2. Connect your VPN. Choose a server location in your VPN app and wait until the app says it is connected.
3. Refresh this page. The IP address in the box above should change to the VPN server's IP address.
4. Check the location. The displayed city or country should match, or be close to, the VPN server location you selected.
5. Run a DNS leak test. Your DNS results should not point back to your home internet provider or mobile carrier.
6. Check browser leaks. If you use Chrome, Edge, Firefox, Safari, or another browser, test for WebRTC leaks.
7. Test the kill switch. If your VPN app includes one, turn it on and confirm that traffic stops when the VPN drops.

This is enough for most everyday checks. If you want more background on what an IP address reveals, Crispy VPN has a plain-English guide at what is my IP.

Does VPN change IP address? The before and after check

Yes, a working VPN should change the public IP address that websites see. Your device still has a local network address, such as a home Wi-Fi address, but websites should see the VPN server's public IP instead of your normal public IP.

Here is the cleanest way to test it:

1. Turn the VPN off.
2. Open this page in a normal browser tab, not a cached screenshot or old tab.
3. Write down the IP address and approximate location shown in the box above.
4. Open your VPN app and connect to a server.
5. Return to this page and refresh it.
6. Confirm that the IP address has changed.

If the IP address does not change, the VPN is probably not carrying that browser's traffic. Check whether the app is actually connected, whether you are using a browser extension instead of the full VPN app, or whether split tunneling is excluding that app or website.

What result should you expect?

The location does not always need to be exact down to the street or city. IP location databases are approximate. What matters is that the result no longer shows your normal internet provider's public IP address. A VPN server in London might show London or a nearby area, for example. That is normal.

With Crispy VPN, you can choose from 12 server locations, including cities in Europe, the United States, and Asia Pacific. Pick one, reconnect, then refresh the IP box above to see whether your visible address changes.

Am I using a VPN? Check the app, device, and route

If you are asking, am I using a VPN, do not rely on one signal alone. A browser can show one route while another app uses a different route. A system VPN app, a browser extension, and split tunneling can all affect what is protected.

Check the VPN app status

Open the VPN app and look for the connection state. It should clearly show that it is connected. If it is still connecting, reconnecting, or waiting for network access, your traffic may not be protected yet.

On phones and computers, the operating system may also show a VPN indicator. That indicator is helpful, but the VPN app is usually the better source of truth because it shows the selected server and connection state.

Check what you are actually using

A full VPN app can protect traffic from your device, subject to your settings. A browser extension usually protects only browser traffic. If you are testing in a browser but using a system VPN app, the IP check should change. If you are using only a browser extension, apps outside that browser may not use the VPN route.

Crispy VPN offers apps for iPhone and iPad, Mac, Windows, Linux, Android, Apple TV, Android TV and Google TV, plus browser extensions for Chrome, Edge, and Firefox. If you are not sure you have the right app for your device, use the official download page.

Check split tunneling rules

Split tunneling can make a failed-looking test perfectly normal. If a website or app is set to bypass the VPN, it may show your regular IP address by design. Crispy VPN supports split tunneling on Android by app, on iPhone and iPad by website, and in browser extensions by website.

Run a DNS leak VPN test

A DNS leak happens when your browser uses the VPN for the website connection, but your DNS lookups still go to your internet provider or another resolver outside the VPN path. DNS is the lookup step that turns a domain name into an IP address.

To run a DNS leak check, connect to your VPN, then use a DNS leak test page from your browser. You are looking for DNS servers that match the VPN route, not your home internet provider, office network, school network, or mobile carrier.

How to read the result

• Expected: DNS servers are associated with the VPN route or do not reveal your normal provider.
• Possible leak: DNS servers clearly identify your home internet provider, mobile carrier, or local network while the VPN is connected.
• Mixed result: Some entries look like the VPN route, while others look like your normal provider. Treat this as a problem worth fixing.

If the DNS test fails, disconnect and reconnect the VPN, then repeat the test in a fresh browser tab. If you are on Wi-Fi, try switching networks or restarting the device. Also check whether a manual DNS setting, enterprise profile, security product, or browser DNS setting is overriding the VPN route.

DNS leaks matter because they can reveal which domains your device is trying to reach, even if the website connection itself uses the VPN. They do not necessarily reveal every page you visit, but they are still a sign that your setup needs attention.

What is my IP VPN result in browsers? Check WebRTC

The phrase what is my IP VPN usually means, what IP address does my browser reveal while the VPN is connected. The box above answers the basic version of that question, but browsers can expose network information in another way: WebRTC.

WebRTC is a browser technology used for real-time voice, video, and peer-to-peer features. In some setups, a WebRTC test may show local or public network addresses that you did not expect to expose.

How to test for WebRTC leaks

1. Connect your VPN.
2. Open a WebRTC leak test in the browser you actually use.
3. Look for public IP addresses in the result.
4. Compare them with the VPN IP shown in the box above.
5. If your normal public IP appears, treat it as a leak.

If WebRTC shows only the VPN IP, local private addresses, or non-identifying local network values, that is usually fine. If it shows your normal public IP address, check your browser privacy settings or use a browser extension that routes browser traffic through the VPN. You can also test in another browser to see whether the issue is browser-specific.

This is one reason it helps to test the exact browser you use every day. Passing in one browser does not guarantee the same result in another browser with different settings and extensions.

Test IPv6 behavior without overthinking it

IPv6 is the newer internet addressing system. Some networks use it, some do not, and some use both IPv4 and IPv6. A VPN check can look good for IPv4 while IPv6 traffic still uses the normal network route.

To test this, connect your VPN and run an IPv6 leak check. If your network does not support IPv6, the test may simply say IPv6 is not available. That is not a leak. If IPv6 is available and the result shows your normal provider or a non-VPN address, you should fix it.

What to do if IPv6 leaks

• Reconnect the VPN and retest.
• Restart the VPN app, then refresh the test page.
• Check for operating system network profiles that force IPv6 behavior.
• Update the VPN app if you are using an old version.
• Test on another network, such as mobile data instead of Wi-Fi, to see whether the issue follows the device or the network.

Do not assume every IPv6 warning is a privacy failure. The key question is whether the test exposes a usable public IPv6 address tied to your normal network while the VPN is connected.

Kill switch test: make sure traffic stops when the VPN drops

A kill switch is designed to stop traffic if the VPN connection drops. It is useful on unstable Wi-Fi, during network changes, or when you do not want apps to reconnect outside the VPN without you noticing.

In Crispy VPN, the kill switch is opt-in, so it is off by default. It is available on iPhone and iPad, Mac, Windows, Linux, and the browser extensions. Windows also includes an optional Lockdown mode. On Android, use the system Always-on VPN and Block connections without VPN settings. Apple TV and Android TV apps do not have a kill switch.

Safe way to test it

1. Turn on the kill switch in the VPN app or system settings.
2. Connect the VPN and confirm the IP address changes in the box above.
3. Start loading a simple webpage.
4. Disconnect the VPN from inside the app, or briefly switch networks.
5. Check whether traffic stops instead of falling back to your normal connection.
6. Reconnect the VPN and confirm browsing works again.

If traffic continues normally after the VPN drops, check whether the kill switch is enabled for the right app or profile. Browser extension kill switches apply to browser extension traffic, not necessarily to every app on the device.

A kill switch is not a malware filter, phishing shield, or anonymity tool. It is a connection safety feature. It helps prevent accidental fallback to the normal network route.

What to do if a check fails

A failed VPN test does not always mean the VPN service is broken. It can be a stale browser tab, a split tunneling rule, a browser feature, a DNS override, or a device setting. Work through fixes in a sensible order.

Use this troubleshooting order

1. Refresh the test page. Old tabs can show cached or outdated information.
2. Reconnect the VPN. Disconnect, wait a few seconds, then connect again.
3. Change server location. Pick another location and repeat the IP and DNS checks.
4. Check split tunneling. Make sure the browser, app, or website is not excluded from the VPN route.
5. Disable conflicting network tools. Other VPNs, proxies, custom DNS tools, and security products can interfere.
6. Update the app. Install the current version from the official source.
7. Restart the device. This clears stuck network states more often than people expect.
8. Test another network. Try mobile data, a different Wi-Fi network, or a hotspot.

If you are new to VPNs, our step-by-step guide on how to use a VPN explains the basic setup flow. If you want the technical background, read how a VPN works.

Finally, keep expectations realistic. A VPN can change the IP address websites see and protect traffic on untrusted networks, but it does not make you anonymous. It also does not stop malware or phishing on its own, and it does not stop tracking by websites where you are logged in.