What does “down for everyone” mean?

It means the site responded neither from our external vantage point nor from your browser, even though the domain resolves. The cause is almost always on the site's side: the server is overloaded, down or under maintenance. There is nothing to do on your end but wait for the owners to restore it.

What does “only for you” mean?

The external point sees the site but your browser does not. So the site itself works, but something is blocking your connection specifically: provider blocking, a DNS failure, a firewall, a browser extension or a temporary network problem. Changing DNS, disabling extensions or turning on a VPN often helps.

How accurate is the browser check?

Because of the CORS security rule, a browser does not report the HTTP code of another site, so the local check only shows whether a connection succeeded. That is a reliable “does it open for you” signal, but without a response code. We get the full HTTP status from the external point.

Do you check the site from several countries?

For now the external check runs from one point (our server) plus your browser — enough to tell “down for everyone” from “only for you”. The response format is designed to add nodes from other countries; that is a planned enhancement of the tool.

The site works for everyone but is blocked for me — what do I do?

If a site is reachable externally but not for you, a provider block or regional restriction is likely. Turn on LiMP VPN: traffic goes through an encrypted tunnel and a server in another country, and domain-list blocking stops applying. Then check the site again.

Do you store the addresses I check?

No. The external check is a single request from our server, and the local one runs in your browser. We do not log or store the site addresses or the check results.

Is the site down — for everyone or just you?

Enter a site address and we check it from two sides at once: from our external vantage point on the internet and straight from your browser. The result tells you whether the site is down for everyone or the problem is only on your side — for example provider blocking, DNS or your network.

The check runs from our server and from your browser. We do not log or store the addresses you check.

The external check is a single request from our server; the local one runs in your browser. We do not log or store the addresses you check.

How the check works

We look at the site from two independent sides and compare the results — that shows exactly where the problem is.

External vantage point

Our server on the internet requests the site directly: resolves the domain, opens a connection and gets the HTTP status. This answers whether the site is reachable at all.

Your browser

In parallel we check availability from your network. If the site is up externally but not for you, the problem is local: provider, DNS or blocking.

A clear verdict

We compare both points and explain the result in plain words: down for everyone, only for you, or the domain does not resolve at all — and what to do about it.

When it helps

A site suddenly won't load

Quickly tell whether the site is down for everyone or it is your internet, before rebooting the router and calling your provider.

Suspected blocking

Check whether a site is blocked specifically by your provider — if it works externally but not for you, a VPN helps.

Your own site or service

Confirm your site is visible from the internet, not just from the office network, and see the server response time.

Ready to try?

Download LiMP VPN for free and feel the difference within a minute.

Download for AndroidGet the Chrome extension

“Is a site down for everyone or just me” — how to tell

When a site stops opening, the first thing to know is where the problem is: on the site itself or in your connection. If the site is down for everyone, all you can do is wait for the owners to fix it. But if it works for others and only fails for you, the cause is in your network, provider, DNS or a block — and that can often be fixed yourself.

Our tool checks the site from two sides at once: from an external vantage point on the internet (our server) and straight from your browser. By comparing both results it gives a clear answer instead of guesswork.

What the check shows

HTTP status — the server's response code (200 is fine; 404, 500, 503 and others point to a problem on the site's side).
Response time — how fast the server replied from the external point and from your network.
Availability per point — separately for the external server and your browser.
Domain resolution — whether the site name resolves to an IP address; if not, an HTTP check is impossible.

Why a site may fail only for you

If the external point sees the site but your browser does not, the cause is almost always local. The most common cases: the provider blocked the resource, DNS fails (the site does not resolve for you specifically), a firewall or browser extension interferes, or there is a temporary network glitch. Provider blocks and regional restrictions are bypassed with a VPN: traffic goes through an encrypted tunnel and a secure server, so restrictions on the provider's side no longer apply.

Why the check cannot see the HTTP status from the browser

For security reasons a browser does not let scripts read the HTTP code of another site (the CORS rule). So the local check honestly shows only the fact: whether a connection from your network succeeded or not. We get the full HTTP status from the external point — our server, where there are no such limits. Together these two signals give the “everyone or just you” answer.

How LiMP VPN helps with unreachable sites

If a site is blocked by your provider or available only in another region, LiMP VPN routes your traffic through an encrypted tunnel and a server in the country you need. Your provider only sees the connection to the VPN, not the site addresses, so domain-list blocks stop working. Your real IP address and location are hidden as well.