Donate
Donate
BETA

Is My VPN Working?

Verify IP change, DNS leaks, WebRTC leaks, and routing signals with a practical checklist

Why a simple IP change is not enough

Many users connect a VPN, see a different IP, and assume everything is fine. That is a good first check, but DNS leaks, WebRTC behavior, or route inconsistencies can still expose useful information. This wizard helps you verify the full picture.

Before/After Snapshot Compare

Capture a baseline before connecting your VPN, then capture your current network after connecting to compare IP, ASN, and provider changes. Snapshots are stored only in your browser.

Open IP checkerCheck ASN manually

Baseline

Capture before connecting your VPN.

Current

Capture after connecting your VPN.

Continue the checks

Complete the steps below to verify whether your VPN is actually protecting your traffic.

0 of 8 steps marked0% complete

Save your baseline IP details

Open the homepage checker before connecting your VPN and note your IP, ISP, and ASN. This is your comparison baseline.

Pending
Open IP checker

Connect your VPN

Enable your VPN and choose the server/location you want to test. Wait until the client shows connected status.

Pending
Compare VPNs

Did your public IP change?

Run the homepage checker again. Your public IP should usually change after the VPN connects.

Pending
Re-check IP

DNS leak test result

Run the DNS leak test workflow and decide whether it passed, failed, or needs more review.

Pending
Run DNS leak test

WebRTC leak test result

Run the WebRTC leak test to check browser-level IP exposure via STUN/WebRTC behavior.

Pending
Run WebRTC leak test

IPv6 leak test result (optional)Optional

If your network uses IPv6, check whether your VPN still exposes native IPv6 routing after it connects.

Pending
Run IPv6 leak test

Proxy/VPN detection signals look expected

Use Proxy Check as an extra signal. Unexpected results are not always failure, but they can indicate a setup issue.

Pending
Run Proxy Check

ASN/provider shift confirmed (optional)Optional

Compare the ASN before and after connecting. A provider/ASN change is a strong sign your routing changed.

Pending
Check ASN

How this VPN check works

The wizard is a guided checklist that combines your existing tools into one workflow: public IP verification, DNS leak checks, WebRTC leak checks, IPv6 leak review, proxy/VPN signal review, and optional ASN comparison. It stores only your step selections in local browser storage so you can continue later.

This page does not automatically inspect your system or VPN app. Instead, it helps you run repeatable tests and record the result of each step.

Run the core checks

What to do if your VPN fails a check

  • Reconnect to a different VPN server and test again.
  • Enable kill switch and leak protection in your VPN app settings.
  • Review split tunneling rules for browser and DNS apps.
  • Restart your browser after changing WebRTC/privacy settings.
  • Re-run the same sequence after OS, browser, or VPN app updates.

If your VPN connects but your IP does not change, start with VPN connected but IP not changing.

Fix and learn more

Protect your IP and privacy

Related Articles

VPN Connected but IP Not Changing? How to Fix It8 min read • February 9, 2026VPN vs Proxy: Privacy, Speed, and Which to Use14 min read • December 1, 2025IPv4 vs IPv6: Understanding the Differences10 min read • November 4, 2025What is a VPN and How Does it Work?9 min read • November 9, 2025How to Hide Your IP While Gaming: Reduce DDoS Risk and Verify Your VPN10 min read • February 23, 2026

Frequently asked questions

How do I know if my VPN is actually working?
Verify more than just the public IP. Check for IP changes, DNS leaks, WebRTC leaks, and proxy/VPN signals, and optionally compare ASN/provider changes before and after connecting the VPN.
Is a changed IP enough to confirm VPN protection?
No. A changed IP is a strong start, but DNS, WebRTC, and sometimes IPv6 can still leak useful information outside the VPN route.
Why does my VPN show connected but my IP does not change?
It can happen because of app issues, split tunneling, browser caching, or testing the wrong network path. Reconnect, change server, and re-run the full checklist.
Do I need to run the tests every time I use a VPN?
Not every session, but you should re-test after VPN app updates, browser updates, OS networking changes, or when switching devices/networks.
Does this wizard store my IP address?
No. The wizard only stores your step selections in local browser storage so you can continue the checklist later.