search

Found

info Overview

Searchable reference of HTTP status codes with category filter and related headers.

📘 How to Use

  1. Type a specific status code number or keyword into the search input
  2. Select a category filter to narrow down the displayed results
  3. Click on a specific status code card to expand its details

HTTP Status Code Reference

grid_view Related

Article

HTTP Status Code Reference | Quick Guide for Developers

An interactive lookup tool designed for developers, network engineers, and system administrators to quickly identify and understand HTTP status codes. It provides precise descriptions, practical use cases, and associated headers for codes ranging from 100 to 511.

💡 About This Tool

  • Instant Search and Filtering Locate a specific status code immediately by typing its number, name, or related keywords. You can also click category filters (1xx, 2xx, 3xx, 4xx, 5xx) to narrow down response classes.
  • Practical Context and Implementation Details Beyond basic definitions, the tool outlines real-world scenarios. For example, it explains adjusting client_max_body_size in Nginx for a 413 Payload Too Large error, or handling 0-RTT replay attacks in TLS 1.3 with a 425 Too Early response.
  • Header Associations Instantly view which HTTP headers are required or commonly paired with specific status codes, such as the Retry-After header for 429 Too Many Requests or Content-Range for 206 Partial Content.

🧐 Frequently Asked Questions

Q. What do the different status code categories (1xx to 5xx) mean?

A. The first digit defines the response class and helps developers immediately evaluate the state of a request: - 1xx (Informational): The request was received, and the process is continuing. - 2xx (Success): The action was successfully received, understood, and accepted. - 3xx (Redirection): Further action must be taken to complete the request. - 4xx (Client Error): The request contains bad syntax or cannot be fulfilled. - 5xx (Server Error): The server failed to fulfill a valid request.

Q. Does this reference include experimental or uncommon codes?

A. Yes. Alongside standard responses like 200 OK and 404 Not Found, it includes specialized codes utilized in specific environments. You will find WebDAV specific codes like 207 Multi-Status, protocol-specific responses like 421 Misdirected Request for SNI mismatches, and even the classic RFC 2324 Easter egg, 418 I'm a Teapot.

📚 HTTP Status Code Trivia

Many status codes are deeply tied to evolving web standards and specialized protocols. For instance, 103 Early Hints allows browsers to start preloading HTML, CSS, and JS resources via the Link header before the final response is ready, significantly speeding up page rendering.

Furthermore, historical and cultural references are occasionally embedded into network specifications. The status code 451 Unavailable For Legal Reasons—often used for GDPR content blocking or government censorship—directly references Ray Bradbury's dystopian novel Fahrenheit 451. Understanding these underlying specifications provides developers with better insight when configuring Nginx reverse proxies or handling complex HTTP/2 and HTTP/3 environments.