HTTP Status Codes Reference - Complete Status Code Guide

Free online HTTP status codes reference. Search and browse all HTTP response status codes with descriptions, categories, and common use cases.

1xx Informational

100
Continue

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

101
Switching Protocols

The server is switching protocols as requested (e.g., WebSocket upgrade).

2xx Success

200
OK

The request succeeded. Standard response for successful HTTP requests.

201
Created

The request succeeded and a new resource was created. Common after POST requests.

204
No Content

The request succeeded but there is no content to return. Common for DELETE.

206
Partial Content

The server is delivering only part of the resource due to a range header.

3xx Redirection

301
Moved Permanently

The resource has been permanently moved to a new URL. Use for SEO redirects.

302
Found

The resource is temporarily at a different URL. Often used in OAuth redirects.

304
Not Modified

The resource has not been modified since the last request. Use cached version.

307
Temporary Redirect

Like 302 but preserves the HTTP method. Used in HSTS redirects.

308
Permanent Redirect

Like 301 but preserves the HTTP method.

4xx Client Error

400
Bad Request

The server cannot process the request due to invalid syntax or parameters.

401
Unauthorized

Authentication is required. The client must provide valid credentials.

403
Forbidden

The client does not have permission to access the resource, even with auth.

404
Not Found

The requested resource does not exist on the server.

405
Method Not Allowed

The HTTP method is not supported for the requested resource.

409
Conflict

The request conflicts with the current state of the resource.

410
Gone

The resource is permanently gone and will not be available again.

413
Payload Too Large

The request body exceeds the server limit.

415
Unsupported Media Type

The media type in the request is not supported by the server.

422
Unprocessable Entity

The request is well-formed but contains semantic errors (used in APIs).

429
Too Many Requests

The user has sent too many requests in a given time. Rate limiting.

5xx Server Error

500
Internal Server Error

Generic server error. Something unexpected went wrong.

502
Bad Gateway

The server received an invalid response from an upstream server.

503
Service Unavailable

The server is temporarily unable to handle the request (maintenance/overload).

504
Gateway Timeout

The upstream server did not respond in time.

What Are HTTP Status Codes?

HTTP status codes are three-digit numbers returned by a web server in response to a client's request. They indicate whether the request was successful, redirected, resulted in a client error, or caused a server error. Status codes are grouped into five categories: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error). Understanding these codes is essential for web developers, API designers, and system administrators who need to build, debug, and monitor web applications and services.

How to Use the HTTP Status Code Reference

  1. Browse the complete list of HTTP status codes organized by category (1xx through 5xx).
  2. Use the search field to filter codes by number, name, or description — for example, type '404' or 'redirect'.
  3. Each status code shows its numeric code, official name, and a concise description of when and how it is used.
  4. Color-coded categories make it easy to distinguish between success (green), redirection (yellow), client errors (orange), and server errors (red).
  5. Use this reference while debugging API responses, configuring web servers, or writing error handling logic.

Common Use Cases

  • API Development — Choose the correct status codes when designing REST API responses — knowing when to use 201 vs 200, or 400 vs 422, leads to better APIs.
  • Debugging HTTP Errors — When an API returns an unexpected status code, quickly look up its meaning to understand whether the issue is client-side or server-side.
  • SEO & Redirects — Understand the difference between 301 (permanent) and 302 (temporary) redirects and their impact on search engine optimization.
  • Error Page Design — Reference the correct codes when implementing custom error pages for 404, 403, 500, and other common error scenarios.

FAQ

What is the difference between 401 and 403?
401 Unauthorized means the request lacks valid authentication credentials — the user needs to log in. 403 Forbidden means the server understood the request and the user may be authenticated, but they don't have permission to access the resource.
When should I use 200 vs 201 vs 204?
Use 200 OK for successful GET requests and general success. Use 201 Created after a successful POST that creates a new resource. Use 204 No Content for successful requests that don't return a body, such as DELETE operations.
What is the difference between 301 and 308 redirects?
Both are permanent redirects. 301 allows the client to change the HTTP method (e.g., POST may become GET). 308 requires the client to preserve the original HTTP method. For most website redirects, 301 is standard; 308 is used when method preservation is critical.

Verwandte Tools