Developer Tools

HTTP Status Code Reference

Complete HTTP status code reference. Search by code or name, filter by category.

Runs in your browser

🔎

No codes match ""

Next useful step

Related tools

5 selected

01 Code Beautifier Continue with a nearby task 02 Css Minifier Continue with a nearby task 03 Diff Checker Continue with a nearby task 04 Html Beautifier Continue with a nearby task 05 Html Minifier Continue with a nearby task

What is the Http Status Codes?

HTTP status codes are three-digit numbers returned by a web server to indicate the outcome of a client's request. They are grouped into five classes: 1xx (informational), 2xx (success), 3xx (redirection), 4xx (client errors), and 5xx (server errors). This reference provides plain-English explanations of every standard status code along with guidance on when each is typically encountered and how to handle it.

How to use the Http Status Codes

  1. Browse the status codes by category using the tabs (2xx, 3xx, 4xx, 5xx), or use the search box to jump directly to a specific code.
  2. Click any code to expand its full description, common causes, and recommended actions.
  3. Use the search field to find codes by number (e.g., "404") or by keyword (e.g., "unauthorized").
  4. Filter by category to focus on a specific class of responses.
  5. Bookmark this page for quick reference during API development and debugging.

Frequently asked questions

401 Unauthorized means the client is not authenticated - credentials are missing or invalid. 403 Forbidden means the client is authenticated but does not have permission to access the resource. Authentication would not help for a 403.
400 Bad Request indicates the request is malformed (e.g., invalid JSON syntax). 422 Unprocessable Entity means the request is syntactically valid but semantically incorrect (e.g., a field value fails validation rules). Use 422 for validation errors in REST APIs.
503 Service Unavailable means the server is temporarily unable to handle the request, usually due to overload or scheduled maintenance. It should be temporary. Include a Retry-After header to tell clients when to try again.