WebRTC can gather local, mDNS, and sometimes public candidate addresses for peer-to-peer communication. This checker inspects the candidates your browser exposes and highlights leak risk without adding a third-party STUN lookup.
Creating a local peer connection and reading ICE candidates.
What is a WebRTC leak
WebRTC lets browsers create real-time peer-to-peer audio, video, and data sessions. To do that, the browser gathers ICE candidates that describe possible network paths.
Modern browsers often replace local host addresses with mDNS names, but leaked public candidates or stable local signals can still contradict a proxy profile and help risk systems link sessions.
Read the WebRTC glossaryKeep WebRTC policy aligned with the assigned proxy and account environment.
Keep browser sessions from leaking unexpected local or public network context.
Launch each profile with proxy, timezone, language, and browser network behavior pointing in one direction.
GekkoLogin keeps WebRTC behavior, proxy context, storage, and browser fingerprints separated per account profile.