HTTP Status Code Lookup

When to reach for this tool

Reach for this when you need to understand what an HTTP response code means during setup, debugging, or an incident review. A one-off check is useful for diagnosis, but production systems need continuous monitoring once the immediate question is answered.

• 2xx is usually healthy, but a 200 can still hide an error body.
• 3xx redirects may be expected or a sign of a misroute.
• 4xx and 5xx tell you very different things about who is at fault.

From one-off check to continuous monitor

Use the lookup to decide whether a status code should be treated as healthy, degraded, a redirect, or a failure in an HTTP check before you wire up alerting.

• Recreate the same check in Sandglass on an interval so the next change is caught without re-running the lookup.
• Send failures to email, a Slack webhook channel, or a generic webhook owned by whoever fixes the problem.
• Track the result over time instead of treating one manual reading as the final answer.

Why a lookup is not monitoring

A status code in isolation can mislead. A 200 can wrap an error page and a 301 can be perfectly healthy, so decide what each code means for your service rather than trusting the number alone.