IP data will be checked from 6 sources. If there is only 1 IP stack currently, sources without data will show as empty.
Testing is done by loading small images from corresponding websites. Delay values are for reference only and will be smaller in reality.
Awaiting Test
Awaiting Test
Awaiting Test
Awaiting Test
Awaiting Test
Awaiting Test
Awaiting Test
Awaiting Test
WebRTC often establishes connections directly via UDP. If the test returns your real IP, it means your proxy settings do not cover these connections.
stun:stun.l.google.com:19302
Awaiting Test or Connection Error
stun:stun.nextcloud.com:443
Awaiting Test or Connection Error
stun:us-0.turn.peerjs.com
Awaiting Test or Connection Error
stun:global.stun.twilio.com
Awaiting Test or Connection Error
stun:stun.cloudflare.com
Awaiting Test or Connection Error
stun:stun.miwifi.com
Awaiting Test or Connection Error
stun:stun.qq.com
Awaiting Test or Connection Error
stun:stunserver.stunprotocol.org
Awaiting Test or Connection Error
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.
DNS Endpoint: Awaiting Test
Endpoint Region: Awaiting Test
DNS Endpoint: Awaiting Test
Endpoint Region: Awaiting Test
DNS Endpoint: Awaiting Test
Endpoint Region: Awaiting Test
DNS Endpoint: Awaiting Test
Endpoint Region: Awaiting Test