HTTP Status Code Reference

Your data never leaves your browser

Browse the complete reference of HTTP status codes grouped by category.

Options

Brie — Bug Reporting Tool

Found a bug while testing?

Brie captures screenshots, console logs, network data, and session replays in one click — so developers get the full context without the back-and-forth.

About HTTP Status Code Reference

A complete, filterable reference for every standard HTTP status code. Codes are grouped into five categories — 1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error, and 5xx Server Error — each with the official name and a concise description. Use the filter option to focus on a single category.

How to use

  1. Open the tool — the full list of HTTP status codes is displayed immediately.
  2. Use the "Filter" option to narrow the list to a specific category (1xx, 2xx, 3xx, 4xx, 5xx).
  3. Copy any section from the output for use in documentation or API specs.

More QA & Testing Tools

Frequently Asked Questions

FAQs about HTTP Status Code Reference

What is an HTTP status code?

An HTTP status code is a three-digit number returned by a server in response to a client request. It tells the client whether the request was successful, redirected, or encountered an error.

What does a 2xx code mean?

2xx codes indicate that the request was received and processed successfully. The most common is 200 OK, which means everything worked as expected.

When should I use 422 vs 400?

400 Bad Request is used when the request is syntactically malformed. 422 Unprocessable Entity is used when the request is well-formed but contains semantic errors, such as failing validation rules.

What is the difference between 301 and 302?

301 Moved Permanently tells search engines and browsers that the resource has been permanently moved to a new URL. 302 Found indicates a temporary redirect, so the original URL should still be used for future requests.

What is a 429 status code?

429 Too Many Requests means the client has sent too many requests in a given time window. APIs use this code to implement rate limiting.