HTTP Status Codes — Complete List

All HTTP status codes from the IANA HTTP Status Code Registry, grouped by class. Click any code for the full guide.

1xx Informational

Informational responses (100–199) indicate that the server has received the request and the client should continue. These are interim responses used primarily in protocol negotiation.

CodeNameGuide
100ContinueGuide
101Switching ProtocolsGuide
102ProcessingGuide
103Early HintsGuide
104Upload Resumption SupportedGuide

2xx Success

Success responses (200–299) indicate the request was received, understood, and accepted. The specific code tells the client how to interpret the response body and what action, if any, was taken.

CodeNameGuide
200OKGuide
201CreatedGuide
202AcceptedGuide
203Non-Authoritative InformationGuide
204No ContentGuide
205Reset ContentGuide
206Partial ContentGuide
207Multi-StatusGuide
208Already ReportedGuide
226IM UsedGuide

3xx Redirect Codes

Redirection responses (300–399) indicate the client must take additional action to complete the request. The choice between permanent and temporary, and between method-preserving and non-preserving redirects, has real implications for SEO, caching, and client behavior.

CodeNameGuide
300Multiple ChoicesGuide
301Moved PermanentlyGuide
302FoundGuide
303See OtherGuide
304Not ModifiedGuide
305Use ProxyGuide
306UnusedGuide
307Temporary RedirectGuide
308Permanent RedirectGuide

4xx Client Errors

Client error responses (400–499) indicate the server cannot process the request due to a problem on the client side — malformed syntax, missing authentication, insufficient permissions, or missing resources.

CodeNameGuide
400Bad RequestGuide
401UnauthorizedGuide
402Payment RequiredGuide
403ForbiddenGuide
404Not FoundGuide
405Method Not AllowedGuide
406Not AcceptableGuide
407Proxy Authentication RequiredGuide
408Request TimeoutGuide
409ConflictGuide
410GoneGuide
411Length RequiredGuide
412Precondition FailedGuide
413Content Too LargeGuide
414URI Too LongGuide
415Unsupported Media TypeGuide
416Range Not SatisfiableGuide
417Expectation FailedGuide
418I'm a TeapotGuide
421Misdirected RequestGuide
422Unprocessable ContentGuide
423LockedGuide
424Failed DependencyGuide
425Too EarlyGuide
426Upgrade RequiredGuide
427UnassignedGuide
428Precondition RequiredGuide
429Too Many RequestsGuide
430UnassignedGuide
431Request Header Fields Too LargeGuide
451Unavailable For Legal ReasonsGuide

5xx Server Errors

Server error responses (500–599) indicate the server failed to fulfill a valid request. These are almost always actionable on the server side and should be monitored in production.

CodeNameGuide
500Internal Server ErrorGuide
501Not ImplementedGuide
502Bad GatewayGuide
503Service UnavailableGuide
504Gateway TimeoutGuide
505HTTP Version Not SupportedGuide
506Variant Also NegotiatesGuide
507Insufficient StorageGuide
508Loop DetectedGuide
509UnassignedGuide
510Not ExtendedGuide
511Network Authentication RequiredGuide