Free tool

Every HTTP status code

What each status code means in plain English, what usually causes it, what to do about it, and whether an uptime check counts it as down.

4 of 72 status codes match.

HTTP status codes by class

Standard codes link to the RFC that defines them. Codes used only by Cloudflare or nginx are marked non-standard. The label on each row says whether an Uptimecheck HTTP monitor counts the code as up or down with its default settings (200–399 is up).

1xx Informational

Interim responses: the request is under way and the real answer follows.

Check what your site returns

The free website checker requests any URL from Stockholm and shows the status code it answers with, every redirect on the way, the response time and when its certificate expires.

Check a website

Which codes should a monitor alert on?

The status codes that matter for uptime, which ones mean real trouble and how to set up checks that don’t cry wolf.

Read the cheat sheet

Questions

What do the five classes of status codes mean?

The first digit gives the class: 1xx informational (the request is under way), 2xx success, 3xx redirection, 4xx client error (the server refuses the request as sent) and 5xx server error. A client that doesn’t know a code treats it like the x00 code of its class, so an unknown 4xx is handled as a 400.

Which status codes does Uptimecheck count as down?

By default an HTTP monitor counts 200–399 as up and anything else as down, and an outage is only reported once a second check confirms it. Redirects are followed, up to 10, and the final answer decides. You can set the expected status codes for each monitor, for example 200-299, 401. The free Is it down? checker counts any answer below 500 as the site answering.

What is the difference between 502, 503 and 504?

All three usually come from a proxy or load balancer in front of the application. 502 Bad Gateway: the server behind it gave an invalid answer or none, often because it crashed. 503 Service Unavailable: the server is overloaded or in maintenance and says so. 504 Gateway Timeout: the server behind it didn’t answer in time.

Are Cloudflare’s 52x codes and nginx’s 444 and 499 standard?

No. Cloudflare sends 520–526 to describe problems between its network and the origin server, and nginx uses 444 (close the connection without answering) and 499 (the client hung up) in its own logs. They aren’t in any RFC, so they are marked non-standard here.

Let Uptimecheck keep watching

This free tool answers one question at a time. In Uptimecheck, the same work runs on its own and alerts you when something needs attention.

Downtime is obsolete.

Set up your first monitor in under a minute, or look around the live demo first.

14-day free trial · No credit card required