Website Status Checker
Check whether a website is up and how fast it responds.
Looks up live data What you enter is sent to our server to fetch live results from public sources. Results are cached briefly. A Cloudflare Turnstile bot check runs when you press the button (it loads a script from challenges.cloudflare.com and may show a short challenge).
A Cloudflare Turnstile bot check runs when you press the button (it loads a script from challenges.cloudflare.com and may show a short challenge).
Report a problem with this tool
About this tool
Enter a URL to find out whether a website responds. Our server requests the page, follows up to 3 redirects, and reports whether it is up (any response below 500 counts, including 403 and 404, because the server answered), the final HTTP status and how long the response took. Checking from an outside server helps you tell a site outage from a problem with your own connection. If the request fails entirely, for example because the host does not exist, the connection times out after 12 seconds or there are more than 3 redirects, the tool reports the site as down along with the error message. A result with an HTTP status can be reused for up to a minute; connection errors are never cached. A bare domain is treated as https://.
How to use it
- Enter a domain or full URL.
- Press Check.
- Read whether the site is up, the status and the response time.
- If it is down, run it again in a minute to rule out a brief blip.
Down for everyone or just you?
The check runs from our server, not from your device. If it reports the site as down, the problem is most likely on the site's side. If it reports the site as up but the page does not load for you, the problem is probably between you and the site.
- Open the site in a private window or another browser to rule out extensions and stored cookies.
- Switch networks, for example from Wi-Fi to mobile data, to rule out your router or internet provider.
- Clear your DNS cache or restart your router. An old or blocked DNS answer can send you to the wrong address.
- Check whether a VPN, firewall or company network filter is blocking the site.
What the status code tells you
- 200 OK
- The page loaded normally.
- 403 Forbidden
- The server answered but refused the request. Often bot protection that blocks data-center traffic, so the site may still work in a browser.
- 404 Not Found
- The server is up, but this exact URL does not exist. Check the path, or test the home page.
- 429 Too Many Requests
- The server is up and rate limiting. Try again later.
- 500 Internal Server Error
- The site's own code or configuration failed. Counted as down.
- 502, 503 or 504
- A proxy, load balancer or CDN in front of the site could not get a good answer from it, or the site is overloaded or in maintenance. Counted as down.
- Status 0 with an error
- No HTTP answer at all: the name does not resolve, the connection was refused, or it timed out.
Common problems
- Reported down but it loads for you
- The site may block requests from data-center servers, or it may only be slow from our location. Try again shortly.
- A 403 or 404 is shown as up
- The server answered, so it counts as up; the status code shows that the page itself is missing or blocked. Only network errors, timeouts and 5xx responses are reported as down.
- Reported down with "Too many redirects"
- The tool follows at most 3 redirects. Enter the final URL directly, or trace the chain with the Redirect Checker.
- The tool refuses the address
- Localhost, private ranges and unusual ports are blocked.
Frequently asked questions
Does this monitor my website for downtime?
No. It is a one-off check each time you press the button. For alerts when a site goes down, use an uptime monitoring service that checks on a schedule.
Can I check the HTTP status code of one specific page?
Yes. Enter the full URL including the path. The status shown is the one after redirects; to see each redirect hop and its code, use the Redirect Checker or the HTTP Status Code Checker.
What does the response time measure?
The time from our server sending the request until the response headers arrived, including any redirects. It does not include downloading the whole page, and it depends on the distance between our server and the site.