The popularity of VPNs grows as privacy is revalued. Here are some tips to provide an extra level of security for your connection.
If it is a niche product used by a minority of users, in recent times we are witnessing a growth in the popularity of VPNs (virtual personal networks), as privacy is revalued as well as preserved by the Internet user we leave here a series of tips and tricks to provide an extra level of security to your connection to any of these services.
If the VPN fails
If on any occasion, while our equipment is connected to the Internet, our VPN fails, our IP address would be exposed and visible to all kinds of legal and illegal snoopers. That could be catastrophic if we weren’t in front of the PC to immediately cut the connection (and still, we probably wouldn’t be fast enough).
Therefore, the best solution is to configure our equipment to automatically deactivate any connection attempt that is not being made through the VPN IP. We can do that by establishing specific rules in our firewall, but we talk about a process that is too complex for people with basic knowledge, so it is advisable to use some software that automates it:
- VPNetMon serves to close specific programs at the same time that it stops detecting the IP of our VPN, which it constantly monitors. These programs will not have time to make an unsecured connection. VPNetMon works on Windows.
- VPNCheck has functions equivalent to those of the previous software. Only two circumstances differentiate them: that in addition to specific programs you can close any Internet connection, and that in addition to Windows it is available for GNU / Linux.
You can also use a VPN client that includes this functionality as standard, of course. This list includes Private Internet Access (Windows / Mac), CyberGhost (Windows), Mullvad (Windows / Mac / Linux) and Hide My Ass. And if you only use your VPN to download torrents, you can use a torrent client that also includes this functionality, such as Vuze.
If there is ‘DNS leak’
Typically, when we use VPN services, all our traffic passes through this private network, but sometimes there is a phenomenon called “DNS leakage”: our team stops using the DNS servers provided by the VPN operator and starts using the default of our usual connection. Sometimes, the trigger for this vulnerability is a slight delay in the DNS of the VPN, or in its inability to resolve any fully qualified domain name.
The Pro version of the VPNCheck includes a function to detect these leaks, but you also have the DNSLeakTest.com online test and the corresponding instructions available here.
If our VPN provider does not have our full confidence, we can use 2 simple solutions:
- Use a VPN through another VPN: connecting with the second one without disconnecting the first one.
- Use a VPN through TOR: If your provider betrays your trust, your privacy will not be compromised at any time … even if your performance is. You have a tutorial here.