ToolSphere

HTTP Status Code Reference

More tools

Searchable reference guide for standard HTTP response status codes. Look up 1xx, 2xx, 3xx, 4xx, and 5xx client and server error codes and definitions.

HTTP status code reference

Search standard HTTP response status codes and what they mean.

100
Continue
The server has received the request headers and the client should proceed to send the request body.
101
Switching Protocols
The requester has asked the server to switch protocols.
200
OK
The request succeeded.
201
Created
The request succeeded and a new resource was created.
202
Accepted
The request has been accepted for processing, but processing is not complete.
204
No Content
The server has no content to send for this request.
206
Partial Content
Delivers only part of the resource due to a range header sent by the client.
301
Moved Permanently
The resource has been permanently moved to a new URL.
302
Found
The resource temporarily resides at a different URL.
304
Not Modified
The resource has not been modified since the version specified by request headers.
307
Temporary Redirect
Like 302, but the request method and body must not change.
308
Permanent Redirect
Like 301, but the request method and body must not change.
400
Bad Request
The server cannot process the request due to a client error.
401
Unauthorized
Authentication is required and has failed or not been provided.
403
Forbidden
The server understood the request but refuses to authorize it.
404
Not Found
The requested resource could not be found.
405
Method Not Allowed
The request method is not supported for the requested resource.
408
Request Timeout
The server timed out waiting for the request.
409
Conflict
The request conflicts with the current state of the server.
410
Gone
The resource requested is no longer available and will not be available again.
415
Unsupported Media Type
The media format of the requested data is not supported.
418
I'm a teapot
An April Fools joke from RFC 2324; the server refuses to brew coffee in a teapot.
422
Unprocessable Entity
The request was well-formed but contains semantic errors.
429
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
500
Internal Server Error
A generic error occurred on the server.
501
Not Implemented
The server does not support the functionality required to fulfill the request.
502
Bad Gateway
The server, acting as a gateway, received an invalid response from the upstream server.
503
Service Unavailable
The server is not ready to handle the request, often due to maintenance or overload.
504
Gateway Timeout
The upstream server failed to send a request in time.

On this browser only

Give feedback

Did this tool help?

Tell us what worked, what didn’t, or what you’d like next.

Opens Google Forms in a new tab with this tool’s name filled in. No sign-in or email required. Feedback is optional.

How to use HTTP Status Code Reference

  1. 1Type a status code or keyword into the search box.
  2. 2Browse the matching codes with their standard meaning.
  3. 3Codes are color-coded by class (informational, success, redirect, client error, server error).

About HTTP Status Code Reference

Reading Status Codes by Class First

Every HTTP status code's leading digit signals its general category before you even need to know the specific number: 1xx (informational, request still processing), 2xx (success), 3xx (redirection, further action needed), 4xx (client error, something about the request was wrong), and 5xx (server error, the server failed on an apparently valid request) — checking just this first digit is often enough to triage a problem before reading the specific code at all (see HTTP Status Codes Explained for the full breakdown of the pairs people mix up most, like 401 vs. 403).

Searching by number or by keyword both matter for different situations — sometimes you have a specific code from a log or error message and need its meaning; other times you know roughly what kind of error occurred (an authentication issue, a redirect problem) and need to find the right specific code for it, which is exactly why a keyword-searchable reference is more useful than a code-only lookup table.

The color-coding by class (grouping 2xx, 3xx, 4xx, 5xx visually) reinforces the same leading-digit triage instinct — glancing at a color is faster than reading a full code number when scanning a list of several different status codes at once, like when reviewing a server log with a mix of response types.

Guides and tutorials

Frequently asked questions

Why does the first digit of an HTTP status code matter so much?

It immediately signals the general category — success, redirection, client error, or server error — often enough to triage a problem before even reading the full specific code, which is why the class-based grouping (2xx, 4xx, etc.) is the fastest first read.

Can I search this reference by something other than the exact status code number?

Yes — searching by keyword (like "redirect" or "unauthorized") helps when you know roughly what kind of error occurred but don't remember or don't yet have the specific numeric code.

Why are the codes color-coded by class?

It reinforces the same leading-digit triage instinct visually — scanning a list or log with color-coded status classes is faster than reading every individual code number when trying to spot patterns or problem areas at a glance.

Have a suggestion for HTTP Status Code Reference?Share your feedback ↗