HTTP status code checker
Confirm what a URL actually returns to clients, catch soft 404s behind redirects and understand unfamiliar codes.
How it measures
- One GET request from a single location, following up to five redirects and recording each hop's status.
- The final status is explained from the HTTP semantics (RFC 9110) together with how UptimeMonitor360 monitors treat it by default.
Limits
- Some servers answer differently depending on the User-Agent, cookies or geography; the probe sends none of your browser's state.
- A 200 can still be an error page; combine with a content assertion when it matters.
Troubleshooting
- 403 from the probe but 200 in the browser
- A WAF or bot filter blocks unknown user agents. Allow the UptimeMonitor360 user agent or probe addresses.
- Unexpected 302 to a login page
- The URL requires a session. Monitor a public health endpoint or use a transaction check that signs in first.