Website Uptime Checker
Find out whether a site is really down or whether the problem is on your side. The checker sends three requests from our server, measures each stage of the connection and tells you plainly: up, down, unstable, or up but returning an error.
- Encrypted connection
- No sign-up
- Free to use
How to use Website Uptime Checker
- Enter the address of the website.
- Select Check if it is up.
- Read the verdict at the top.
- Look at the three test requests to see the status code and how long DNS, connection, encryption and the first response took.
Website Uptime Checker features
Clear verdict
Up, down, unstable or reachable-with-error, with the reason in plain words.
Three requests
Repeating the test separates a single hiccup from a real outage.
Stage timing
DNS lookup, connection, TLS handshake, first byte and total time for each request.
Failure diagnosis
Distinguishes a domain that does not resolve, a server that refuses connections, a timeout and a server error.
Independent vantage point
The requests come from our server, outside your network, device and DNS cache.
No history kept
A one-off check: nothing is stored and no account is needed.
When to use Website Uptime Checker
- Deciding whether to restart your router or wait for a site to come back.
- Confirming an outage before contacting a hosting provider.
- Checking that your own site is reachable from outside after a DNS or server change.
- Verifying that a site returns a proper status code and not just a blank or error page.
Website Uptime Checker FAQ
The checker says the site is up, but I cannot open it. Why?
Then something between you and the site is the cause. Common culprits are an outdated entry in your DNS cache, a firewall, VPN or content filter, a browser extension, or a regional routing problem at your provider. Try another network, such as mobile data, or another browser.
What does “reachable but returns an error” mean?
The server accepted the connection and replied, so the machine and the network are fine, but the reply was an error such as 404 or 403. The page you asked for is missing or blocked, while the rest of the site may work.
What is the difference between down and a 5xx error?
A site is down in the strict sense when no connection can be made. A 500, 502, 503 or 504 response means a server answered but the application behind it failed or is overloaded. For a visitor the effect is the same, so both are reported as down, with the reason given.
Is this an uptime monitor?
No. It runs when you press the button and does not watch the site afterwards. A monitoring service checks every minute or so from several locations and alerts you. Use this tool for a quick second opinion.
Why might the result differ from other locations?
The test runs from one place. A site can be reachable from our server and unreachable from another region when the fault is in a network path, a CDN node or a geographic block.
What do the timing columns mean?
DNS is the time to translate the name into an address. Connect is the time to open the connection. TLS is the encryption handshake. First byte is how long the server took to start answering, and Total includes downloading the response and following any redirects.
Narrowing down why a site will not load
When a page refuses to open, the cause can sit anywhere along a chain: your device, your local network, your provider, the DNS system, the network between you and the site, the site's server, or the application running on it. A check from a second location is the quickest way to split that chain in two. If an outside server reaches the site without trouble, everything from the site backwards is fine and the search moves to your end.
The stage timings narrow it further when the site is slow or failing. A long or failed DNS step points to the domain's name servers or an expired domain. A connection that times out means the server is offline, overloaded or blocking the request. A fast connection followed by a long wait for the first byte means the server is up but the application is struggling to produce the page, which is typical during traffic peaks or database problems.
Repeating the request matters because single measurements mislead. One failed request can be a dropped packet. Three failures in a row are an outage. One success and two failures suggest a server pool with unhealthy members, a restart in progress or rate limiting, which is why the verdict in that case is unstable.
For your own site, an external check after every infrastructure change is a good habit. It is easy to test a new server from the machine you configured it on and forget that the firewall, the DNS record or the certificate only work from the inside.