VPN and Proxy Rules (self-SNI)

If a VPN or proxy uses SNI, serverName, target, dest or fallback to disguise or redirect a TLS connection, the domain and the target HTTPS resource must belong to the Client or be under the Client's lawful control. Using other parties' domains and resources without such a right, including domains of banks, government bodies and telecom operators, is prohibited. An ordinary HTTPS website, a legitimate reverse proxy and ordinary outbound HTTPS requests are not prohibited by this rule.

Addendum of 4 November 2026: domains in SNI, serverName, target and dest must not contain "vpn" or "vless" in any letter case, including in subdomains (for example, vpnkuduzo.ru or vless.example.com). Such domains are not allowed even if they belong to the Client. This does not apply to ordinary HTTPS websites.

Addendum of 6 November 2026: domains under mooo.com and sslip.io, including their subdomains, are also not allowed in SNI, serverName, target and dest.

A violation is established from current data taken together: the active VPN or proxy configuration, its link to a running process and port, the domains and addresses it specifies, DNS and TLS checks, and an exact match to the Client's server. A single DNS response, a third-party certificate, an inbound ClientHello, a timeout or an old record is not enough. Passwords, private keys and traffic contents are not needed for the check.

When a violation is confirmed, the specific server may be suspended automatically, with its disks and data kept for the remediation period. The Client receives a notice stating the server, the grounds and how to fix it. The account and the Client's other services are not blocked. An ambiguous check result is passed to a staff member and is not treated as a violation.

At the Client's request, the server is started for 24 hours to fix the issue; the period runs from the confirmed start, and the exact end time is given to the Client. Before it ends, the Client reports the fix in a ticket, stating the server, their own domain and the changed settings (without passwords or keys). A fix report, a dispute or a check error pauses further measures until reviewed. Once the fix is confirmed, the incident is closed.

Addendum of 6 November 2026: for remediation, the server is started once for 1 hour from the confirmed start; no second start is provided. If a fresh check after that period confirms the violation, the server stays suspended with no further access. Disks, data and the account are kept. Periods granted before this date remain valid until they end.

If, after that period, a new check confirms the violation persists, the fix is not confirmed and there is no pending request or dispute, service for the server may be terminated and the server and its disks deleted irreversibly. The cost of such a service is not refunded to the extent permitted by applicable law.

The deletion and non-refund terms in section 4 apply to orders and paid renewal periods placed on or after 3 November 2026, and to violations arising in such periods. Previously opened incidents and already paid periods are not moved under them.