Service operator: ZlexVPN. Contact: [email protected].
Sorry, the Zlex protocol is not open source. We welcome questions about learning, research and other uses. Contact us by email or support ticket to ask what information we can provide.
Learning and responsible research
We permit good-faith, non-commercial, non-destructive reverse engineering and security research for learning or research on lawfully obtained Zlex clients in local environments or isolated laboratories you own or are authorized to test. You do not need our prior approval for research within this scope.
Penetration testing, vulnerability scanning or other security testing of Zlex production systems, including our websites, APIs and VPN nodes, requires our prior written authorization and an agreed scope. Testing another person's systems requires that owner's permission; our local research permission does not grant access to their devices, accounts, traffic or infrastructure.
Research must not access or disclose other people's data, compromise their accounts, bypass authentication, billing or service limits to obtain unauthorized access or unpaid service, deploy malware, disrupt service or damage data. If you unexpectedly encounter someone else's information, stop that activity and report the issue without retaining or sharing that information.
Please contact us privately about vulnerabilities before publishing sensitive technical details. Share only the minimum evidence needed to explain the issue, using test data whenever possible. Do not send passwords, device private keys or other users' information.
About the distributed client core
Our currently distributed VPN client core is not deliberately protected with VMProtect, code virtualization, code obfuscators or an additional executable-encryption wrapper. Normal release optimizations, symbol stripping, installation packaging and encryption used by the VPN protocol or credential storage are separate from this statement.
Source availability and commercial permission
The Zlex protocol and proprietary client components are not open source. This research permission does not promise source-code access or grant rights to redistribute our proprietary code, branding or commercial products.
Commercial use of reverse-engineering results or proprietary Zlex code, commercial redistribution, and commercial licensing of the protocol require a separate, detailed license agreed with ZlexVPN in advance. This does not change ordinary use already allowed by your service subscription, rights under applicable law, or rights granted by third-party open-source licenses.
Nothing in these terms restricts research, interoperability, reverse engineering or other rights that applicable law does not allow us to restrict. Third-party open-source components remain subject to their own licenses; this policy does not replace or reduce those permissions or obligations.
For research information, authorization for production testing or a commercial license, email [email protected] or open a support ticket.
This statement uses the same research permissions and boundaries as our Terms of Service.