I have Windscribe VPN Pro and Nord VPN. I tested both with https://ipleak.net/ Nord - ipleak-webRTC detection shows IANA private or special address (private-use) and IANA private or special adress (unique-local). Windscribe - ipleak-webRTC detection shows IANA private or special address (private-use) and a long address with my country and state (I see the same long address without VPN). Does the above info means, Nord is not leaking and Windscribe is leaking? Win 10 Pro 64 Bit Google Chrome 64 Bit VPN Client only, no browser extension
That "long address" is probably IPv6. And yeah, http://ipv6-test.com/I'd say that Winscribe is leaking IPv6. But try https://test-ipv6.com/
Tested with the above mentioned website. Without VPN - Your IPv6 address on the public Internet appears to be (address here) With Windscribe - No IPv6 address detected
Ah, I get it. It's a webRTC leak, and it's showing the link-local (not routed to the Internet) IPv6 address. Which won't show up in https://test-ipv6.com You can check by running "ipconfig /all" in command prompt.
With NordVPN, link-local is there (long address is not there) With Windscribe, long address is there (link-local is not there) ipconfig /all shows the long address as "temporary IPv6 address" Do you mean, both are leaking?
Since I don't need or want IPV6 running anywhere on my systems I find it easier to completely disable it during boot. If my host system kills IPV6 during mount it doesn't matter, its a moot point. BTW -- I do the exact same thing during boot of/on my VM's as well. I take the possibility of a screw up away from any VPN provider or otherwise by a total disable of any IPV6. Sure fire and forget it from that point on.
It's hard to know what's going on when we're using words like "long address" I mean, all IPv6 are long. And @Palancar has a good point. Why not just disable IPv6? In my testing, I did find that NordVPN leaked IPv6. It didn't leak link-local IPv6, but rather the public IPv6 address assigned by my "ISP" (which was, for testing, a private IPv6-enabled VPN). And I tested with https://test-ipv6.com which won't show link-local IPv6, because they're not routed. You only see them when you hit a site that exploits WebRTC to see local addresses. Some VPN services assign their own IPv6 addresses to users. I didn't test Winscribe, but maybe it does. And if it does, that IPv6 will show up in "ipconfig /all". But on the VPN tap adapter, not the lan adapter. So this "long address", is it on tap or lan? Also, does your ISP assign you an IPv6 address? With no VPN client running, what IPv6 addresses do you see with "ipconfig /all"? Is the long temporary IPv6 address there? Or only link-local IPv6? I'm guessing that you don't have a public IPv6 address from your ISP. And that mainly you have a WebRTC leak. Which NordVPN admittedly isn't blocking. So all you have is a link-local IPv6, and the leak test site sees it via WebRTC. And that Winscribe assigns a public IPv6 address, and also prevents your link-local IPv6 address from leaking via WebRTC. So Winscribe seems like the clear winner here. As long as that long temporary IPv6 address is Winscribe's, anyway.
I meant webRTC detection in ipleak. ip detection in ipleak seems fine i.e windscribe IP is detected and IPv6 test not reachable (error). without VPN - ipconfig /all shows IPv6 address (preferred) , temporary IPv6 address (preferred) and link-local IPv6 address (preferred). without VPN - webRTC detection in ipleak shows IP and long IP (long IP shows my country and state) . long IP matches the temporary IPv6 address in ipconfig /all mentioned above. windscribe VPN - webRTC detection in ipleak shows IANA private and long IP (long IP shows my country and state). long IP matches the temporary IPv6 address in ipconfig /all mentioned above. windscribe VPN + AdGuard webRTC block enabled - webRTC detection in ipleak shows IANA private and long IP (long IP shows my country and state). long IP matches the temporary IPv6 address in ipconfig /all mentioned above. webRTC network limiter chrome extension by google enabled - webRTC detection in ipleak doesn't show anything. example long IP - xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx (first 2 blocks are numbers only and rest blocks are numbers & letters).
Why confused? Why you think the extension is not blocking webRTC? webRTC detection in ipleak doesn't show anything if the extension is enabled with or without VPN. I have set to "use my proxy server (if present)" in the extension options.
OK, I was confused. You did say So just use that. And disable IPv6 in your machine, just in case. Or setup a firewall to block all IPv6 traffic.
mirimir, I have Windscribe VPN and Ivacy VPN. When I test Windscribe VPN at ipleak website, everything is fine i.e IPv4 (windscribe ip) is there and DNS (windscribe) is detected. When I test Ivacy VPN at ipleak website, a few servers get IPv4 not reachable and DNS shows 0 server and 100 errors, but internet works fine. Any info?
Not really. Could Ivacy be giving you IPv6 addresses? Otherwise, it's probably just that a server is overloaded, or maybe doesn't reply to pings.
could you post a screenshot of the ivacy test result please? it might help us understand the issue more clearly.
Attached is a screenshot. Ipleak test shows errors. ExpressVPN test shows IP, DNS, etc. https://i.postimg.cc/FRYhG7Kf/i.png
I don't know it is the website issue or not. Now I tried all the servers available in Windscribe VPN and not a single IP not reachable or DNS error. But with Ivacy VPN I get IP not reachable and DNS error for some servers though the internet works fine.
ipleak.net is an airvpn service (powered by airvpn). take a look at the airvpn forum link in my post above, the answer is there.
@imdb I did check the airvpn link you posted for me. As per their forum it seems the website issue. But the confusion is if it is the website issue then why the issue doesn't appear when testing the Windscribe VPN servers. I tested all the Windscribe VPN servers successfully with no IP issue or DNS error.
