DevToolsAtlas
Local RAM
Web Protocols & Spec

HTTP Status Code Reference Atlas

Comprehensive developer reference guide for HTTP status codes (1xx to 5xx) with RFC spec details.

2xx HTTP Response CodesSuccess

Standard response for successful HTTP requests.

201Created
RFC Spec

Request fulfilled, resulting in the creation of a new resource.

204No Content
RFC Spec

Server successfully processed request, but is not returning any content.

3xx HTTP Response CodesRedirection

301Moved Permanently
RFC Spec

This and all future requests should be directed to the given URI.

302Found (Temporary Redirect)
RFC Spec

Resource temporarily resides under a different URI.

4xx HTTP Response CodesClient Error

400Bad Request
RFC Spec

Server cannot process request due to client syntax error or malformed payload.

401Unauthorized
RFC Spec

Authentication is required and has failed or has not yet been provided.

403Forbidden
RFC Spec

Request was valid, but server is refusing action due to insufficient permissions.

404Not Found
RFC Spec

Requested resource could not be found on the server.

429Too Many Requests
RFC Spec

User has sent too many requests in a given amount of time (rate limiting).

5xx HTTP Response CodesServer Error

500Internal Server Error
RFC Spec

Generic error message when an unexpected condition was encountered on server.

502Bad Gateway
RFC Spec

Server received an invalid response from upstream server while acting as gateway.

503Service Unavailable
RFC Spec

Server is currently unable to handle request due to temporary overload or maintenance.

504Gateway Timeout
RFC Spec

Server acting as gateway did not receive timely response from upstream server.

Frequently Asked Questions

4xx status codes indicate client-side errors (e.g. 400 Bad Request, 404 Not Found, 429 Too Many Requests). 5xx status codes indicate server-side failures (e.g. 500 Internal Server Error, 502 Bad Gateway).