# KIZYAK VPN 4.0: A Free Subscription Feed for Russia's White and Black Lists

> KIZYAK VPN 4.0 is a collection of free VLESS, VMess, Shadowsocks, and Hysteria2 configs aimed at bypassing Russian internet restrictions, including the strict white list that only allows a few domestic sites. It works as a raw subscription feed, not a client, and its value depends entirely on the survival of its public servers.

**Maskkost93/kizyak-vpn-4.0** — Надоело смотреть на "соединение..." в телеграме? Бесит баннер "Адрес не найден"? Мы просто убираем все БС и ЧС в сторонку, чтобы ты получал свой интернет без вопросов. Отдельное спасибо igareck/vpn-configs-for-russia

- Repository: https://github.com/Maskkost93/kizyak-vpn-4.0
- Website: https://maskkost93.github.io/kizyak-site/
- Stars: 57 · Forks: 3
- Language: Unknown
- License: not declared
- Published: 2026-08-21 · Updated: 2026-08-21 · Language: en
- Canonical page: https://hysenlabs.com/projects/maskkost93-kizyak-vpn-4-0

## What This Project Actually Is

KIZYAK VPN 4.0 is not a VPN client or a server. It is a GitHub repository that publishes raw text files containing subscription links for free proxy configurations. The README describes it as a collection of VLESS, VMess, Shadowsocks, and Hysteria2 configs, tested for bypassing both black lists and white lists imposed by Russian internet providers. The target user is someone in Russia who cannot reach Google, Telegram, or YouTube because their ISP either blocks specific sites (black list) or only allows a small set of Russian domains (white list). The project explicitly credits igareck/vpn-configs-for-russia as a source. It is a feed, not a product. You take the raw link, paste it into a client like v2rayNG or Karing, and the client fetches the list of servers. The project's own value is the curation and testing of those servers, not the software that connects to them.

## Black Lists vs White Lists: Two Different Problems

The README makes a clear distinction between two censorship regimes. A black list blocks specific sites, leaving everything else open. A white list, which the project describes as typical of strict mobile internet, blocks everything except a handful of Russian sites like Yandex, Gosuslugi, VK, Ozon, Sber, and Mail.ru. The project offers different subscription files for each case. For black lists, it recommends kizyakbeta6BL.txt, which contains a mix of protocols. For white lists, it recommends kizyakbeta7.txt or kizyakbeta6.txt, which are mostly VLESS and use CIDR or SNI-based circumvention. The mechanism for white list bypass is described in the FAQ: when an operator blocks all IPs except a few white ranges, the project uses those same white IPs to tunnel traffic. That is a specific technical approach, and it is the only way the project claims to break a full white list. The practical implication is that you must choose the right file for your network type, or the configs will not work at all.

## How to Get It Running: Commands and Config Keys

The setup is entirely subscription-based. You do not install anything from this repository. The README gives a five-step process: download a client, copy a raw link, add the subscription in the client, enable auto-update every 2 to 3 hours, and select the server with the lowest ping. The actual raw links are plain URLs. For example, the black list file is https://raw.githubusercontent.com/Maskkost93/kizyak-vpn-4.0/refs/heads/main/kizyakbeta6BL.txt. The white list file is https://raw.githubusercontent.com/Maskkost93/kizyak-vpn-4.0/refs/heads/main/kizyakbeta7.txt. There is also kizyakbeta6.txt as a fallback. The README specifies that auto-update should be set to 120 to 240 minutes, because public servers die quickly. There are no config keys to edit manually; the client handles parsing. The project also provides mirror links via GitHack, GitLab, Codeberg, and SourceHut, plus a Yandex Translate proxy for cases where even raw GitHub is blocked. That is the complete operational surface: copy, paste, refresh.

## The Security Warning About Local Proxies

The README contains a notable security section. It states that starting in 2026, Russian applications may scan your local proxy. This is a concrete warning about a real attack surface: many VPN clients run a local proxy on your device, and any local app could connect to it if there is no authentication. The project recommends using Karing, Happ, or v2rayNG with login and password enabled for the local proxy. It explicitly recommends against Hiddify, citing a problem with localhost. This is not a theoretical concern. If you use a public config, the remote server is untrusted, and your local proxy is a gateway. The README also suggests using a separate device or profile for VPN activity, free of Russian software. This is the most practical security advice in the entire project. It does not guarantee that the public servers themselves are safe, only that you should limit exposure on your own machine.

## Why Configs Die and What That Means for You

The README answers the question 'Why do configs die in a day?' with a blunt explanation: public servers are quickly found and blocked. That is the core limitation of this project. The entire model depends on a constant churn of fresh servers, which is why the auto-update interval is so short. If you do not enable auto-update, your subscription will become stale within hours. If you do enable it, you still depend on the project maintainers to keep adding new servers. The README also notes that in one region one config works, in another region a different one works. That means you may need to try multiple configs manually. This is not a set-and-forget tool. It is a scavenger hunt. The project's own FAQ admits this. For a user who wants a stable, long-term VPN, this is the wrong tool. For a user who needs a free, temporary connection and is willing to monitor and switch, it might be sufficient.

## Client Compatibility and the Localhost Problem

The README includes a table of recommended clients and their status across Android, Windows, and iOS. v2rayNG is marked as excellent on Android but unsupported on Windows and iOS. Karing and Happ are marked as excellent on all three platforms. NekoBox works on Android and Windows but without localhost protection. V2BOX is Android-only. v2rayN is Windows-only. Hiddify is marked as having a problem with localhost and is not recommended. This table is a practical guide, but it also reveals a trade-off. The clients that support inbound authentication, like Karing and Happ, are the ones the project trusts for security. The ones that lack that protection, like NekoBox, are more convenient but risk exposing your local proxy. The README does not explain how to enable authentication in each client, so you will need to consult the client's own documentation. The project's recommendation is clear: if you care about the local proxy risk, choose Karing or Happ.

## Alternatives and How They Differ

The project credits igareck/vpn-configs-for-russia as a source. That is a direct alternative: a similar subscription feed for Russian censorship bypass. The difference is that KIZYAK VPN 4.0 appears to focus specifically on white list bypass using CIDR or SNI techniques, while the original may cover a broader set of scenarios. Another alternative is a commercial VPN service, which offers stable servers and customer support but costs money and may be blocked more aggressively. A third alternative is running your own server on a VPS, which gives you full control and no dependence on public churn, but requires technical knowledge and a payment method. The trade-off is clear: KIZYAK is free and easy but unreliable; a commercial service is reliable but not free; a self-hosted server is reliable but not easy. The project's own FAQ says it has no monetization plans, so the free aspect is a deliberate choice, but it comes with the cost of constant maintenance.

## Maintenance, License, and What to Verify First

The repository has no listed license, which is a legal red flag. You cannot assume you have the right to redistribute or modify the configs. The README says the project is always free and has no monetization plans, but that is a statement of intent, not a license. The last push was on 2026-04-23, and there are recent releases, so the project is actively maintained. However, the maintenance burden is on the maintainers to keep adding servers, and on you to keep updating your subscription. There is no guarantee of uptime or support. Before adopting this project, verify that your VPN client supports subscription auto-update at 120 to 240 minute intervals. Also verify that the raw URL you use is reachable from your network, and have the mirror links ready. Finally, check the client's settings for local proxy authentication and enable it. If you cannot do that, the project itself warns you not to use it. That is the boundary of this tool: it is a free, ephemeral feed, not a secure infrastructure.

## Conclusion

Adopt KIZYAK VPN 4.0 if you are in Russia and need a free, quick way to test whether any public config can pierce your ISP's white or black list, especially on a mobile connection. Do not use it as a long-term or security-critical solution: the configs are public, unauthenticated, and die quickly. Before relying on it, verify that your VPN client supports subscription auto-update at 120 to 240 minute intervals, and prefer clients like Karing or Happ that allow inbound authentication for the local proxy. Also check the mirror links (GitHack, GitLab, Codeberg) if GitHub is blocked. The project has no license, so treat the configs as experimental and do not assume any legal or maintenance guarantees.

## FAQ

### How do I add a kizyak-vpn-4.0 subscription to my client?

Copy the RAW link for the file matching your situation, add it in your VPN client as a new subscription, group or remote config, and set the auto-update interval to 120 to 240 minutes. Then pick the server with the lowest ping.

### Which kizyak-vpn-4.0 client works on both Windows and iOS?

Karing, Happ and Hiddify are all marked as supporting Android, Windows and iOS. Hiddify is also flagged as having a localhost problem and not recommended, leaving Karing and Happ as the clients noted as having authorisation.

### Why do kizyak-vpn-4.0 configs stop working after a day?

Because public servers are found and blocked quickly, so the configurations there expire within about a day. That is why auto-update is set every two to three hours rather than once a week, and why the working config differs by region.

### How does kizyak-vpn-4.0 get past a white list?

By CIDR. When an operator blocks everything except a few permitted ranges, the tunnel is built over those same permitted addresses. The documentation calls this the only way to break a total block.

## Sources

- [Official documentation](https://maskkost93.github.io/kizyak-site/)
- [Official README](https://github.com/Maskkost93/kizyak-vpn-4.0#readme)
- [Project repository](https://github.com/Maskkost93/kizyak-vpn-4.0)
- [Release notes](https://github.com/Maskkost93/kizyak-vpn-4.0/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/maskkost93-kizyak-vpn-4-0