Is It Down?
Checks if a URL is up from our server — is it down for everyone or just you?
The URL you type is sent to the Nexinon server at check time, used only to test that URL (following up to 5 redirects) — nothing is stored, and the page content (HTML) is never read, only the HTTP response.
What this tool checks
This tool tests, from the Nexinon server, whether the given URL responds to an HTTP request — following up to 5 redirects, if any. The result is one of three states: "up" (the server responded, even with something like a "page not found" error), "degraded" (the server responded, but with an error on its end) or "down" (no response arrived at all — for different reasons, each explained separately in the result).
"Down" from where, exactly?
A site can be reachable for most people and still not respond to this check (or the other way around) — the internet isn't the same place for everyone. Things like an ISP blocking a specific domain, DNS that hasn't propagated to your region yet, or a momentary hiccup between the Nexinon server and the target can make this result differ from what you see in your own browser. This tool answers "is it down for the Nexinon server, right now" — strong evidence, but not a universal certainty.
How the verdict is decided
Any HTTP response received already proves the server is reachable — including a "404 not found" error, which counts as "up" (the server exists and responded, it just doesn't have that page). A "500" or "503" error becomes "degraded": the server is standing, but something went wrong on its end. Only when no response arrives at all — the name doesn't resolve, the connection is refused, the time runs out, TLS fails, or redirects never end — is the verdict "down".
Frequently asked questions
Because the server responded — it's online, reachable and working well enough to say "I don't have that page". That's quite different from a site that responds with nothing at all. "Up" here means reachable, not "every page works".
Yes, and that's not a bug in the tool — it's the nature of the internet. Regional blocks, DNS that hasn't propagated everywhere yet, or a momentary hiccup between the Nexinon server and the tested site can make the two results differ. See "'Down' from where, exactly?", above.
Because they're quite different situations for whoever is diagnosing something: a site returning a 500 error is standing (the problem is in the application), while a site that responds with nothing at all might have an expired domain, a powered-off server, or a network failure. Lumping both into a generic "down" would hide that difference.
No. Only the HTTP response (status, redirect header) is used to decide the verdict — no HTML is ever parsed or stored.
Because the final destination is what matters: if the given URL redirects (e.g. to HTTPS, or to another domain), the response a real visitor would get after all the hops is what actually reflects whether the site is reachable. The limit is 5 redirects — more than that also counts as "down" (a loop that never ends).
A few seconds per attempt (each redirect hop pays that time individually). A relatively short wait like this is deliberate: a genuinely up site responds well before that in the vast majority of cases.