Plain VPN

What WebRTC IP Candidates Mean in a VPN Privacy Check

简体中文

A browser call can list several addresses while it explores ways to connect. A public IP check and WebRTC candidates describe different activity. Learn which kind of address you are seeing before interpreting a result.

About 2 min read

Read each type of candidate

  1. LocalAn address from a device interface, sometimes masked by the browser
  2. MappedA network mapping observed by an external service
  3. RelayAn address supplied by a relay server
ICE provides possible paths for real-time communication.

A candidate is an option. Seeing it in a list does not identify the path a completed call selected. Browser version, policy, and network configuration affect what appears.

Compare your own browser

  1. Note the browser version, connection mode, and intended coverage.
  2. Use a trusted check to compare your public exit and the candidate types shown.
  3. Repeat using the same browser and a permitted baseline. Keep conclusions without exposing raw addresses.
  4. If you need a real call test, use an approved test session without private content.

Do not grant unrelated permissions to a test website. A browser can expose different candidates under different permission states. Use an approved diagnostic method on a managed device.

Investigate the candidate that differs

Start by identifying whether an address is local, mapped, or relayed. For a public candidate, check whether it matches the expected VPN exit or a relay provider. If it appears to match the normal public exit instead, repeat the test and ask the provider to explain what its VPN or extension covers. Separate app traffic can follow different rules.

Keep the result tied to your actual use

Follow the browser and provider documentation for privacy controls. Some calling apps use relays to limit what a peer can see, which can affect the media path and performance. Use an observation like "matches the baseline" when sharing a support note.

Frequently asked questions

Do several addresses prove a leak?

Multiple candidates are part of normal connection setup. Identify their types and compare them with the expected paths.

Can an ordinary IP check replace a WebRTC check?

Each measures a different kind of traffic. Check the behaviour relevant to your own use.

Sources