It's not quite as straight forward as you're making it out to be.
Securex wrote:And VPN encrypt all your traffic unlike proxy.
There's two ways of reading this sentence, so I'll address both;
Interpretation 1: "A VPN catches all your traffic, a proxy only some of it."
For both VPN and Socks proxies, they only transport (and encrypt) what you tell them to. You can pass mostly any type of common traffic through both, the only difference here is that a VPN usually has a 'catch everything' setting by default.
Interpretation 2: "A VPN encrypts traffic, a proxy does not."
This is really a matter of configuration. There's no technical reason a VPN has to encrypt traffic, and in fact you can turn encryption off for almost all VPN implementations. For socks proxies, as far as I know it depends entirely on the transport layer's encryption. For example if you're doing Socks5 off the back of SSH, it'll be encrypted. But again, there is nothing enforcing encryption to happen here.
To make a long story short; It's not a case of "one encrypts traffic, the other does not." It depends entirely on the configuration in both cases.
Securex wrote:- Unparalleled traffic encryption with a 4096-bit key
Key size is not the only parameter that matters. You can have the worlds biggest key but if it's for a broken encryption algorithm it's perfectly useless.
On the other side, not all algorithms need equally large keys. For some algorithms a 4096-bit key might be a reasonable suggestion, but for others it's way, way overkill and will probably require way too much processing power overhead to be useful as a VPN anymore.
But even that's not the end of the story. You should also look at forward secrecy. Really this means that it should not be possible for someone to decrypt captured traffic at some later point if the server's key is ever compromised. And this depends entirely on the encryption algorithms being used.
So the moral of this story is; look at the type of encryption used by the vpn/proxy provider and check if it meets the standards you need.
Securex wrote:- Double and Triple VPN chains in a different countries.
This is really a case of "use only when needed". If you're just trying to get out of a specific network or country, there's usually really no reason to chain your vpns/proxies. If you want to be really sure someone isn't able to track you down from the remote side, chaining might be a good additional layer of obstruction.
Also note that chaining isn't the same as layering. Chaining will have your traffic decrypted and re-encrypted at every link, meaning that might be a weak point where it can be more easily intercepted. Layering means you wrap the first vpn/proxy with the second, then wrap that whole thing with the third etc. There won't be any weak links where the traffic is unencrypted that way, but it is much harder on your endpoint as it has to now do encryption for all your layers instead of just for the first link in your chain.
But both these methods increase the overhead on your traffic with each extra link/layer. Latency will be higher and throughput will be lower. This is why it's usually not a good idea to do if it's not needed.