A VPN connection icon is a starting point, not proof that every part of your traffic is taking the route you expect. A few focused checks can reveal configuration surprises.
Clearly labeled evidence • No invented live measurements
Selected network route
IP • DNS • WebRTC
Check your public IP and IPv6 behavior, look at DNS resolver paths and understand WebRTC candidates. A complete leak test needs controlled measurement infrastructure and clear privacy handling; this draft is an educational hub, not an active leak scanner.
Read the method, check the limits, then use your own connection to confirm the result.
An IP address check, a DNS leak check and a WebRTC diagnostic observe different behaviors. The tools hub distinguishes available educational guidance from browser diagnostics that still require a secure backend or tested client code.
Public address is not an identity test
Resolver paths need independent checking
Browser exposure varies by settings
| Check | What it can reveal | Current status |
|---|---|---|
| Public IP / IPv4 / IPv6 | An address or route visible to a service you contact | Interpretation guide available; automatic lookup not connected |
| DNS leak test | Whether lookups appear to leave the intended resolver path | Diagnostic tool not connected |
| WebRTC exposure | Whether browser-mediated networking exposes addresses | Diagnostic tool not connected |
| Connection baseline | How throughput and latency compare VPN-off vs VPN-on | Measurement guide available; live test not connected |
Privacy and availability: No automatic IP, DNS or WebRTC diagnostic runs inside this draft. A production tool requires verified endpoints, a transparent privacy notice, scoped logging and appropriate rate limits.
Before connecting to the VPN, note the general location of your connection without publishing the full address. After connecting, confirm that remote services now see an exit address that matches the VPN configuration.
Our What Is My IP guide explains what the result can and cannot reveal.
Check IPv4 and IPv6 separately
Watch for split-tunneling rules
Understand approximate geolocation
Your device uses DNS to look up hostnames. Depending on network configuration, DNS traffic may follow a different path from ordinary browsing traffic. A leak test compares the resolvers observed during controlled DNS queries with the route you intended to use.
A list of resolver names is not enough to declare a privacy failure without understanding how the test was performed.
Verify the test resolves fresh names
Interpret resolver ownership carefully
Account for browser encrypted DNS settings
WebRTC can gather network connectivity candidates for real-time communication. Modern browsers apply privacy protections, but specific browser, extension and VPN combinations may expose network details in ways you did not expect.
A real WebRTC test must run in the browser with appropriate permissions and must explain which addresses are local, relayed or externally visible.
Browser settings matter
Different browsers can behave differently
Avoid overselling a single test result
Run checks before and after connecting, using the same device and browser. Keep the setup consistent and note IPv6, split tunneling and custom DNS configuration.
No live leak-detection result is shown in this draft. The production component should be tested and reviewed for data retention before it goes public.
Baseline first
Compare equivalent conditions
Publish the tool privacy policy
No. DNS, IPv6 and WebRTC behavior need separate checks.
Not yet. The current draft is a learning and interface page; active tests require separate validated tooling.
Not by default. Consider your threat model and required functionality; browser protections vary.
Related pages chosen for the next decision, not for repeating the same search query.
Learn how to check your public IPv4/IPv6 address, how VPN exit IPs work, and why IP location estimates can be inaccurate.
WireGuard vs OpenVPN explained: speed, UDP/TCP, security design, stability and which VPN protocol to choose for your connection.
How to test VPN speed correctly: download, upload, ping, jitter and packet loss. Learn to compare VPN performance against a fair baseline.
When an observed metric is published, its date, route, protocol, sample size and limitations should travel with it. Product claims and editorial judgments are labeled separately.
Independent VPN research and performance context.