WebRTC Fingerprint

WebRTC capabilities and IP leakage checks. Detect peer connection support and potential network exposure signals.

Live signal

Runs only when you ask. This check contacts Google STUN servers, which can observe your IP. Results stay in this tab.

Ready to inspect this signal.

You will receive observed values, API availability, and a copyable JSON result. A single signal cannot identify a person.

What CreepJS reports

After you start the check, creates a peer connection with Google STUN servers and reports candidate addresses, connection state, codec capabilities, and support flags.

How to interpret it

Inspect public and local candidates separately. Rerun after changing your VPN or WebRTC policy to compare what the browser exposes.

Limits

STUN servers can observe your IP. No returned public candidate does not prove that a VPN prevents leaks. Candidate gathering is bounded and browser policy may conceal addresses. A single signal does not identify a person.

Test the signal

Keep the live result for comparison, change one relevant setting, then run again in the same tab. Compare the fields before interpreting a changed signature.

Reviewed: 2026-10-29.