WebRTC Leak Test

Check if WebRTC reveals local/public IP addresses through ICE candidates.

No scan yet

0

Public IPv4

0

Private / Local

0

mDNS Obfuscated

Detected ICE addresses

Run the test to collect WebRTC candidates.

About This Tool

WebRTC Leak Test inspects ICE candidate strings produced by your browser and highlights possible address exposure categories. It is useful when validating VPN, proxy, or privacy browser setup.

Frequently Asked Questions

Does a detected local IP always mean a leak?

Not always. Local candidates can appear in normal ICE gathering, but they can still matter in privacy threat models.

Why do I only see .local addresses?

Many browsers use mDNS hostnames to reduce direct local IP exposure in ICE candidates.

Is the scan remote?

No. Candidate parsing and reporting run locally in your browser. Only standard STUN signaling is used by WebRTC itself.

Related Tools

IP Address Analyzer
Analyze IPv4/IPv6 addresses: class, scope, binary, and hex representation.
Screen Resolution Info
View your screen resolution, viewport size, DPR, color depth, and device info.
Browser Fingerprint Checker
Inspect browser/device fingerprint signals like canvas hash, WebGL, timezone, and platform.

Workflow Links

Suggested step-by-step tools based on this page intent.

Before This Tool

Browser Permissions AuditorCheck browser permission states for camera, microphone, geolocation, notifications, and more.JWT DecoderDecode and inspect JSON Web Tokens. View header, payload, and expiration.ROT13 / Caesar CipherEncode/decode text with ROT13, ROT47, or custom Caesar cipher shift.

Next Step Tools

Browser Fingerprint CheckerInspect browser/device fingerprint signals like canvas hash, WebGL, timezone, and platform.Secret Detector for Code SnippetsDetect hardcoded keys, tokens, and credential-like strings before sharing code snippets.Password Strength CheckerAnalyze password strength with detailed scoring. Get tips to improve security.