DNS resolution
Check in progressDetecting the recursive DNS servers used by this browser.
Network diagnostics
See the public IP websites receive, its location and network type, then check for DNS, WebRTC, and proxy-header leaks.
Checking
Checking
No critical leak signals found so far. 2 checks still running
Check a single SOCKS5, HTTP, or HTTPS proxy against Socks5.io controlled test endpoints.
Paste a proxy URL or enter host:port:username:password.
These are network-level signals only. Account history, browser fingerprint, behavior, and payment details may affect platform decisions.
| Use case | Status | Signals detected | |
|---|---|---|---|
| AI platforms OpenAI, Claude, and Gemini network signals | Checking | Checking | |
| Social platforms TikTok, Instagram, and X network signals | Checking | Checking | |
| Commerce and payment Amazon, PayPal, and Stripe network signals | Checking | Checking |
Review the items that could make this network setup inconsistent.
Location and network labels can differ between providers. Compare source details before treating a classification as conclusive.
No proxy indicator headers detected
This summary is shown for the current session. It is not stored as a persistent cross-session identifier.
Detecting the recursive DNS servers used by this browser.
Checking browser connection candidates.
Create a privacy-protected troubleshooting report.
How it works
WebRTC leakage occurs when browser real-time connection data exposes a network address that does not match the expected proxy or VPN path.
Read the WebRTC leak guideA DNS leak occurs when domain lookups do not follow the expected proxy or VPN path.
Read the DNS leak guideSocks5.io cross-checks the public IP observed by its controlled endpoint with available network metadata and browser-side connection signals. Unavailable checks are reported as unavailable rather than inferred.