Is It Down or Up?

Network Server-side uptime website http status-code monitoring ping down up

This tool processes your data on the server: whatever you submit here is sent over the network to be processed, then the result is sent back to your browser.

What it does

Enter a URL and this tool makes a real HTTP request from the server to check whether the site is reachable, how long it took to respond, and which exact HTTP status code it returned (200, 301, 404, 500, timeout, connection refused, etc.). This is more reliable than checking from your own browser, since your local network, DNS, or firewall might behave differently than the wider internet.

Try it

How it works

Your browser sends the URL to /api/tools/is-it-down-or-up.
The server (tools/is-it-down-or-up/server.js) makes an HTTP(S) request to that URL directly, with a 10-second timeout.
It reports back:

Up / Down verdict (up = any 2xx–3xx status code)
The exact HTTP status code and status message
The response time in milliseconds
The Location header, if the response is a redirect
The Server header, if present
The specific error (timeout, DNS failure, connection refused...) if the request could not complete at all

Why check from the server instead of the browser?

Browsers block many cross-origin requests via CORS, so a plain client-side fetch() often can't even read the status code of another site.
A server-side check reflects what any visitor on the internet would see, rather than being affected by your local DNS resolver, browser extensions, or corporate proxy.

Notes

Only http:// and https:// URLs are supported.
Redirects are not followed automatically — the tool reports the redirect status code and destination (Location header) so you can see exactly what's happening at each step, rather than hiding it.
A request that fails to connect at all (DNS error, connection refused, timeout) is reported as Down with the underlying error message.