Website down checker
Enter a site and this tool requests it from our server, follows any redirects, and reports whether it answered, the status code and how long it took. If it loads here but not for you, the problem is most likely on your side.
It’s for the moment a site won’t load and you need to know whether to wait, restart your router or wake up your host. It checks from one location, so it confirms an outage rather than mapping one.
Free with a ShipScroll account.
How to use the Website Down Checker
- Enter the site address, with or without https://.
- Press Check.
- Read the status: up, a server error, a refusal, or no answer.
- If it’s up here but not for you, try another network or clear your DNS cache.
What the results mean
| Result | Meaning |
|---|---|
| Up, 200 | The site answered normally |
| Up, 401 or 403 | The server is running but refused us. Some sites block automated checks |
| Up, 404 | The server is running but this page doesn’t exist |
| Server error, 5xx | The server answered but something on it failed |
| No answer | Nothing replied within 5 seconds: the server, DNS or network is down |
When it’s up here but down for you
- Try the site on mobile data instead of Wi-Fi, to rule out your network.
- Your device may be holding an old DNS answer, especially after a domain move. Clearing the DNS cache or waiting helps.
- A browser extension, VPN or firewall can block one site.
- Some sites block visitors by country, so it may be down only where you are.
Questions
Where does the check run from?
From ShipScroll’s server, as a single request with no cookies. A site can be up from one place and down from another, so this confirms whether it responds rather than mapping an outage worldwide.
Why does it say “refused” when the site loads for me?
The site answered with 401 or 403, which usually means it blocks automated requests. It’s running, it just didn’t want to talk to our checker.
Can it watch my site and alert me?
No, it checks once when you ask. For alerts, use an uptime monitor that checks every few minutes from several places.
Why is the response time different each time?
Response time depends on the server’s load, caching and the route between us and it. Check a few times before reading much into a single number.
Related tools
- Redirect CheckerFollow every hop from an address to the page it ends on, with each status code.
- HTTP Header CheckerSee a page’s response headers, with notes on security, caching and indexing.
- DNS LookupList a domain’s A, AAAA, CNAME, MX, NS and TXT records in one place.