How to use
01
Enter the website URL
Type or paste the address, such as https://example.com; https:// is added if missing. Use the page that fails for you, and add a keyword that should appear on it if you want that checked too.
02
Press Check now
You get a verdict, the status code, the response time, the SSL days left, and a checklist: DNS, reachable from our server, reachable from your browser, and the keyword.
03
Re-check or keep watching
Tick auto re-check, pick an interval and turn on notifications if you like. The history shows uptime and response times and exports as CSV. Checks stop when you close the tab.
Why Website Uptime Checker
- Tells you if a site is up, returning an error, or down, with HTTP status and response time.
- Checks from our server and from your own browser, so you know if it is down for everyone or just you.
- Also checks DNS, the SSL certificate and an optional keyword on the page, in one run.
- Auto re-check every 30 seconds to 5 minutes with alerts, uptime stats and CSV export. Bulk mode checks 20 URLs.
What to do when a site is down
Work from the outside in. The checker already covers the first few steps in its checklist, and the tools named here go deeper on each layer.
- Confirm it is not just you: run this check, then try the site on mobile data or another network.
- Check DNS: run the DNS Lookup on the domain. A missing A record or wrong nameservers after a change or an expired domain will stop the site loading.
- Check the domain itself: a WHOIS Lookup shows whether it expired or carries a hold status.
- Check SSL: the SSL Certificate Checker shows an expired certificate or a name mismatch, which browsers treat as a hard stop.
- Check the server's answer: the HTTP Header Checker shows the status code, redirects and the server or CDN that answered.
- If you use a CDN, see whether the error page comes from the CDN (such as a 52x page from Cloudflare) or from your own server, then check your host's status page and error logs.
HTTP status codes you will see in an uptime check
The status code tells you which layer answered and what went wrong. Codes in the 500s are server-side problems. Codes in the 400s mean the server works but refused or could not find this request.
| Code | Verdict here | What it usually means |
|---|---|---|
| 200 OK | Up | The page loaded normally |
| 301 or 302 | Up | The server redirected to another URL |
| 403 Forbidden | Error | Server is up but blocked the request, often bot protection |
| 404 Not Found | Error | Server is up but this page does not exist |
| 429 Too Many Requests | Error | Rate limiting; the server is up but busy |
| 500 Internal Server Error | Down | The application crashed on this request |
| 502 Bad Gateway | Down | A proxy or CDN could not get an answer from the server behind it |
| 503 Service Unavailable | Down | Overloaded or in maintenance mode |
| 504 Gateway Timeout | Down | The server behind the proxy took too long |
| No response | Down | DNS failed, the connection was refused, or it timed out |
Common questions
How does the website uptime checker decide a site is up or down?
A 2xx or 3xx status counts as up. A 4xx status means the server is online but refused or could not find the page, and a 5xx status or no response at all counts as down. If the server rejects the first HEAD request, the tool retries with a GET before deciding.
Is my site down for everyone if this check says DOWN?
Very likely, if the Reachable from your browser row fails too. Our server and your browser are on separate networks, so two failures in different places point to the site itself. Both are only two locations, though, so an outage limited to one region or provider can still be missed.
Why does the uptime check say ERROR with a 403 status?
403 Forbidden means the server is running but refused our request. Bot protection, a firewall or a CDN security rule often blocks automated checks like this one, while real visitors still get in. Open the site in your browser to confirm.
Why might the uptime check say UP while my browser shows an error?
The problem is then usually on your side: an old DNS answer cached on your device, your network or VPN, a browser extension, or a block in your country. The Reachable from your browser row shows whether your own connection got through. Try another network, such as mobile data, or clear your DNS cache. A page can also load its HTML fine and still break because of a script error.
Why does the uptime checker show the SSL certificate as well?
An expired or broken certificate makes browsers show a full-page warning, which looks like an outage to visitors even when the server is fine. Seeing the days left next to the status helps you rule that cause in or out.
Does the uptime checker keep monitoring my site after I leave?
No. Checks run when you press the button, or at your chosen interval while auto re-check is ticked and the tab is open. Browser notifications work only while the page stays open. Nothing runs after you close it, and no email or SMS alerts are sent. For round-the-clock alerts, use a monitoring service.
What response time should a healthy site show in an uptime check?
Under about 500 ms is a quick answer, and several seconds suggests the server is struggling. The number includes the distance between our server and yours, so a site hosted on another continent will read higher. It measures the server's answer, not the full page load.
Does the website uptime checker test from several countries?
No. Each check comes from our server in one location plus your own browser. If you suspect a regional outage, ask someone in that region to try the site, or use a service that tests from many locations.
What does the keyword check in the uptime checker do?
Type a word or phrase that should always be on the page, such as your shop's Add to cart button. Each check reads the page and reports whether the text was found. It catches a site that answers 200 OK but shows an error message, an empty template or a hacked page.
Can I check website status online here without creating an account?
Yes. There is no sign-up and no limit for normal use. The history lives in the page only and disappears when you leave, so export it as CSV first if you want to keep it.