If you’re like most people, you’ve never tested whether your virtual private network (VPN) is actually working. You install the app, see the connection indicator, and assume everything’s fine. But what if your real IP address and other online activities are still visible to websites and your internet provider? What if the privacy you’re counting on is more illusion than reality?

Checking if your VPN is working takes less than five minutes and requires no technical expertise. In this guide, we’ll walk through exactly how to test your VPN for the most common problems, what to do if you discover issues, and a simple monthly routine that ensures your VPN is genuinely protecting your privacy, not just displaying a reassuring icon.

Quick Start Steps:

  1. Check your IP address: it should show your VPN server’s location, not your real one.
  2. Run a DNS leak test: ensure your device isn’t still sending DNS requests to your ISP.
  3. Run a WebRTC leak test: confirm your browser isn’t revealing your true IP during calls or collaboration tools.
  4. Run an IPv6 leak test: make sure IPv6 traffic isn’t bypassing your VPN tunnel.
  5. Fix any leaks you find: enable leak protection, switch servers, restart your device, or adjust browser privacy settings. Most leaks are easy to resolve.

Why Checking Your VPN Matters

People rely on VPNs for many reasons: securing connections on public Wi-Fi, blocking ISP tracking, reducing data‑broker profiling, and accessing region-specific content. But once a tool becomes this essential, simply installing it isn’t enough; you need to know it’s actually protecting you. Regular testing ensures it will work when you need it most.

The Trust Gap in Privacy Tools

Even reputable privacy tools can get it wrong. In 2024, for instance, the FTC banned security company Avast from selling user data it allegedly collected without consent and fined the company $16.5 million. Users believed they were gaining privacy. Instead, their browsing habits were being monetized without consent. 

This isn’t an isolated incident. Each year, the FTC files hundreds of cases against individuals and businesses for deceptive privacy claims.

For VPN users, having the tool installed doesn’t automatically mean your privacy is protected. The VPN must be configured correctly, function as advertised, and be verified. Testing provides the only real proof.

Who Benefits Most from Regular Testing

While all users benefit from a correctly working VPN, certain groups enjoy the most advantages:

  • Remote and hybrid workers who handle sensitive business information on home networks need reliable protection to avoid exposing confidential work or client-related communications.
  • Small business owners and freelancers must conduct testing as a personal responsibility, as they often lack IT support.
  • Content creators and journalists working on sensitive topics need assurance that their research and communications remain private. Location tracking through VPN leaks could pose professional or personal risks.
  • Frequent travelers connecting through hotel Wi-Fi, airport networks, and international internet infrastructure deserve a VPN that properly protects them across diverse network conditions.
  • Privacy-conscious individuals who specifically chose VPNs to reduce data broker tracking should verify that their efforts are actually working rather than creating a false sense of security.

If you fall into any of these categories, regular VPN testing moves from “nice to have” to essential practice.

What a Working VPN Should Do

Before you test anything, it’s best to establish clear expectations about what a properly functioning VPN should do. A VPN creates an encrypted tunnel between your device and the remote server. In practice, this means:

  • Encryption: Your internet traffic is scrambled before leaving your device, making the information unreadable to anyone who might intercept it. This is particularly important on public Wi-Fi networks, where other users on the same network could monitor your activity.
  • IP masking: Instead of websites seeing your actual IP address, which can reveal your location and identify your internet service provider (ISP), they see the address of the VPN server you’re connected to. If you’re physically in Berlin but connected to a VPN server in Toronto, websites will think you’re browsing from Canada.
  • DNS routing: Your requests to access websites should go through your VPN provider’s DNS servers, not your internet provider’s. This prevents your ISP from building a profile of your browsing behavior.

These three capabilities address specific concerns: securing work connections while remote, reducing tracking by data brokers and advertisers, protecting personal information on untrusted networks, and accessing content that might be restricted by geographic location. Knowing how VPNs work clarifies what you are testing for.

How to Check If Your VPN Is Working

 A VPN can look connected while still leaking information behind the scenes. Modern devices, browsers, and networks sometimes override your VPN’s routing rules, creating quiet failures you’d never notice without testing. These failures usually fall into four categories: 

  • IP leaks
  • DNS leaks
  • WebRTC leaks
  • IPv6 leaks

Basic IP Address Test

An IP leak happens when websites can still see your real IP address, instead of only seeing your VPN server’s IP. If it’s not working, websites and advertisers can still identify your region and ISP, even with a VPN. This is the most fundamental check to determine if your VPN is successfully masking your IP address.

How to test it:

  1. Turn your VPN off and visit an IP‑checking site, such as WhatIsMyIP.com. Note your real IP, approximate location, and ISP.
  2. Turn your VPN on and connect to a server in another city or country.
  3. Refresh the page. You should now see a different IP address, the VPN server’s location, and either the VPN provider’s name or a data‑center label.

    Red flag: If any of your original information still appears, especially your real location or ISP name, your VPN is not working properly.

    Real-world check: Access a streaming service or website that adjusts its content based on your location. If you’re supposedly connected to a server in Japan but Netflix still shows your local library, that’s an indicator that your IP isn’t being masked.

    DNS Leak Test

    The Domain Name System (DNS) translates website names like “mcafee.com” into the numeric addresses your device uses to connect to them. Every time you visit a site, your device sends DNS queries. A DNS leak happens when those queries go to your internet provider’s DNS servers instead of your VPN’s. This allows your ISP to see every website you visit, even if your VPN appears connected and your IP looks hidden. 

    So, your IP might be masked, but your browsing history might still be visible through DNS queries. Follow these steps to check:

    1. With your VPN off, visit a DNS leak test site, such as BrowserLeaks or BrowserScan. The sites will list the DNS servers belonging to your internet service provider in your actual geographic area.
    2. Turn on your VPN to a server in a different country, then go back to the DNS leak test site.
    3. What success looks like: The DNS servers shown now should either belong to your VPN company or a third-party DNS provider that your VPN routes through, such as Cloudflare or Google Public DNS. The server locations should align with your VPN server location or established privacy-focused DNS providers.
    4. Red flag: If you still see your ISP’s name in the DNS results, you have a DNS leak.

    DNS leaks are invisible during normal browsing. Everything will seem to work fine, but your internet provider is tracking every website you visit.

    WebRTC Leak Check

    Web Real‑Time Communication (WebRTC) is a browser feature that enables video calls and real‑time collaboration. A WebRTC leak occurs when your browser bypasses your VPN connection, exposing your real IP address to websites or advertisers, even when your VPN appears connected. This is especially important for anyone using browser‑based meeting tools or remote‑work apps.

    To check if WebRTC has bypassed your VPN and exposed your IP address: 

    1. With your VPN connected, visit a WebRTC leak test site. Good options include BrowserLeaks WebRTC test or Top10VPN’s leak test tool. These tools check whether your browser exposes IP information via WebRTC.
    2. What success looks like: You should see only your VPN server’s IP address. No local network addresses, and definitely not your real public IP address.
    3. Red flag: If the test shows your actual public IP address or local network addresses alongside your VPN IP, you have a WebRTC leak. If you use your browser for work video conferences, including Zoom web client, Google Meet, Microsoft Teams in browser, browser-based collaboration tools, or even websites that use WebRTC for features like peer-to-peer file sharing, these services can potentially see your real IP address and location. This is particularly relevant for remote workers.

    Quick fix: Many VPN apps include WebRTC leak protection that you can enable in the settings. You can also disable or restrict WebRTC directly in your browser settings, or install a browser extension that blocks WebRTC and just re-enable it temporarily when needed.

    IPv6 Leak Test

    Many networks now support IPv6, the newer internet addressing system. Some VPNs, however, only secure IPv4 traffic. An IPv6 leak occurs when your device uses IPv6 to connect while your VPN protects only IPv4, allowing websites or services to see your real IPv6 address and location.

    This is how to test if you have an IPv6 leak:

    1. With your VPN connected, use a comprehensive leak test tool that checks both IPv4 and IPv6. You may use BrowserLeaks IP test or Top10VPN’s tool to show both protocol versions.
    2. What success looks like: You should see only your VPN server’s IP address for both IPv4 and IPv6 results, if IPv6 is shown at all. Many VPNs simply disable IPv6 entirely, and you will see only your masked IPv4 address.
    3. Red flag: If you see two IP addresses, that is, your VPN’s IPv4 address and a different IPv6 address that reveals your real location or internet provider, you have an IPv6 leak. Your IPv6 traffic is not being protected.
    4. Advanced option: Some VPN clients allow you to disable IPv6 at the operating system level, forcing all traffic through IPv4 where your VPN protection works. Check your VPN’s documentation for guidance. Alternatively, look for VPN providers that fully support and protect both IPv4 and IPv6 traffic.

    Troubleshooting Common VPN Issues

    Finding leaks doesn’t mean you need to panic or switch providers immediately. Many common VPN leaks can be resolved quickly with configuration changes you can make yourself.

    Simple Fixes to Try First

    Start with your VPN app’s built-in protection features, specifically designed to prevent leaks. These fixes resolve many common leaks within minutes.

    • Enable DNS leak protection: This VPN setting forces all DNS queries through your VPN connection, preventing your device from using your ISP’s DNS servers. In your VPN app’s settings or preferences section, this might be called “DNS leak protection,” “Custom DNS,” or “Use VPN DNS only.”
    • Activate the kill switch: A kill switch is a safety feature that monitors your connection and automatically blocks all internet traffic if your VPN disconnects unexpectedly, preventing your device from reverting to an unprotected connection without warning. Enable it whenever possible.
    • Restart everything: Sometimes your device’s network settings get cached in ways that cause leaks. Disconnect your VPN, close the app completely, restart your device, then reconnect. This clears cached DNS information and network routing tables.
    • Try different servers or protocols: Connect to a different VPN server location and run your tests again. Sometimes, specific servers have configuration issues. You could also try switching protocols if your app allows it. Modern protocols often handle leak prevention better than older protocols.

    Address Browser-Level Privacy Settings

    Your web browser may undermine your VPN through its own privacy and performance features. Here’s how to align your browser with your VPN:

    • WebRTC control: You can disable WebRTC entirely in your browser settings, although this may break browser-based video calls and similar features. Alternatively, you could install a reputable browser extension that disables or restricts WebRTC.
    • Disable secure DNS features: Modern browsers include secure DNS (DNS over HTTPS) features that bypass your system’s settings. While these features aim to improve privacy, they can cause DNS leaks by ignoring your VPN’s DNS routing. To disable them in Chrome, go to Security settings > Use secure DNS and turn it off or configure it to use your VPN’s DNS provider. In Firefox, go to Privacy settings > Enable DNS over HTTPS, then disable it or manually configure it.
    • Check default browser settings: Some browsers now default to privacy-focused DNS providers. Make sure these settings match your VPN rather than working against it.

    The goal is to make your browser respect your VPN’s network routing rather than trying to optimize around it.

    Troubleshooting Device‑Specific VPN Issues

    How to Check If VPN Is Working on iPhone:

    1. Connect to your VPN and open Settings → Wi‑Fi → (i) to confirm your IP has changed.
    2. Visit WhatIsMyIP — you should see your VPN server’s location, not your real one.
    3. Run a DNS leak test in Safari to ensure your ISP’s DNS isn’t showing.
    4. If leaks persist, toggle VPN → Off/On, disable Private Relay, then retest.

    How to Check If VPN Is Working on Android:

    1. Connect your VPN and look for the VPN key icon in the status bar.
    2. Visit WhatIsMyIP to confirm your IP and location have changed.
    3. Run a DNS leak test using Chrome or Firefox.
    4. If issues appear, disable Smart DNS, Data Saver, or Private DNS modes, then retest.

    How to Check If VPN Is Working on Mac/PC:

    1. Connect your VPN, then search “What is my IP?” in any browser.
    2. Confirm your new IP matches your VPN server’s location.
    3. Run DNS, WebRTC, and IPv6 leak tests in sequence.
    4. If results show your ISP, restart the VPN app, switch servers, or enable leak‑protection settings.

    When to Consider Switching VPN Providers

    Sometimes, persistent leaks indicate issues with your VPN service that configuration won’t fix. Here are red flags that suggest it’s time to evaluate alternatives:

    • Persistent leaks after troubleshooting: If you’ve enabled leak protection, restarted everything, tried multiple servers and protocols, and leaks still persist, that’s a serious concern. Your VPN provider should offer reliable leak-prevention measures.
    • Vague or missing documentation: Reputable providers clearly document how they handle DNS, IPv6, and WebRTC. If your provider’s website doesn’t address these topics or offers vague marketing-speak instead of technical details, that’s a red flag.
    • Free VPNs with unclear business models: Many free VPNs monetize by logging and selling user data, displaying ads, or secretly routing traffic through other users’ connections. If you don’t know how a free VPN sustains itself, your data might be the product.
    • No third-party audits or transparency: Leading VPN providers commission independent audits of their infrastructure and publish the results. They clearly document what data they collect, how long they keep it, and when they share it. Providers who don’t show transparency should be approached skeptically.

    When evaluating alternatives, look for providers that offer robust leak protection across all protocols, clear and specific privacy policies, independent security audits, modern protocols such as WireGuard, and responsive customer support to help troubleshoot issues.

    Free VPN Services

    Free VPN services are especially prone to leaks and questionable logging practices, yet 28% of internet users rely on them. Many free providers fund their operations by collecting and monetizing user data, injecting ads, or routing traffic through shared infrastructure that offers little real privacy. Without testing, you might go months or years believing you’re protected, while your actual browsing behavior remains visible to the entities you’re trying to avoid.

    Final Thoughts

    Testing your VPN is basic digital hygiene, similar to checking your phone’s screen lock or verifying that your home alarm system responds when tested. You can take a few minutes today to run the tests we outlined and determine whether your VPN is protecting you or just displaying a useless icon while your data flows freely.

    If you discover leaks, don’t panic. Start with the simple fixes: enable leak protection in your settings, activate the kill switch, restart, and reconnect. Many issues are resolved in minutes. If problems persist, use this guide to evaluate whether your current provider meets your needs or if it’s time to find one that does.

    VPN protection is most effective as part of a layered security approach, such as McAfee+, because privacy and security threats come from multiple directions. While your VPN handles IP masking and encrypted routing, comprehensive digital protection covers malware defense, identity monitoring, and safe browsing habits. Look for providers that demonstrate ongoing investment in protection methods, not just those relying on yesterday’s solutions.