HTTP Status Codes Reference

Searchable reference of HTTP status codes and meanings.

Quick answer: Searchable reference guide for all HTTP Status Codes. Quickly look up the meaning of 404, 500, 301, and every other server response code.

Search status codes

100ContinueThe server received the request headers and the client should proceed to send the body.

101Switching ProtocolsThe requester asked the server to switch protocols and the server agreed.

200OKStandard response for successful HTTP requests.

201CreatedThe request succeeded and a new resource was created.

202AcceptedThe request was accepted for processing but is not yet complete.

204No ContentThe server successfully processed the request and is not returning any content.

206Partial ContentThe server is delivering only part of the resource due to a range header.

301Moved PermanentlyThis and all future requests should be directed to the given URI.

302FoundThe resource resides temporarily under a different URI.

304Not ModifiedThe resource has not been modified since the version specified by request headers.

307Temporary RedirectRepeat the request to another URI using the same method.

308Permanent RedirectThe resource is now permanently at another URI; reuse the same method.

400Bad RequestThe server cannot process the request due to a client error (malformed syntax).

401UnauthorizedAuthentication is required and has failed or not been provided.

403ForbiddenThe server understood the request but refuses to authorize it.

404Not FoundThe requested resource could not be found but may be available in the future.

405Method Not AllowedThe request method is not supported for the target resource.

408Request TimeoutThe server timed out waiting for the request.

409ConflictThe request conflicts with the current state of the server.

410GoneThe resource is no longer available and will not be available again.

418I'm a teapotAn April Fools joke from RFC 2324; the server refuses to brew coffee.

422Unprocessable EntityThe request was well-formed but contains semantic errors.

429Too Many RequestsThe user has sent too many requests in a given amount of time (rate limiting).

500Internal Server ErrorA generic error message when the server encounters an unexpected condition.

501Not ImplementedThe server does not recognize the request method or lacks the ability to fulfil it.

502Bad GatewayThe server, acting as a gateway, received an invalid response from the upstream server.

503Service UnavailableThe server is not ready to handle the request, often due to overload or maintenance.

504Gateway TimeoutThe upstream server failed to send a request in time.

A fast, searchable reference of HTTP status codes — from 200 OK to 500 Internal Server Error — with a plain explanation of what each one means.

How it works

Open the reference table.
Search by code number (e.g., 404) or keyword (e.g., "Not Found").
Read the standardized definition to debug your API or web server.

Frequently asked questions

What is the core difference between 401 and 403?

401 Unauthorized strictly means you lack authentication (you need to log in). 403 Forbidden means you are logged in, but lack the permission to view the resource.

When is it correct to use a 301 instead of a 302?

301 indicates a Permanent redirect (search engines will update their indexes). 302 is Temporary (the original URL is kept indexed).

What triggers a 429 status code?

429 means Too Many Requests. You have aggressively hit an API rate limit and must implement a backoff strategy.