Current public IP
The address comes from the current HTTPS request. With a proxy or VPN enabled, it should show the exit address rather than your ISP address.
Free network tool
Check my IP and possible WebRTC leaks
See the address used to open this page, then run a local WebRTC candidate check on demand. The tool does not contact a third-party STUN server or store the result.
Your public IP
Current connection address
…· the tool does not store this result
WebRTC check
Runs only when requested
The check uses local WebRTC candidates only and does not contact a third-party STUN server. An exact DNS leak test requires dedicated DNS infrastructure.
Local WebRTC check
The browser is checked only after you press the button. We distinguish another public address, a local address, and a protected mDNS name.
No fake DNS verdict
An exact DNS leak test needs a dedicated diagnostic DNS domain. Until that infrastructure exists, the page does not present a guess as a result.
Practical guides
From a successful check to a correct setup
Use these concise guides to choose a protocol, prepare credentials, and handle retries without unnecessary load.
Common questions
How can I tell whether my proxy or VPN works?
Compare the displayed IP with the address shown without the proxy or VPN. If it changes and WebRTC does not expose a different public IP, this check found no obvious leak.
Why does WebRTC show a .local address?
Modern browsers may replace a local IP with a temporary mDNS name. This prevents the page from seeing the device's exact local address.
Is this a complete anonymity test?
No. It checks the current IP and local WebRTC candidates only. Browser fingerprinting, cookies, accounts, and the exact DNS route are separate concerns.
Need a ready-to-use mobile proxy?
Review the published plans and choose an available Russian mobile proxy in the client portal.