---
title: "WebRTC leak"
description: "Which addresses a peer connection reveals. Obfuscated local names are the protection, not the leak."
canonical: "https://scalebrowser.net/check/webrtc"
last_modified: "2026-10-04T12:05:52.000Z"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://scalebrowser.net/llms.txt
> Use this file to discover all available pages before exploring further.

one check

# What WebRTC gives away

Two things are worth measuring here, and only one of them is usually shown. The local addresses matter far less than the comparison: does WebRTC see the same public address your web traffic goes out over?

## What this one page cannot tell you

Whether a specific site would use WebRTC at all, and what it would do with the result. We also do not probe your local ports over WebRTC: one widely used checking page does, to guess at installed software, and it guesses wrong.

The interesting part is usually not a single value but the disagreement between two. [The full check](https://scalebrowser.net/check) reads all five layers and shows you where they contradict each other.