HTTP Status Codes List

A fast reference guide for HTTP status codes, complete with RFC definitions and instant search filters.

Browser-Based

Class Description: Browse all standard status codes

100

ContinueRFC 9110

The server has received the request headers and the client should proceed to send the request body.

101

Switching ProtocolsRFC 9110

The server understands and is willing to comply with the client's request to switch protocols.

102

ProcessingRFC 9110

An interim response used to inform the client that the server has accepted the complete request, but has not yet completed it.

103

Early HintsRFC 9110

Used to return some response headers before the final HTTP message is ready.

200

OKRFC 9110

The request has succeeded.

201

CreatedRFC 9110

The request has succeeded and has resulted in the creation of a new resource.

202

AcceptedRFC 9110

The request has been accepted for processing, but the processing has not been completed.

203

Non-Authoritative InformationRFC 9110

The returned metadata is not identical to that at the origin server, but is collected from a local or a third-party copy.

204

No ContentRFC 9110

The server has successfully fulfilled the request and there is no additional content to send.

205

Reset ContentRFC 9110

Tells the client to reset the document view which caused the request to be sent.

206

Partial ContentRFC 9110

The server is delivering only part of the resource due to a Range header sent by the client.

300

Multiple ChoicesRFC 9110

The request has more than one possible response. The user agent should choose one.

301

Moved PermanentlyRFC 9110

The target resource has been assigned a new permanent URI.

302

FoundRFC 9110

The target resource resides temporarily under a different URI.

303

See OtherRFC 9110

The server redirects the client to get the requested resource at another URI using a GET request.

304

Not ModifiedRFC 9110

Tells the client that the cached version of the resource is still valid.

307

Temporary RedirectRFC 9110

The target resource resides temporarily under a different URI, keeping the original HTTP method.

308

Permanent RedirectRFC 9110

The target resource has been permanently moved to the URI specified in the Location header.

400

Bad RequestRFC 9110

The server cannot or will not process the request due to something that is perceived to be a client error.

401

UnauthorizedRFC 9110

The request has not been applied because it lacks valid authentication credentials.

402

Payment RequiredRFC 9110

Reserved for future use, but sometimes used for subscription blockages.

403

ForbiddenRFC 9110

The server understood the request but refuses to authorize it.

404

Not FoundRFC 9110

The server cannot find the requested resource.

405

Method Not AllowedRFC 9110

The request method is known by the server but is not supported by the target resource.

406

Not AcceptableRFC 9110

The server cannot produce a response matching the Accept headers sent by the client.

408

Request TimeoutRFC 9110

The server timed out waiting for the request from the client.

409

ConflictRFC 9110

The request could not be completed due to a conflict with the current state of the target resource.

410

GoneRFC 9110

The target resource is no longer available at the origin server and no forwarding address is known.

413

Content Too LargeRFC 9110

The server is refusing to process a request because the request payload is larger than the server is willing or able to process.

415

Unsupported Media TypeRFC 9110

The origin server refuses to service the request because the payload is in a format not supported.

418

I'm a teapotRFC 9110

Any attempt to brew coffee with a teapot should result in the error code '418 I'm a teapot'.

422

Unprocessable ContentRFC 9110

The server understands the content type of the request entity, but was unable to process the contained instructions.

429

Too Many RequestsRFC 9110

The user has sent too many requests in a given amount of time.

451

Unavailable For Legal ReasonsRFC 9110

The server is denying access to the resource as a consequence of a legal demand.

500

Internal Server ErrorRFC 9110

The server encountered an unexpected condition that prevented it from fulfilling the request.

501

Not ImplementedRFC 9110

The server does not support the functionality required to fulfill the request.

502

Bad GatewayRFC 9110

The server, while acting as a gateway or proxy, received an invalid response from the inbound server.

503

Service UnavailableRFC 9110

The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.

504

Gateway TimeoutRFC 9110

The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server.

505

HTTP Version Not SupportedRFC 9110

The server does not support the HTTP protocol version that was used in the request.

Quick Answer

A dedicated utility designed specifically to handle http status codes list operations swiftly and securely in your browser.

100% Free and requires no installation.
Processes data locally, ensuring no sensitive information is uploaded.
Optimized for immediate, real-time results.

How to Use

1Type search queries (like '404' or 'not found') to filter the HTTP codes registry.
2Filter by class tabs: 1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error, 5xx Server Error.
3Review official RFC 9110 descriptions and typical use cases for each status code.

Common Use Cases

Validating malformed JSON responses from backend APIs.
Decoding and verifying JWT payloads during authentication flows.
Minifying CSS/JS assets manually before a quick hotfix deployment.

Features

Keeps proprietary code, tokens, and API keys strictly on your local machine.

Instant execution provides immediate feedback loops during active debugging.

Eliminates the need to install heavy IDE extensions for simple formatting tasks.

Frequently Asked Questions

Is the HTTP Status Codes List free to use?

Yes, the HTTP Status Codes List is completely free, runs locally in your browser, and requires no registration.

Is data sent to the cloud for processing?

No, developer utilities like JSON formatters and Base64 encoders execute completely within your local browser sandbox to prevent data leaks.

How large of a payload can I format?

Local tools are restricted only by your browser's heap limit, typically allowing several megabytes of raw text processing without freezing.

Get New Tools in Your Inbox

We build new offline utilities weekly. Subscribe to our tiny mailing list. No spam, ever.

Recommended Resources

Partner

Vercel Hosting

Deploy your Next.js application to Vercel's global edge network in seconds.

Get Started Free

Best Value

Hostinger Cloud

High-performance web hosting with SSD storage and free domains.

View Plans