✅Hostname: ec2-3-135-190-238.us-east-2.compute.amazonaws.com
✅Browser: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
✅Language: Unknown
Loading...
Testing is done by loading small images from corresponding websites. Delay values are for reference only and will be smaller in reality.
Status: Loading...
URL: https://www.google.com/favicon.ico
Status: Loading...
URL: https://github.githubassets.com/favicon.ico
Status: Loading...
URL: https://www.youtube.com/favicon.ico
Status: Loading...
URL: https://chat.openai.com/favicon.ico
Status: Loading...
URL: https://twitter.com/favicon.ico
Status: Loading...
URL: https://www.facebook.com/favicon.ico
Status: Loading...
URL: https://www.linkedin.com/favicon.ico
Status: Loading...
URL: https://www.amazon.com/favicon.ico
WebRTC often uses UDP. If you see your real IP under “Public IP,” your proxy/VPN isn’t covering WebRTC traffic.
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
Local IP: …
Public IP: …
A DNS leak means that when you are connected to a VPN/proxy, your domain name resolutions are still done through your local ISP, thus posing a risk of DNS leaks. The method to test for DNS leaks involves accessing a newly generated domain name to detect which regional DNS exit you are resolving through. If the endpoint region returned matches your local service provider's region, there is a risk of DNS leakage. In this case, you may need to modify your VPN/proxy settings.
Please wait while we fetch DNS records.