Networking · Privacy · Digital Security

DNS & WebRTC Leak Test

Check your visible IP address and investigate whether WebRTC or DNS behavior could expose information about your connection.

A VPN is designed to route supported traffic through a VPN server, but browser behavior, network configuration, and DNS settings can affect what is exposed. Run these checks to better understand your current connection.

No security score. No fabricated results.

Privacy notice — read before testing

The public IP check contacts ipify, and the WebRTC check may contact the configured STUN server using the STUN protocol (not an HTTP/HTTPS API request). These services can observe your public IP address. A genuine DNS test, once configured, will trigger a unique DNS probe and contact your configured test backend. Results remain in this page's current memory; this tool does not save them in cookies, local storage, analytics, or an application database.

How this test works
  • Public IP: one HTTPS request to each configured IPv4 and IPv6 ipify endpoint. A failed request is not proof that an address family is unsupported.
  • WebRTC: your browser gathers ICE candidates. When the STUN server is used, it receives STUN-protocol traffic and may observe your public IP address. Candidate addresses are processed in this browser and are not sent to Synth Visual analytics.
  • DNS: disabled until a real backend and controlled probe domain are configured. A public DNS-over-HTTPS lookup is not substituted for this check.
  • Limits: results cover only the requests and candidates available during this test. They do not certify a VPN or guarantee anonymity.

Connection privacy checks

Run the available checks together. If DNS infrastructure has not been configured, IP and WebRTC checks still run normally.

No account required

Ready. No checks have run yet.

Test results

Statuses describe only the evidence available to this page.

Public IP Address

Not Tested
IPv4Not Tested
Not tested

No IPv4 lookup has been attempted.

IPv6Not Tested
Not tested

No IPv6 lookup has been attempted.

This is the public IP address seen by the lookup service. With a VPN, it may be the VPN server's IP address rather than your original ISP address.

WebRTC

Not Tested

WebRTC candidate inspection has not run yet.

The configured STUN server may observe your public IP address. Candidate gathering may be limited or blocked by browser/network settings.

DNS Leak Test

Not Configured

DNS leak detection requires a configured test service that can observe authoritative DNS queries. This part of the test is not available yet.

The page will not substitute a DNS-over-HTTPS lookup for a test of your current recursive resolver.

Overall summary

No tests have run. Start the checks to see the available observations. A clean result cannot certify that a VPN is secure.

Public IPv4
Not tested
Public IPv6
Not tested
WebRTC
Not tested
DNS test
Not configured

Timestamp: no test run yet.

Understand the results

What these checks can tell you

These tests are useful signals, not a complete audit of your network or VPN.

What Is a DNS Leak?

A DNS leak can occur when DNS queries are sent to a resolver outside the privacy configuration you expect—for example, an ISP resolver when you expect your VPN to handle DNS. A resolver operated by a third party is not automatically a leak; network topology, split tunneling, browser-level encrypted DNS, VPN configuration, and enterprise networks all affect what you may observe.

What Is a WebRTC Leak?

WebRTC is a set of browser technologies used for real-time communication, including voice and video. During connection setup, ICE candidates can contain address information. Depending on browser and network configuration, candidate details may reveal IP or local-network information that a user did not expect. A private LAN address is not automatically a public IP leak.

Does a Clean Test Guarantee That My VPN Is Secure?

No. These checks inspect selected aspects of the browser's current connection. They cannot certify a VPN, audit every application or network route, detect every form of tracking, verify malware protection, or guarantee anonymity. A mismatch is a reason to investigate, not proof that an original ISP address was exposed.

What Should I Do If a Problem Is Detected?

  1. Confirm that the VPN is connected, then repeat the test after reconnecting.
  2. Review the VPN application's DNS, IPv6, split-tunneling, and leak-protection settings.
  3. Check browser WebRTC and secure-DNS settings where applicable.
  4. Consult the VPN provider's official troubleshooting documentation. Avoid disabling security protections indiscriminately.