Look up HTTP status codes

Status lookup.

Browse and search IANA-style HTTP status codes with their reason phrases. Pure browser; no login.

Showing 36 of 36 status codes.

100Continue1xx

Server has received request headers, client should send body.

101Switching Protocols1xx

Protocol upgrade (e.g. WebSocket).

102Processing1xx

Server is processing the request; no response yet (WebDAV).

103Early Hints1xx

Preload links while the final response is being prepared.

200OK2xx

Standard success.

201Created2xx

Resource created (POST).

202Accepted2xx

Request accepted, processing later.

204No Content2xx

Success, no body to return.

206Partial Content2xx

Range request succeeded.

301Moved Permanently3xx

Resource moved; clients should update bookmark.

302Found3xx

Temporary redirect; method may change.

303See Other3xx

GET the URL in Location to complete the action.

304Not Modified3xx

Use cached copy.

307Temporary Redirect3xx

Same method, temporary redirect.

308Permanent Redirect3xx

Same method, permanent redirect.

400Bad Request4xx

Client sent something the server cannot parse or accept.

401Unauthorized4xx

Missing or invalid authentication credentials.

403Forbidden4xx

Authenticated but not allowed.

404Not Found4xx

Resource does not exist.

405Method Not Allowed4xx

Method not supported on this resource.

406Not Acceptable4xx

Cannot produce a response matching Accept headers.

408Request Timeout4xx

Server gave up waiting for the client.

409Conflict4xx

Request conflicts with current state.

410Gone4xx

Resource intentionally removed; do not retry.

413Payload Too Large4xx

Body is larger than the server is willing to accept.

415Unsupported Media Type4xx

Content-Type is not supported.

418I'm a teapot4xx

April Fools' RFC 2324.

422Unprocessable Entity4xx

Request is well-formed but semantically wrong (WebDAV).

429Too Many Requests4xx

Rate limit exceeded.

500Internal Server Error5xx

Generic server error.

501Not Implemented5xx

Server does not support the feature.

502Bad Gateway5xx

Upstream returned an invalid response.

503Service Unavailable5xx

Server temporarily cannot handle the request.

504Gateway Timeout5xx

Upstream did not respond in time.

505HTTP Version Not Supported5xx

Server does not support the HTTP version in the request.

511Network Authentication Required5xx

Captive portal; client must authenticate.

HTTP status codes and what they mean

Every response a web server sends starts with a three-digit status code that tells the client what happened: 200 for success, 404 when nothing exists at the address, 500 when the server failed. Browsers, API clients, search engine crawlers and monitoring tools all decide what to do next based on that number.

This reference lists the status codes you meet in practice with their official reason phrases and a short explanation. Search by number, by name or by a word from the description.

How to use it

Type a code such as 429, or a word such as teapot or redirect, into the search box.
Read the matching codes with their reason phrases and notes.
Clear the search to browse the whole list, grouped by class.
Use the class colour to tell success, redirects, client errors and server errors apart at a glance.

Example: searching for a code

Input

Output

418 I'm a teapot: April Fools' RFC 2324.

Search matches the number, the reason phrase and the note, so typing teapot finds the same entry.

The five classes

The first digit gives the class. 1xx codes are informational and rarely seen in tools. 2xx means success: 200 OK, 201 Created after a new record, 204 No Content when there is nothing to return. 3xx means redirection: the content is elsewhere. 4xx means the client made a mistake, and 5xx means the server failed while handling a valid request.

When debugging, the class tells you where to look. A 4xx error is fixed in the request: the URL, the login, the body. A 5xx error is fixed on the server, and repeating the same request may succeed later.

Codes that are easy to confuse

401 Unauthorized actually means not authenticated: log in or send a valid token. 403 Forbidden means the server knows who you are and still refuses. 404 Not Found says nothing exists at the URL, while 410 Gone says it existed and was removed on purpose, which search engines treat as a stronger signal to drop the page.

301 and 308 are permanent redirects; 302 and 307 are temporary. Search engines move rankings to the target of a permanent redirect. 307 and 308 also guarantee that the request method stays the same, so a POST stays a POST.

429 Too Many Requests means you hit a rate limit; well-behaved clients wait for the time in the Retry-After header. 502 Bad Gateway and 504 Gateway Timeout come from a proxy or load balancer in front of the application, which usually means the application itself is down or too slow.

Questions

Is 418 I'm a teapot real?

It comes from an April Fools' specification from 1998 about coffee pots. It was never meant for real use, but many servers and frameworks support it as an in-joke.

Is every registered code listed?

No. The list covers the 36 codes you meet in practice. The full registry, maintained by IANA, also includes rare codes used by WebDAV and other extensions.

Does the tool check a live URL?

No. It is an offline reference and makes no network requests.