Leak Check Checklist: IP, DNS and WebRTC Before You Log In

Prepare a clean test

Use a fresh browser profile. A clean profile helps separate connection checks from extensions, saved settings, and site data carried over from other activity.
Keep the test profile free of unnecessary extensions. Some extensions can change network behavior or expose information, making results harder to interpret.
Check the proxy or VPN settings before opening account sites. Confirm that the intended connection is enabled and that the browser is configured to use it.
Avoid signing in during the test. Checking connection behavior first helps prevent account activity from relying on a setup you have not verified.
Record what settings are active. A brief note makes it easier to identify what changed if a later check shows a different result.

Check the public address shown by a reputable network-checking service. It should reflect the route you intended to use rather than your ordinary connection.
Review the reported general location. Location estimates can be imprecise, but a result that clearly conflicts with your intended route deserves investigation.
Compare results across more than one independent check. Different services may interpret location or network details differently, so one result alone may not explain a mismatch.
Look for signs that both direct and routed connections are active. A mixed result can mean some traffic is bypassing the proxy or VPN.
Pause if the visible address is unexpected. Resolve the discrepancy before using the profile for legitimate accounts, and follow each platform’s rules.

Run a DNS leak check while the proxy or VPN is active. The check can show whether domain lookups appear to follow the intended route.
Compare the DNS results with the connection setup. Results associated with an unrelated network may indicate that name requests are taking a different path.
Check the browser’s secure DNS setting. Browser-level DNS options can affect where lookups go, even when a system-level proxy or VPN is enabled.
Review operating-system DNS settings if results remain unclear. Network settings outside the browser may influence requests and should be consistent with the setup.
Repeat the check after changing DNS options. A setting change can alter routing, so an earlier result may no longer describe the current configuration.

Check whether WebRTC reveals a local or public address. WebRTC supports real-time browser features, but its network details may not follow the same route as ordinary page traffic.
Review the browser’s privacy controls for WebRTC. Use settings that are appropriate for your needs and compatible with the sites and services you use.
Retest after changing WebRTC controls. The change should be verified in the same profile and connection setup you plan to use.
Check for local network details in the result. An unexpected address can indicate that browser features are exposing information not shown by an ordinary address check.
Avoid assuming that hiding one address hides every browser signal. A browser profile can share other technical details, so connection checks are only one part of privacy and account safety.

Repeat the full check after configuration changes. Proxy settings, DNS options, browser updates, and extensions can all affect how traffic is handled.
Test from the profile you intend to use. Results from a separate browser or profile may not represent its settings.
Recheck after switching networks or connection modes. A setup that behaved as expected before a switch may route requests differently afterward.
Keep profiles clearly organised and access-controlled. Good management reduces accidental use of the wrong profile and helps protect account data.
Stop and investigate any unexplained mismatch. Do not rely on a configuration until its behavior is understood, and use accounts only in ways permitted by the relevant platform.