A complete reference of every standard HTTP response status code defined by the IETF, organized by category. Whether you are building APIs, debugging server responses, or documenting error handling, this list has every code you need.
Pro tip: Download as JSON to use as a lookup table in your application — each code maps directly to its phrase and description for easy programmatic access.
Select which columns to include in your download.
About the HTTP Status Codes Dataset
This dataset contains every standard HTTP response status code defined in RFCs 7231, 7232, 7233, 7235, 7538, 6585, and 7725 maintained by the Internet Engineering Task Force (IETF). Each entry includes the numeric code, the standard reason phrase, a clear description of when the code is returned, and its category classification. The data was last verified against the IANA HTTP Status Code Registry.
Common Use Cases
Developers and technical writers use this dataset in several practical scenarios:
- API documentation: Embed status code tables in your API reference so consumers know exactly which codes your endpoints return and what each one means.
- Error handling logic: Import into your application as a lookup map to display user-friendly messages for every possible server response.
- Monitoring dashboards: Load into Grafana, Datadog, or a custom dashboard to label status code charts with human-readable phrases instead of bare numbers.
- Developer training: Use as a teaching reference for onboarding materials, coding bootcamps, or internal knowledge bases.
Column Reference
The dataset includes four columns designed for maximum flexibility:
- code — The three-digit HTTP status code (e.g.
200,404,503). Always an integer with no leading zeros. - phrase — The standard reason phrase as defined in the relevant RFC (e.g. "OK", "Not Found", "Service Unavailable").
- description — A concise explanation of what the code means and when a server typically returns it.
- category — One of five classes: Informational (1xx), Success (2xx), Redirection (3xx), Client Error (4xx), or Server Error (5xx).
How to Use in Your Application
Download the JSON format to get an array of objects you can import directly into JavaScript, Python, or any language that parses JSON. For database-backed applications, use the SQL export to create a http_status_codes table you can JOIN against your access logs. The CSV format works well for spreadsheet analysis or as a data source for documentation generators like Swagger or Redoc.
Status Code Categories Explained
HTTP status codes are grouped into five classes based on their first digit. 1xx Informational codes indicate the server received the request and the client should continue. 2xx Success codes confirm the request was received, understood, and accepted. 3xx Redirection codes tell the client it must take additional action to complete the request, usually following a new URL. 4xx Client Error codes indicate the request contains bad syntax or cannot be fulfilled. 5xx Server Error codes mean the server failed to fulfill a valid request due to an internal issue.