Log In Get Started
Free tool

Does your site open from other countries

You see your own site from your own country and your own network — and that is all you know about it. This page opens it from our servers in different countries and shows what the site answered each of them: the status code, the latency and where a redirect took it.

Enter an address — the check takes a few seconds.

Ready to check

The vantage points are our own servers. The list is fetched from the server when you press "Check".

What is measured here, and what is not

One thing is measured: whether your address opened from a particular server of ours, in how many milliseconds and with which status code. That is enough to catch the commonest cases — the site is down, the domain does not resolve, the certificate has expired, a redirect leads astray, or it answers only for you because it is cached in your network.

What is not measured is blocking. Filtering in China, Iran or Russia is built so that it is invisible from outside: it fires on the path from a local user to the site, and our node stands somewhere else on that path. So "our server in Tokyo opened your site" does not mean "the site opens for everyone in Asia", and we do not write it that way.

What your own network blocks is a separate question, answered by the network check. What does not work where, by country — the blocking map.

Site does not open from everywhere?

Then your readers do not see it from everywhere either. 404 VPN gives you an exit through our nodes — a convenient way to look at your own site with someone else’s eyes.

How it works →

FAQ

guest@404vpn:~$ cat site-reach-faq.md
[01] $ Is this a check for blocking in China? ▸
> No, and promising that would be a lie. We show exactly what we measured: our node in such a country opened your address like this. The Chinese filter is built in a more complicated way — it behaves differently in different provinces and with different carriers, and you cannot judge it from one point outside. What is useful, and visible at once, is "the site answers none of our points at all".
[02] $ What does "the name does not resolve" mean? ▸
> The domain does not turn into an address: either it has a typo, or the DNS records are not set up, or the domain has expired. That is a state before any availability — it never even gets as far as the site.
[03] $ The site answered 403 or 503 — is it working or not? ▸
> It answers, and that is the main thing: the network reaches it. What exactly it answers is a question for the site itself or its bot protection: our probe comes from a data centre, and some sites deliberately rebuff such requests. If one country gets 200 and another 403, it is most likely the site’s own rules rather than blocking.
[04] $ One point is silent, the others answer. Is that blocking? ▸
> Perhaps — or perhaps our node was unavailable at that moment, in which case the row says exactly that: "the vantage point is not answering". That is our problem, not your site’s, and we call it by its name rather than passing it off as unavailability.
[05] $ Do you store the addresses I check? ▸
> No. The request goes through our server, because a browser cannot check another country, but neither the address nor the result is written to a database or a log — the server answers and forgets.