🌙 LATE NIGHT MODE ACTIVATED — THE CLOWN IS WATCHING 🌙
Home → Tools → DNS Leak Test

Leak
Detector.

Real-time WebRTC leak detection in your browser, plus a guided DNS leak check. Runs entirely client-side.

🎪 Step 1 — Public IP

First, baseline: what does the public internet see as your IP?

📡 PUBLIC IP (HTTP)
checking...
—

🎪 Step 2 — WebRTC Leak Check

WebRTC can leak real IPs even when a VPN is active. We probe the browser's WebRTC API and surface any IPs it volunteers.

🩺 WEBRTC-VISIBLE ADDRESSES
probing…

🎪 Step 3 — DNS Leak (Manual)

DNS leak detection requires a server-side component (one that watches which resolver queries it). Since this page is fully client-side, we point you at the dedicated services:

dnsleaktest.com →

Run their Standard test. Listed resolvers should NOT match your real ISP if a VPN is active.

browserleaks.com/dns →

Shows what DNS server your browser is using right now. Compare against your VPN provider's expected resolver.

Heads up: opening these sites exposes your real IP to them (same as any site). They have their own privacy policies.

🎪 Reading Your Results

Step 1 (Public IP) Step 2 (WebRTC) Verdict
VPN-looking IP Only local IPs (192.168.x.x, 10.x.x.x) or none ✓ Healthy
VPN-looking IP A public IP different from Step 1 ✗ WebRTC leak
Your real ISP IP Anything ✗ VPN not active or routing
— Probe blocked (no candidates) ✓ Browser is locked down

🎪 FAQ

What's the difference between an IP leak and a DNS leak?
IP leak = a site sees your real IP even though you're on a VPN (often via WebRTC). DNS leak = your DNS queries go to a non-VPN resolver (often your ISP). Both undermine the privacy of a VPN session. They're independent problems.
Why can WebRTC leak my real IP even with a VPN?
WebRTC is a browser feature for direct browser-to-browser communication (video calls). To make connections work, it queries STUN servers — and those can reveal your real IP outside the VPN tunnel. Some browsers expose this by default.
How do I fix a WebRTC leak?
Firefox: about:config → set media.peerconnection.enabled to false. Chrome: install WebRTC Network Limiter or uBlock Origin with the 'Prevent WebRTC from leaking local IP' setting. Brave: Settings → Shields → WebRTC IP Handling Policy → 'Disable Non-Proxied UDP'.
How do I fix a DNS leak?
Most modern VPN clients (including ClownVPN) prevent DNS leaks by default — DNS queries are pushed through the tunnel. If you somehow see a leak, check that you don't have a custom DNS configured at the OS or browser level that bypasses the VPN.
Is the WebRTC IP shown below my real IP or a local one?
Could be either. Local-network IPs look like 192.168.x.x or 10.x.x.x — those are fine. Public IPs (real IPv4 / IPv6 addresses) showing up here behind a VPN = actual leak.

🎪 Got A Leak?

ClownVPN's kill switch + DNS push prevent both classes of leak for tunneled traffic. WebRTC leaks need a browser-level fix (see FAQ above).

🤖 Get The Free App