HTTP Status Codes

Complete reference for HTTP status codes with detailed explanations, examples, and best practices.

Most Common Status Codes

200

OK

301

Moved Permanently

302

Found

400

Bad Request

401

Unauthorized

403

Forbidden

404

Not Found

429

Too Many Requests

500

Internal Server Error

503

Service Unavailable

Informational

1 codes
100

Continue

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

RFC 7231

Success

7 codes
200

OK

The request has succeeded.

RFC 7231
201

Created

The request has been fulfilled and resulted in a new resource being created.

RFC 7231
202

Accepted

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

RFC 7231
203

Non-Authoritative Information

The server is a transforming proxy (e.g. a Web accelerator) that received a 200 OK response to satisfy a previous request.

RFC 7231
204

No Content

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

RFC 7231
205

Reset Content

The server has fulfilled the request and the user agent should reset the document view which caused the request to be sent.

RFC 7231

Redirection

9 codes
300

Multiple Choices

The request has more than one possible responses.

RFC 7231
301

Moved Permanently

The requested resource has been permanently moved to a new URL.

RFC 7231
302

Found

The requested resource resides temporarily under a different URI.

RFC 7231
303

See Other

The response to the request can be found under a different URI and should be retrieved using a GET method on that resource.

RFC 7231
304

Not Modified

Indicates that the resource has not been modified since the version specified by the request headers.

RFC 7232
305

Use Proxy

The requested resource must be accessed through the proxy given by the Location field.

RFC 7231

Client Error

29 codes
400

Bad Request

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

RFC 7231
401

Unauthorized

The request requires user authentication.

RFC 7235
402

Payment Required

Reserved for future use.

RFC 7231
403

Forbidden

The server understood the request, but is refusing to fulfill it.

RFC 7231
404

Not Found

The server cannot find the requested resource.

RFC 7231
405

Method Not Allowed

The request method is not supported for the requested resource.

RFC 7231

Server Error

11 codes
500

Internal Server Error

The server has encountered a situation it does not know how to handle.

RFC 7231
501

Not Implemented

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

RFC 7231
502

Bad Gateway

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

RFC 7231
503

Service Unavailable

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

RFC 7231
504

Gateway Timeout

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

RFC 7231
505

HTTP Version Not Supported

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

RFC 7231

Available for Freelance

Fullstack developer specializing in Flutter Mobile Apps, .Net Back End, and Angular/React. Let's build something amazing together!

Contact me

Stay in the loop

Get notified about new tools and updates

HTTP Status Codes Reference - Complete List with Descriptions