Free website tool
Is It Down? Website Status Checker
Check if a website is up or down right now: HTTP status code, response time and redirects, tested live from our server.
How the status check works
We send a real request to the URL from our server, follow up to 10 redirects, and record the status code and how long each hop took. If the connection fails, you see why: the domain doesn’t resolve, the server refused the connection, the certificate is invalid or it simply didn’t answer within 15 seconds.
It’s one check from one place, run when you press the button. It tells you whether the site answers right now; it can’t tell you how long it has been down, or whether it’s down in other countries.
When a site is down
- Couldn’t find the domain: check the domain hasn’t expired (try the WHOIS lookup) and that its DNS records exist.
- Connection refused or timed out: the web server or host is offline. Check the hosting control panel.
- HTTP 500: the application is crashing. The error log on the server says why.
- HTTP 502 or 504: the CDN or proxy is fine, the server behind it isn’t.
Frequently asked questions
- Is the website down for everyone or just me?
- If this checker reaches the site but you can't, the site is up and the problem is on your side: your Wi-Fi or mobile network, a stale DNS cache, a browser extension, or a block by your company network. If the checker can't reach it either, the site is down or unreachable from the internet at large.
- What do the HTTP status codes mean?
- 2xx means the page loaded normally and 3xx is a redirect to another URL. 4xx means the server is up but refused or couldn't find the page (403 Forbidden, 404 Not Found). 5xx means the server itself failed: 500 is an application error, 502 and 504 mean a proxy or CDN couldn't get an answer from the origin server, and 503 usually means overload or maintenance.
- What is a good response time?
- Under about 600 ms for the server to answer is fast; up to roughly 1.8 seconds is acceptable. Response time here is time to the server's first answer, including any redirects. The page still has to download and render after that, so a slow server response makes every page view slow.