SharkBank
Golden Member
- Joined
- March 2, 2026
- Messages
- 150
- Reaction score
- 7
- Points
- 18
- Thread Author
- #1
1. Verify Your IP Address and Geolocation
Objective: Confirm that the IP and location match what you expect (e.g., the location of your proxy or VPN).
What to look for: Correct country, region, and internet service provider name. There should be no discrepancy between the IP location and the desired location.
2. Test for DNS Leaks
Objective: Ensure that your DNS requests are not going through your actual internet service provider.
What to look for: DNS servers should match your desired location/provider, not your home internet service provider.
3. Test for WebRTC Leaks
Objective: Ensure that your real IP is not exposed through WebRTC.
What to look for: Only your desired IP should appear—no local or internet service provider IPs.
4. Verify the Uniqueness of Your Browser Fingerprint
Objective: See how identifiable your browser is based on technical attributes.
What to look for: A fingerprint that blends in with many others is better than an extremely unique one. 5. Check your IP's fraud reputation/score
Objective: Ensure your IP is not flagged as suspicious or high-risk.
What to look for: Low fraud score (below 20 is generally considered "clean").
Websites and how to use them
whoer.net
Run the test and check the IP, location, internet service provider (ISP), DNS servers, and WebRTC status.
Scroll down to see the anonymity score.
Check for DNS/WebRTC leaks.
Use the DNS Leak Test and WebRTC Leak Test pages separately.
Confirm that no unexpected IP or DNS server is displayed.
amiunique.org
Click on “View my browser fingerprint” to see how unique your configuration is.
Analyze the uniqueness percentage — the lower the percentage, the more you camouflage yourself.
coveryourtracks.eff.org
Run the test to see if your browser is “unique” or “non-unique” and if the tracking protection is effective.
Check the fingerprint resistance section to identify vulnerabilities.
ipqualityscore.com/ip-reputation-check
Enter your IP to see your fraud score, proxy/VPN detection, and risk level.
Aim for a low score and no “high risk” indication.
When you type a website name (like google.com) into your browser, your device needs to find the correct IP address to connect. The system sends a request to a DNS server, which works like a phone book, translating the domain name into an IP address. This communication occurs before any actual connection to the website, allowing your device to know where to send the data.
A DNS leak occurs when your device bypasses the VPN or SOCKS proxy and sends DNS requests directly to your internet service provider's DNS servers instead of using the encrypted tunnel. This can happen due to incorrect VPN settings, operating system behavior, or IPv6 leaks. When a DNS leak occurs, your internet service provider can see which websites you are trying to access, even if the actual traffic is encrypted by the VPN. This exposes your identity and browsing habits, defeating the purpose of using a VPN or SOCKS for privacy.
To avoid DNS leaks, make sure your VPN has DNS leak protection enabled, use a VPN with its own DNS servers, or manually configure your device to use secure DNS providers (such as Cloudflare or Google DNS). Testing for leaks through sites like DNSLeakTest.com can confirm whether your real IP and DNS requests are exposed. When using SOCKS5, remember that it does not encrypt DNS by default, so combining it with a VPN or forcing DNS through a proxy is necessary to achieve complete anonymity.
Objective: Confirm that the IP and location match what you expect (e.g., the location of your proxy or VPN).
What to look for: Correct country, region, and internet service provider name. There should be no discrepancy between the IP location and the desired location.
2. Test for DNS Leaks
Objective: Ensure that your DNS requests are not going through your actual internet service provider.
What to look for: DNS servers should match your desired location/provider, not your home internet service provider.
3. Test for WebRTC Leaks
Objective: Ensure that your real IP is not exposed through WebRTC.
What to look for: Only your desired IP should appear—no local or internet service provider IPs.
4. Verify the Uniqueness of Your Browser Fingerprint
Objective: See how identifiable your browser is based on technical attributes.
What to look for: A fingerprint that blends in with many others is better than an extremely unique one. 5. Check your IP's fraud reputation/score
Objective: Ensure your IP is not flagged as suspicious or high-risk.
What to look for: Low fraud score (below 20 is generally considered "clean").
Websites and how to use them
whoer.net
Run the test and check the IP, location, internet service provider (ISP), DNS servers, and WebRTC status.
Scroll down to see the anonymity score.
Check for DNS/WebRTC leaks.
Use the DNS Leak Test and WebRTC Leak Test pages separately.
Confirm that no unexpected IP or DNS server is displayed.
amiunique.org
Click on “View my browser fingerprint” to see how unique your configuration is.
Analyze the uniqueness percentage — the lower the percentage, the more you camouflage yourself.
coveryourtracks.eff.org
Run the test to see if your browser is “unique” or “non-unique” and if the tracking protection is effective.
Check the fingerprint resistance section to identify vulnerabilities.
ipqualityscore.com/ip-reputation-check
Enter your IP to see your fraud score, proxy/VPN detection, and risk level.
Aim for a low score and no “high risk” indication.
When you type a website name (like google.com) into your browser, your device needs to find the correct IP address to connect. The system sends a request to a DNS server, which works like a phone book, translating the domain name into an IP address. This communication occurs before any actual connection to the website, allowing your device to know where to send the data.
A DNS leak occurs when your device bypasses the VPN or SOCKS proxy and sends DNS requests directly to your internet service provider's DNS servers instead of using the encrypted tunnel. This can happen due to incorrect VPN settings, operating system behavior, or IPv6 leaks. When a DNS leak occurs, your internet service provider can see which websites you are trying to access, even if the actual traffic is encrypted by the VPN. This exposes your identity and browsing habits, defeating the purpose of using a VPN or SOCKS for privacy.
To avoid DNS leaks, make sure your VPN has DNS leak protection enabled, use a VPN with its own DNS servers, or manually configure your device to use secure DNS providers (such as Cloudflare or Google DNS). Testing for leaks through sites like DNSLeakTest.com can confirm whether your real IP and DNS requests are exposed. When using SOCKS5, remember that it does not encrypt DNS by default, so combining it with a VPN or forcing DNS through a proxy is necessary to achieve complete anonymity.
