DNS records
Make sure the A/AAAA records are the same on all of the domain's name servers and do not point to an old server. An expired domain also shows up as “no DNS”.
Website availability check from different countries
Enter an address and 8 points will check the site at once: three in Russia (Moscow and Saint Petersburg, two different networks) and five abroad — Germany, the Netherlands, the USA, Singapore and Japan. You will see where the site opens, where it does not and at which stage the connection breaks.
Only the site's home page is checked, by domain name. The result is ready in 5–30 seconds.
Checks are run by nodes of the open check-host.net network: only the site name is passed to them, without path or parameters. The result is kept in our server's memory for 5 minutes so that repeated checks do not load the site. We keep no log of checks.
If you own the site
The site does not open from some country? Go through the common causes before contacting your host.
Certificate
An expired or mismatched certificate breaks the site in every country. Turn on auto-renewal and make sure the intermediate certificate is in the chain.
CDN and bot protection
CDNs and WAFs sometimes block whole countries or data centres. Review country and ASN rules in your CDN panel and the protection event log.
Hosting geo-block
Some hosts block certain countries by default. If the refusal (HTTP 403) comes only from some countries, start with the hosting settings.
Operator-side filtering
If connections from Russia break while setting up the secure channel but everything works elsewhere, the cause may lie in operators' networks. Your site itself is fine.
Monitoring
A one-off check is a snapshot. To learn about problems before your users do, set up regular availability monitoring from several regions.
How we check
Every point goes through the same steps, and the conclusion compares Russian points with foreign ones.
DNS
The point asks its resolver for the site's IP addresses. If the address seen in Russia differs from the global one and leads to another network, it is flagged separately.
TCP connection
The point connects to the server on port 443 (or 80 for sites without HTTPS). This shows whether the server answers at all.
HTTPS and the page
The home page is requested. If the connection exists but the page never arrives, the break happens at the secure-channel or request stage.
Retry and quorum
A quick failure is retried once. A point that did not answer itself is excluded. We only draw a conclusion when enough points have answered.
Certificate
We check the site's HTTPS certificate separately. An expired certificate is a fault of the site, and we do not confuse it with an access restriction.
Honest limits
A data-centre point is not your home connection. We show facts for each point and never claim a site is “blocked” or “listed in a registry”.
Why check website availability from different countries
A site can open fine for you and still be unavailable for part of its audience: because of a CDN failure, a hosting geo-restriction, a DNS error or traffic filtering by operators. A check from a single point will not show that — you need a view from several places at once.
The tool checks the site in parallel from three points in Russia and five abroad and compares the answers. That shows whether the site is down everywhere, only from Russia or, conversely, only from other countries.
How to tell a site is restricted from Russia
If foreign points receive the page and Russian points do not, the check shows where the connection breaks: the name does not resolve, the server does not answer, the connection is reset or it breaks while setting up the secure channel. These are observable technical signs.
The check does not claim a site is “blocked” or “listed in a registry”: such a statement needs an official source. We only show what is visible from each point.
“Does not open” vs. “restricted”
- Does not open anywhere — the problem is on the site's side: the server is down, overloaded or the domain is misconfigured.
- Does not open only from Russia — there are signs of access restriction on the path from Russian networks, or site settings for Russian addresses.
- Does not open only from abroad — usually a geo-restriction set by the site owner or their host.
- Opens, but the browser complains — the certificate has expired or is issued for another name: the site is faulty but reachable.
FAQ on availability and blocking
Run the check: if every point gets the site's response, it works and the cause is on your side — ISP, DNS, Wi-Fi or browser extensions. If the site answers nowhere, the problem is the site itself. To compare with your own connection, use the “Is a site down for everyone or just me” tool.
“Does not open” is a fact: the point did not get the page. “Blocked” is a claim about the cause and about who restricted access. The check only sees facts per point and the stage where the connection breaks, so it does not call a site blocked.
There are several possible causes: access restriction on the path from Russian networks, site settings for Russian addresses (often an HTTP 403), CDN rules or bot protection. The break stage is a hint: a 403 is usually set by the site, while a break during the secure-channel setup points to the network.
It means the site opens from Russia but not from most foreign points. Most often such a restriction is set by the site owner, their host or CDN — for example, to close access from countries without customers or to cut data-centre traffic.
Check points live in data centres, not at home ISPs or mobile operators. Filtering and routes differ between operators, so a site that opens from our point may not open for you — and vice versa.
Check DNS records and the certificate, then country and ASN rules in your CDN, WAF and hosting. If an HTTP 403 comes only from some countries, it is almost always a setting on your side. If connections from Russia break during the secure-channel setup while the site is healthy, the cause is outside your server.
We keep no log of checks. The result is held in server memory for 5 minutes so that repeated requests do not load the site, and is then deleted. The checks themselves are run by nodes of the open check-host.net network — only the site name is passed to them.
Yes. The check makes a normal home-page request, just like a visitor's browser, with no address scanning or load. A repeat within 5 minutes is served from the saved result. If you own a site and do not want it checked, write to support@limpvpn.com.