It too passed the leak tests with no problems. The IP address does indeed correspond to Miami, FL. It turns out that the database that uses to map an IP address to a physical location, is not 100% accurate. Although you can see in the VPN window on the left that I am connected to a server in Miami, USA, on the right is claiming the IP address if the server I am connected to is in Italy. Note: You might have noticed something odd in the image above. SecureLine VPN doesn’t support IPv6, so of course that test will fail. Look on the right and you will see that my virtual IP address is the one that is seeing.ĭon’t worry about the IPv6 “error” in the preceding image. If you look closely on the left (circled in red), you can see my Virtual IP address (at the time I was writing this). The following image shows the Windows VPN in action. The VPN protects against DNS leaks by forcing DNS requests to go to the VPN’s own DNS servers through the encrypted VPN tunnel. The Avast SecureLine VPN apps didn’t show any problems: no leaks, no crashes. We ran the SecureLine VPN through our standard set of VPN tests, looking for things that didn’t work right. As you can see in the image above, the optimal location the VPN selected was the Miami, USA server location from among 57 possible locations.
