Free tools Windows power users keep installed
One-click scans. No signup required.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
A router’s WireGuard status can look healthy while a client still uses the ISP for web traffic or DNS. To verify the setup, test one device behind the router in a clean network path, confirm the peer handshake, check the client’s public IPv4 address, run a separate DNS leak check, test IPv6 independently, and—if your policy requires it—verify that traffic stops when the tunnel drops.
The result applies to the tested client, route, configuration and moment. It is not a universal guarantee for every device, VLAN, policy-routing rule or future router state.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
What exactly are you trying to prove?
There are four separate questions:
- Is the WireGuard peer active? A recent handshake and increasing counters show that the router and VPN endpoint are exchanging packets.
- Does this client’s internet traffic use the VPN exit? A client-side public-IP check should show the VPN provider’s expected address, not the home ISP address.
- Where do DNS lookups go? A DNS leak test reports resolver addresses or organizations. Compare those with the resolver behavior documented for your provider and router.
- What happens if the tunnel fails? A connected-state check does not prove that the router will block traffic during an outage. You must test fail-closed behavior separately if that is your requirement.
WireGuard is the encrypted tunnel protocol; routing policy decides which packets enter it. The WireGuard project describes replacing the default route as the straightforward full-tunnel technique, with policy routing used to keep the tunnel endpoint reachable (WireGuard’s routing documentation). A handshake therefore confirms connectivity, not end-to-end routing for every downstream device.
What do you need before starting?
Use one client connected to the router under test. Record the router model and firmware, VPN provider, client device, connection type, and whether the router is configured for full-tunnel or selective (policy) routing. Menu names vary by firmware and version.
Popular on Amazon
- 【90 Degree Full Function USB C Adapter】Supports the latest USB4 standard for up to 40Gbps of bandwidth, 8K video support, and up to 240W Fast charging; Support USB PD 3.1 Extended Power Range (EPR) including 140W, 180W and 240W. Your productivity is easily doubled. *Warm Tip: For the best fit, please make sure the USB-C port is fully exposed; thick or bulky cases may affect compatibility.
- 【Reliable Quality】Made from high-quality, scratch-resistant aluminum alloy, delicate metal frame. get excellent wear resistance and heat dissipation. Non-Slip Design for easier insertion and removal.
- 【Small and portable】Ultra thin size, ultra compact design, a petite physique that matches the minimalist design of your modern laptops. Coming with a slim figure that won't block the port next to the one it's plugged into.
- 【Compatibility】Widely work with most usb c, thunderbolt 4/3 devices. Compatibilit for ROG Ally, Steam Deck, Switch, MacBook Pro, Quest 3 VR headset, Surface Book 2, iPhone 18/17/16/15, Samsung Galaxy S23/S22/S21, Note 20/10, Google Pixel, ChromeBook, etc.
- 【Excellence Customer Support】If you experience any issues or cable failure, simply reach out to our dedicated customer service team. We provide a prompt response within 18 hours, providing you with the necessary technical support to resolve any concerns.
- Disconnect the client’s cellular data, any second VPN or proxy, and Wi-Fi connections to another router.
- If practical, use Ethernet. It is an isolation aid, not a fix. A device can remain connected to another router over Wi-Fi while also using Ethernet; router documentation warns that this can send DNS queries over the unintended path (Mullvad’s OpenWrt router guide).
- Check which SSID, VLAN or policy-routing group the client uses. Guest networks, work VLANs and per-device rules may intentionally bypass the WireGuard interface.
- Have the VPN provider’s expected exit address and DNS behavior available. Some providers operate their own resolvers; others permit custom DNS.
Do not change settings during the initial run. Capture the time, client and results so that a later rerun can be compared with the same path.
How do you confirm that the WireGuard tunnel is active?
Open the router’s WireGuard status page and verify the expected peer has a recent handshake. If the router exposes transfer counters, generate traffic from the test client and confirm that sent and received byte counts move.
On systems that provide the WireGuard command-line utility, wg show displays interface and peer state; this is the command used in the official WireGuard Quick Start. OpenWrt’s worked example places the check at Status → WireGuard (Mullvad’s OpenWrt instructions).
A handshake is only a connectivity signal. It does not show that the test client selected the tunnel, that DNS uses the intended path, that IPv6 is protected, or that a failed tunnel cannot fall back to WAN. Continue with the client-side checks even when the status page is green.
How do you check the client’s public IPv4 address?
From the device behind the router, open your VPN provider’s connection-check page or another reputable public-IP service. Compare the displayed IPv4 address with the provider’s expected VPN exit result. The check must be performed on the client, not only in the router’s administration interface.
- Confirm the browser or app is running on the selected client and that cellular data and alternate Wi-Fi are disabled.
- Note the reported IPv4 address and the time.
- Compare it with the provider’s documented or connection-check result.
- Repeat after reconnecting the tunnel if the address is unexpected.
If the result is your home ISP’s public address, first verify the physical and wireless path. Then inspect whether the client is included in the full-tunnel route, whether a policy rule sends it to WAN, and whether firewall or kill-switch rules match the WireGuard interface. OpenWrt and provider guidance both use a client-side public-IP check; GL.iNet likewise states that the current IP should be the VPN provider’s address (GL.iNet’s VPN and DNS guidance).
Also popular on Amazon
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
An ISP address is evidence to investigate, not an explanation by itself. A second network adapter, a split-tunnel rule or a stale browser path can produce a different result. State which client and address family were checked and when; no single public-IP site proves that every device or service is leak-free.
How do you run a DNS leak test correctly?
DNS is a separate test from the public-IP check. Run a DNS leak test from the same client, record every resolver address or organization shown, and compare those results with the DNS service your provider and router are supposed to use.
- Keep the clean path from the preparation step: one router, one active connection and no second VPN or proxy.
- Run the provider’s recommended DNS check, or a reputable independent DNS leak test.
- Save the resolver names or addresses, not just a headline such as “no leak.”
- Compare the result with your actual configuration: provider DNS, custom DNS, router forwarding, or a policy-specific resolver.
- If the test appears to show the ISP, repeat with alternate Wi-Fi and cellular disabled, then inspect the router’s DNS settings and the route used for both client-originated and router-originated DNS.
Resolver branding or geographic location alone is not a universal leak criterion. A provider may deliberately use a third-party resolver, anycast infrastructure or a resolver whose displayed location differs from yours. The meaningful question is whether the resolver identities match the provider’s documented behavior and your configured route. Mullvad includes DNS-leak troubleshooting in its OpenWrt guide, and GL.iNet recommends a DNS leak test as part of its router privacy checks (Mullvad; GL.iNet).
One browser test cannot cover every process. Router firmware updates, NTP, telemetry, and other router-originated services may use a different resolver path from a client. If those services matter to your threat model, inspect the router’s own DNS and routing policy as well as the client result.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →How do you test IPv6 for a separate leak?
Check IPv6 independently because a clean VPN IPv4 result does not prove that IPv6 is tunneled or blocked. Use an IPv6-capable address and leak check from the same client, then compare the observed IPv6 behavior with the VPN provider’s documented design.
- Verify that the test client has IPv6 connectivity; a “no IPv6” result may mean IPv6 is intentionally disabled rather than leaked.
- Record the public IPv6 address, if one appears, and identify its network or provider.
- Compare it with the provider’s expected IPv6 exit or with the router policy that intentionally blocks IPv6.
- Repeat after reconnecting WireGuard and after any IPv6 setting change.
There are three legitimate outcomes: IPv6 can be carried through WireGuard, deliberately disabled or blocked, or accidentally sent to the ISP. The safe choice depends on your configuration and provider. For its documented OpenWrt setup, Mullvad says the Allowed IPs should include 0.0.0.0/0 and ::0/0 when the provider IPv6 address is leaking. The same guide notes that its router receives a single /128 IPv6 address rather than a downstream /64 prefix by default (Mullvad’s guide). Those values are provider-specific, not universal WireGuard settings; do not copy them blindly to another service.
Also popular on Amazon
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
If you intentionally disable IPv6, verify that the router’s firewall actually blocks IPv6 traffic rather than merely hiding the address from one test page. If you intend to tunnel IPv6, confirm that the provider supplies an IPv6 exit and that the router’s route and firewall include it.
How do you test what happens when the tunnel drops?
Normal connected-state checks do not test an outage. If your policy is “no internet without the VPN,” briefly interrupt the WireGuard tunnel and verify that the client loses internet access instead of silently using WAN.
- Complete and record the normal IPv4, DNS and IPv6 results first.
- Choose a short, controlled interruption: disable the WireGuard interface or stop the client tunnel from the router’s status page.
- While it is down, try a known website and repeat a public-IP check. A fail-closed router should block traffic, not expose the ISP address.
- Restore WireGuard, wait for a recent handshake, and rerun the same public-IP and DNS checks.
Only perform this test when a brief outage is acceptable. Firewall and kill-switch controls differ by firmware. GL.iNet documents an Internet Kill Switch setting, while Mullvad’s OpenWrt guide includes firewall and kill-switch troubleshooting (GL.iNet; Mullvad). Identify the router model and firmware before following menu-level instructions.
A router that falls back to WAN may still be suitable for a policy that prioritizes availability, but it is not fail-closed privacy protection. Document the actual behavior rather than assuming the word “kill switch” means every client and router-originated service is blocked.
What should you check when a result fails?
Work from the client path inward and change one setting at a time:
- Connection path: confirm the client is on the intended router, SSID and VLAN, with cellular data, alternate Wi-Fi and other VPNs disabled.
- Peer activity: confirm the expected peer and a recent handshake; generate traffic and watch counters.
- Routing scope: verify whether the setup is full-tunnel or selective. A policy rule may deliberately send this client, subnet or destination through WAN.
- DNS configuration: compare router forwarding, custom resolver settings and provider instructions. Check client-originated and router-originated DNS separately when necessary.
- IPv6 handling: determine whether IPv6 is tunneled, blocked or unintentionally using the ISP. Check routes and firewall policy for both address families.
- Failure behavior: inspect kill-switch and firewall rules, then repeat the tunnel-drop test.
For OpenWrt, use the current WireGuard client documentation and WireGuard extras documentation for the installed firmware, alongside your provider’s guide. OpenWrt menu paths and firewall defaults can change between releases.
Also popular on Amazon
- Portable and powerful USB-C HUB: BENFEI USB Type-C HUB, with super-soft and knot-free silicone woven design cable, meets most mobile office needs. Compact, lightweight, stylish, and powerful portable USB C Hub equipped with 1 x HDMI port, 1 x 100W charging, and 3 x USB ports. 18-month warranty, 24-hour response, to ensure you feel at ease when using our product.
- Design centered on comfort and reliability: Thanks to BENFEI's end-to-end in-house cable production capability, in-house PCBA and assembly capability, using the industry's most advanced silicone woven design and process, 20cm cable in length, no knots, super-soft, the HUB is easy to use in all scenarios: laptop, tablet, stand etc. Super-soft, 25000+ life cycles, to meet your daily carrying and office needs.
- 100W Charging: Support up to 90W USB C pass-through charging via Type-C port to keep your laptop powered. 10W is reserved for other interface operations. No data and video function on the Type-C port.
- 4K HDMI Display: The HDMI port supports media display at resolutions up to 4K 30Hz, keeping every incredible moment detailed and ultra vivid. Please note that the C port of the Host device needs to support video output.
- Transfer Files in Seconds: Transfer files and from your laptop at speeds up to 10 Gbps with USB A 3.2 port. Extra 2 USB A 2.0 ports are perfectly for your keyboards and mouse.
If the client’s IPv4 address is the VPN exit but DNS shows an unexpected resolver, treat that as a DNS-routing issue rather than proof that all traffic bypasses WireGuard. Conversely, matching DNS does not prove that the client’s web traffic uses the tunnel. Keep each result tied to its own test.
How can you read mixed or confusing results?
| IPv4 result | DNS result | IPv6 result | Likely interpretation |
|---|---|---|---|
| VPN exit | Expected provider or configured resolver | Expected tunneled result or deliberately blocked | Consistent with the intended policy for this client; still record the timestamp and route. |
| VPN exit | Unexpected ISP resolver | Not checked | Investigate DNS forwarding, client resolver settings and alternate network paths. |
| ISP address | Any result | Any result | Check client path, tunnel inclusion and policy routing before changing DNS. |
| VPN exit | Expected | ISP IPv6 address | IPv6 is a separate bypass; tunnel it or block it according to the provider’s supported design. |
| No internet during outage | Not applicable | Not applicable | Consistent with fail-closed behavior for the tested client, but repeat after restoring the tunnel. |
Do not infer more than the evidence supports. A result describes one client, one route, one router state and one moment. Separate SSIDs, VLANs, selective routing and router-originated traffic can behave differently.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What does a clean verification record look like?
Save a short record rather than a screenshot with no context:
- Router model and firmware version.
- VPN provider and WireGuard peer.
- Client device, operating system and connection type.
- SSID, VLAN or policy group.
- Full-tunnel or selective-routing configuration.
- Handshake time and transfer-counter change.
- Observed public IPv4 address and provider comparison.
- DNS resolver identities and expected resolver policy.
- Observed IPv6 result and whether IPv6 is tunneled or blocked.
- Tunnel-drop behavior and restoration result.
- Date and time: November 2026 for this checklist’s publication context.
Repeat the record after firmware upgrades, provider configuration changes, new VLANs, or changes to DNS and IPv6 policy. A previously clean result is not a permanent guarantee.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How we define “not leaking” for this test
For the selected client, a defensible result is: the WireGuard peer has a recent handshake; the client’s public IPv4 matches the VPN exit; DNS resolver identities match the provider and router policy; IPv6 is either correctly tunneled or intentionally blocked; and, if required, traffic is blocked when the tunnel is unavailable. Any result outside that statement needs investigation or a documented policy exception.
This is an evidence-based verification procedure, not a promise that every device, application or future router state will behave identically. Keep the client path clean, test IPv4, DNS and IPv6 separately, and treat failover behavior as its own test.
Also popular on Amazon
- 【Read before You Buy】 Note: This adapter is USB 2.0 version and cannot transmit HDM, VGA, or other video signals. Nevertheless, they are fully capable of charging devices,duplicating files, and can be seamlessly integrated with USB-C earphones, wireless network adapters, and SD card adapters.
- 【Easy to Use and Safe】Thanks to modern manufacturing techniques, we've made these adapters sufficiently compact so that they can remain inserted in your device without noticeable protrusion or inconvenience. This means you don't have to constantly plug and unplug them, reducing the likelihood of wear and misalignment, and making them more convenient to carry around.
- 【Reliable Quality】Engineered for enhanced durability, durable aluminum alloy shell material,get excellent wear resistance and heat dissipation,the male USB C and female USB connectors & the male USB and female USB C connectors are designed to be plugged and unplugged up to 20000 times. Provides data transfer, device charging, memory space expansion, and additional computer peripherals.
- 【Think more for you】Do you need to connect a USB-C-enabled device to an odd device that only has USB-A ports? Then these USB-A male to USB-C female adapters are made for you.Simply insert the adapter into the USB-A port on the device, and you can instantly connect your USB-C device to the device that originally didn't have the correct connection port.
- 【Trusted xiwxi Quality and Service】As a responsible brand seller, you will receive xiwxi's 12-month Quality assurance and lifetime friendly customer service, you're not just buying a product,you're investing in peace of mind with all-round quality and exceptional customer service.
Frequently Asked Questions
Does a recent WireGuard handshake prove that my router is leak-free?
No. It proves that the configured peer exchanged packets recently, but it does not prove that every downstream client is routed through the interface. A client-side public-IP and DNS check is still required.
Should I test devices on guest Wi-Fi or other VLANs separately?
Yes. Guest SSIDs, VLANs and per-device policy rules can use different routes or firewall zones from the first client you tested. Run the same checks for each group whose traffic is supposed to use WireGuard.
Is an IPv6 address from my ISP always a DNS leak?
No. It is an IPv6-routing result, not a DNS result. It indicates that IPv6 traffic may be outside the tunnel; determine whether your policy is to tunnel IPv6 or block it, then verify that behavior directly.
What should I do if the VPN exit is correct but the DNS test lists several organizations?
Compare each resolver with the provider’s documented DNS design and your router’s forwarding settings. Multiple identities or an unexpected organization warrants checking alternate network paths and router-originated DNS, but branding or geography alone does not establish a bypass.
Can a router pass leak tests while its own updates use the ISP?
Yes. A browser on a downstream client and services generated by the router can follow different DNS or routing policies. If router-originated traffic matters, inspect the router’s own resolver and route configuration in addition to client tests.
