Is my website up right now?
Enter an address and we call it straight away from our server in Germany. You get the HTTP status, how fast it responded and whether redirects are involved.
This is a snapshot from one location. It says nothing about whether your site was reachable at three in the morning.
What the check measures
- HTTP status code: 200 means fine, 404 not found, 500 server error.
- Time to first byte (TTFB): how long the server takes to start answering.
- Total time: until the response has been transferred completely.
- Redirects: which hops were involved, for example http to https.
- TLS: whether the connection was encrypted.
How to read the result
Under 300 milliseconds is fast, up to about a second is fine, beyond that visitors start to notice. Consistency matters more than a single value: a site that usually answers in 200 milliseconds and occasionally in four seconds has a problem a one-off check will not show.
An error does not automatically mean your site is down for everyone. DNS issues, a firewall or a block against foreign servers can cause it too.
What the check cannot do
It only looks from the outside and only once. To know whether your site went down last night, or how response times develop over weeks, you need continuous monitoring with history and alerts.
Frequently asked questions
Are internal addresses checked too?
No. Private networks, localhost and similar targets are rejected for security reasons. The target must be reachable from the internet.
How often may I check?
A few checks per minute are fine. Beyond that a limit kicks in so the tool is not abused.
Checking once is good. Monitoring continuously is better: three monitors are free.
Monitor for free