Skip to content

How to check if a website is blocked in Russia

Key idea:

Run three independent checks: (1) the EAIS registry — Roskomnadzor’s official register at eais.rkn.gov.ru or its public mirrors; (2) availability from Russian nodes (Moscow + St. Petersburg, different ISPs); (3) the IP — whether your CDN address was caught in a neighbour’s block. If the domain is in the registry AND unreachable from RU nodes, it is blocked. Reachable for you but not for clients in Russia is the classic symptom — check all three layers, one source is never enough.

Below: details, example, related guides, FAQ. This is diagnostic guidance for resource owners using the public EAIS registry — not circumvention advice.

Check your site →

Details

  • EAIS is the unified register of prohibited information maintained by Roskomnadzor. Lookup by domain, URL and IP is open at eais.rkn.gov.ru; public exports are mirrored by aggregators (antizapret).
  • Four block types exist: by domain, by specific URL, by IP address and by subnet mask — an IP block hits every site sharing that address.
  • Checking from a single vantage point is unreliable: operators apply blocks with a 1–3 day lag and differently (DPI, DNS spoofing, null-route). You need different ISPs and cities.
  • “It opens fine for me” almost always means you are not on a Russian network — your ISP is not enforcing EAIS filtering. That does not prove availability for clients in Russia.
  • The /rkn tool on enterno.io combines all three: registry status (multi-source), availability from RU nodes and a CDN-neighbour IP-block hint.

Example

# 1. Registry status + RU availability in one request
https://enterno.io/en/rkn  (enter your domain)

# 2. Official Roskomnadzor registry (manual check)
https://eais.rkn.gov.ru/  → search by domain / URL / IP

# 3. Which IP the domain resolves to (for CDN-neighbour checks)
dig +short example.com A

# 4. Availability from external nodes (indirect — RU routes)
curl -sS -o /dev/null -w 'http=%{http_code} time=%{time_total}s\n' https://example.com/

# Read it as: 'in registry + unreachable from RU nodes' = blocked;
#             'not in registry + unreachable only from RU' = check CDN IP block.

Related

Roskomnadzor RegistryCheck in official registry
ISP DNS FilteringBlocking at Russian ISPs
AS-Level CheckIP or subnet-level blocking
Block ReasonDecision number and grounds

Why teams trust us

RKN
official registry
ISP
ISP DNS filtering
AS
IP/subnet check
Free
no signup

How it works

1

Enter domain or IP

2

Check RKN registry

3

Get status and reason

Why check for RKN blocking?

Roskomnadzor maintains a registry of blocked sites. If your domain or IP is in the registry, Russian users won't be able to access the site. The check shows status and reason.

RKN Registry

Direct query to the prohibited sites registry — domain, URL, or IP.

RKN DNS Check

Simulate queries via provider DNS (Rostelecom, MTS, SkyDNS).

IP Blocking

Check if your hosting IP address or subnet is in the registry.

Reason and Number

If blocked, show decision number, date, and legal basis.

Who uses this

Business

Russia accessibility check

DevOps

hosting IP control

Developers

new hosting verification

SEO

site visibility monitoring

Common Mistakes

Thinking only "bad" sites are blockedSites end up in the registry due to shared hosting IPs used by thousands of sites.
Not checking hosting providerIf hosting changes IPs — check the new address for registry presence.
Ignoring subnet blockingSometimes an entire /24 subnet is blocked. Check not just your IP but neighbors too.
Not monitoring regularlyYou can end up in the registry due to your hosting neighbors. Monitor automatically.

Best Practices

Use a dedicated IPYour own IP reduces the risk of being blocked alongside other sites.
Set up monitoringAn HTTP monitor will be first to notice unavailability for Russian users.
Check after hosting changeNew IP may be in the registry. Check before migration.
Document IP addressesKnow all your hosting IPs — this speeds up diagnostics when issues arise.

Monitor availability in Russia

HTTP monitor from Moscow — be first to know about blocking.

Sign up free

Learn more

Frequently Asked Questions

How does the official registry differ from the antizapret aggregator?

eais.rkn.gov.ru is Roskomnadzor’s primary source with per-record lookup. Aggregators (antizapret, antifilter) mirror the official export and are handy for bulk/programmatic checks, but update with a lag and are not individually complete — that is why /rkn takes the union of several sources.

Why might a site be unreachable from Russia without a block?

Many causes besides EAIS: a neighbour IP block on a shared CDN, a geo-firewall on your side (you yourself drop Russian IPs), routing issues at a specific operator, or hosting overload/outage. That is why you check the registry, availability and the IP together.

How long does a block last?

As long as the grounds exist. The record stays in the registry until the violation is removed and a delisting request is filed (for automatic/extrajudicial blocks) or until a court decision is reversed/complied with. Removal is a separate official procedure for the resource owner.

Try the live tool that powered this guide

Free plan — 20 monitors, 5-minute checks, no card required. Upgrade for 1-minute interval and multi-region monitoring.