Skip to content
← All articles

Russia's Internet Blocklist in Numbers: 131,000 Blocked Domains Analyzed (2026)

Short answer. We pulled Russia's official banned-sites registry (Roskomnadzor's EAIS) plus the extended operator blocklists and analyzed them. The official registry holds 131,361 domains; extended operator lists exceed 1.47 million entries. The headline: almost 70% of blocked domains are international (.com and other zones), not .ru. One in five of the world's top sites (19%) is unreachable in Russia — Meta, X, LinkedIn, BBC, Medium, WordPress.com and more.

How we counted

Methodology (fully open, see footer): we aggregated the same authoritative sources public block-checkers use — the antizapret export (a mirror of the official EAIS registry, registered domains) and the antifilter.download extended blocklist (includes subdomains and operator lists). Then we overlaid a sample of the world's top sites. Every figure is reproducible — the engine sits behind our RKN block checker. Snapshot date: June 2026.

Scale of the registry

SourceDomainsWhat it is
EAIS (antizapret)131,361official registry, registered domains
Extended (antifilter)1,470,647+ subdomains, operator lists, IP blocks

131k domains in the official registry — not counting the IPs, subdomains and network ranges that push the real number of unreachable resources into the millions.

Headline: it's not "the Russian web" being blocked — it's the global one

The registry's TLD distribution breaks the "they block Russian sites" stereotype:

ZoneDomainsShare
.com35,07727%
.ru39,28630%
.net5,1504%
.top4,5253%
.org4,0383%
.online3,7653%
other (550+ zones)~39,50030%
Only 30% of blocked domains are in .ru. The other 70% are international — .com, .net, .org and 550+ more TLDs. The RKN registry is first and foremost a filter on the global web, not the Russian segment.

One in five of the world's top sites is blocked

We sampled the most-visited sites worldwide and checked them against the registry. The result — 19% (13 of 67) are unreachable in Russia:

  • Social: Facebook, Instagram, X (Twitter), LinkedIn, Tumblr, Bluesky
  • Media: BBC, Medium, SoundCloud, Dailymotion
  • Platforms: WordPress.com, Patreon

Many of these still "resolve" — DNS returns an IP, the host Ping — but traffic is cut at the operator's DPI layer. So a plain ping or nslookup won't reveal the block: you need a registry check.

Why "the site works for me but my users can't reach it"

A classic case: the owner sees the site up, while some users report it down. Causes:

  • IP / subnet block. RKN blocks an IP, but a CDN (Cloudflare, Akamai) hosts thousands of unrelated sites on it — one "neighbour" lands in the registry, everyone on that IP suffers.
  • Domain-level DPI block — the operator cuts by SNI/Host while DNS stays "clean".
  • Regional variation — operators roll out blocks unevenly.
# Check whether a domain is in the registry (antizapret export)
curl -s https://antizapret.prostovpn.org/domains-export.txt | grep -ix "example.com"

# See if the site sits on a "dirty" CDN IP
dig +short example.com   # → IP → check the IP against the blocklist

What a site owner should do

  1. Check the domain and IP with the RKN block checker — registry status + network signals in 10 seconds.
  2. If the site is on a shared CDN IP, that's "block-by-neighbour" risk; consider a dedicated IP.
  3. Put the domain on availability monitoring so you learn about a registry hit first, not from your customers.

Where does the data come from?

From the antizapret export (a mirror of Roskomnadzor's official EAIS registry) and the antifilter.download extended blocklist — the same sources independent block-checkers use. We publish aggregate statistics only, not the lists themselves.

Why 131k in the registry but "millions of blocks"?

131k is the registered-domain count of the official registry. With subdomains, IPs and network ranges (extended lists exceed 1.47M entries) the real number of unreachable URLs is an order of magnitude higher.

The site "pings" but users can't open it — is it blocked?

Possibly. A domain/SNI DPI block doesn't affect DNS or ping — the host "resolves" but traffic is cut. Check against the registry, not with ping.

Can I check my own site?

Yes — the RKN block checker uses the exact same sources as this study.

Methodology. Sources: antizapret (a mirror of Roskomnadzor's EAIS registry, registered domains) + antifilter.download (extended blocklist with subdomains and operator lists). The TLD distribution is computed over the official registry. The "world's top" overlay is a 67-site sample of the most-visited sites by category. Date: June 2026. Reproducible via our RKN checker.

Check your website right now

Check your site →
More articles: Monitoring
Monitoring
INP in Core Web Vitals: The 2026 Metric
15.06.2026 · 37 views
Monitoring
Real User Monitoring: The Complete Guide to RUM vs Synthetic Monitoring
16.03.2026 · 184 views
Monitoring
Cron Job Monitoring with Dead Man's Switch
14.03.2026 · 230 views
Monitoring
The Four Golden Signals of Monitoring
22.06.2026 · 24 views