My site works for me but not for clients in Russia
Walk the cause tree in order: (1) domain/URL in the EAIS registry; (2) your CDN IP blocked because of a neighbour; (3) regional differences (Moscow opens, St. Petersburg does not, or vice versa); (4) DNS propagation after a record change; (5) a geo-firewall on your side (you drop Russian IPs yourself). The first two are RKN blocks; the rest are config and routing. Check top to bottom — this is diagnosis, not circumvention.
Below: details, example, related guides, FAQ. This is diagnostic guidance for resource owners using the public EAIS registry — not circumvention advice.
Free online tool — Rkn tool: instant results, no signup.
Details
- Step 1 — registry. Check the domain and exact URLs in EAIS. If a record exists, it is a block — proceed to the official owner-side delisting procedure.
- Step 2 — CDN IP. If the domain is not in the registry but is unreachable from RU, find which IP it resolves to. A shared IP of a large CDN (Cloudflare etc.) can be blocked because of another site on the same address.
- Step 3 — region. Availability from Moscow and St. Petersburg can differ: different operators, routes and filtering points. “Works in one city, not the other” is normal for IP/DPI blocks.
- Step 4 — DNS. After changing A/AAAA/NS records, old entries are cached at operators until the TTL expires. Some clients still hit the old IP — check propagation.
- Step 5 — your side. A geo-firewall, a “block country RU” WAF rule, a CDN geo-tier limit, or your provider’s sanctions policy can drop Russian traffic regardless of RKN. Check your own rules and hosting policy.
Example
# Diagnostic tree (top to bottom)
# 1) Registry + RU-node availability
https://enterno.io/en/rkn
# 2) Which IP the domain resolves to (shared CDN?)
dig +short shop.example.com A
dig +short shop.example.com AAAA
# 3) Regional differences (Moscow vs St. Petersburg) — external nodes
# enterno.io /rkn shows availability across RU nodes
# 4) DNS propagation after a record change
dig +short @8.8.8.8 shop.example.com A
dig +short @77.88.8.8 shop.example.com A # Yandex DNS
# 5) Your side: look for geo blocks in WAF/CDN/nginx
grep -ri 'geoip\|country\|GeoIP2\|allow.*deny' /etc/nginx/ 2>/dev/nullRelated
Why teams trust us
How it works
Enter domain or IP
Check RKN registry
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
Best Practices
Monitor availability in Russia
HTTP monitor from Moscow — be first to know about blocking.
Sign up freeLearn more
Frequently Asked Questions
Where do I start if the domain is not in the registry?
Jump straight to step 2 — the CDN IP. The most common “invisible” cause of RU unreachability with a clean registry is a collateral block on a shared IP. Then check the geo-firewall on your own side.
Why does it open in Moscow but not in St. Petersburg?
The cities are served by different operators with different filtering points and routes. IP and DPI blocks roll out unevenly. Treat it as a diagnostic signal: check the IP and the registry rather than assuming randomness.
Could the problem be on my side?
Yes, and this is missed most often. A “block country” WAF rule, a CDN-tier geo limit, or a hosting sanctions policy will drop Russian traffic independently of RKN. Step 5 is mandatory.
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.