Send a URL and get back its status code and HTTP headers - the first check when a page behaves oddly or a redirect chain needs untangling. Free.
Half the questions about a broken page are answered by the status code: a 404 where a 200 was expected, a 301 pointing at the wrong place, a 503 that says the server is up but refusing. This bot gives you that plus the response headers, which is where caching, security and redirect problems show themselves.
It is a working tool for anyone who owns a site - a developer checking a deploy, an SEO specialist tracing a redirect chain, a support person confirming that a page really is down and not just down for one visitor. The author is named in the bot's own description.
Free
| Criterion | Weight | Points | |
|---|---|---|---|
| Functionality | 25 | 7 / 10 | |
| Reliability & speed | 15 | 8 / 10 | |
| Popularity & trust | 15 | 6 / 10 | |
| Price & free tier | 10 | 10 / 10 | |
| Usability | 10 | 9 / 10 | |
| Safety & privacy | 10 | 8 / 10 | |
| Freshness | 5 | 7 / 10 | |
| Localization | 5 | 10 / 10 | |
| No intrusive ads | 5 | 10 / 10 | |
| Score | 100 | 78.5 |
It shows what one server sees. That rules out your own network, but a region-specific outage needs a monitoring service with several locations.
Caching, security policy and the redirect target all live there, so a page that looks fine can still be misconfigured in a way only the headers reveal.