Status and speed
The HTTP status code and how many milliseconds the answer took.
Monitor
Protect
Manage
By role
Security
Renewals
Monitoring
Free tool · No signup
Check whether a site is responding right now. You get the HTTP status code, the response time, every redirect on the way and the final response headers.
No domain handy?
Lookups run live and are not stored.
Every result is pulled live, so you see the state of the domain right now.
The HTTP status code and how many milliseconds the answer took.
Each hop in the chain with its own status, so slow or looping redirects show.
Server, content type and security headers on the final response.
| Code | Meaning | Usual cause |
|---|---|---|
| 200 | The page loaded | Normal |
| 301 / 302 | Redirect to another URL | Moved page, http to https, www to non-www |
| 403 | The server refuses the request | Firewall, bot rule or permissions |
| 404 | Page not found | Wrong URL or deleted page |
| 500 / 502 / 503 | Server or upstream error | Application crash, overload or maintenance |
| No response | Connection or DNS failed | Server down, DNS broken or expired certificate |
A domain such as example.com is checked over https.
Each hop shows its status and time. Long chains slow every visit.
A site can be up from here and down elsewhere. Multi-region monitoring settles it.
This tool checks from our server, not your device. If it reports the site up while your browser fails, the problem is on your side: your network, DNS cache or a local block.
The server is temporarily unable to handle the request, often from overload or maintenance. A persistent 503 needs the host or developer.
Each row is one request in a redirect chain, for example http to https, then www to non-www, then the final page.
A broken certificate makes the connection fail, which shows here as no response. Use the SSL checker for the certificate detail.
This is one check from one location. Aepto checks your sites from up to six regions, as often as every minute on paid plans, and alerts you when one fails.
