HTTP Status Codes & Headers Directory
Searchable directory of all 1xx, 2xx, 3xx, 4xx, 5xx HTTP response codes and modern security headers.
Initial part of a request has been received and hasn't yet been rejected by the server.
The server is switching protocols according to the Upgrade header (e.g., HTTP to WebSocket).
Server has received and is processing the request, but no response is available yet (WebDAV).
The request has succeeded. Meaning of success depends on HTTP method (GET, POST, PUT, DELETE).
The request has succeeded and a new resource has been created, usually with a Location header.
The request has been accepted for processing, but processing has not been completed.
The server successfully processed the request and is not returning any content.
The server is delivering only part of the resource due to a Range header sent by the client.
The target resource has been assigned a new permanent URI. Clients and search engines should update links.
The target resource resides temporarily under a different URI.
Resource has not been modified since the version specified in If-Modified-Since or If-None-Match.
Target resource resides temporarily under a different URI; client MUST NOT change the HTTP method.
Target resource has been assigned a new permanent URI; client MUST NOT change the HTTP method.
The server cannot or will not process the request due to a client error (malformed syntax, invalid framing).
Authentication is required and has failed or has not yet been provided.
The server understands the request but refuses to authorize it (insufficient permissions).
The server cannot find the requested resource or does not wish to reveal its existence.
The request method is recognized by the server but is not supported by the target resource.
The server did not receive a complete request message within the time that it was prepared to wait.
The request could not be completed due to a conflict with the current state of the target resource.
The server refuses the attempt to brew coffee with a teapot (April Fools' RFC 2324/7168).
The server understands the content type and syntax, but was unable to process the contained instructions.
The user has sent too many requests in a given amount of time (rate limiting).
The server encountered an unexpected condition that prevented it from fulfilling the request.
The server does not support the functionality required to fulfill the request.
The server, while acting as a gateway or proxy, received an invalid response from the inbound server.
The server is currently unable to handle the request due to temporary overloading or scheduled maintenance.
The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server.
How to Use the HTTP Status Codes & Headers Directory
Filter by status category (2xx Success, 3xx Redirect, 4xx Client Error, 5xx Server Error).
Use the instant search bar to find codes by number (e.g. 404, 502) or description.
Review official specifications, debugging advice, and essential security headers (CSP, HSTS).
Key Capabilities & Features
- •Covers all standard RFC HTTP status codes with practical explanations
- •Searchable directory with category-based filtering
- •Comprehensive Security Headers guide (HSTS, CSP, CORS, X-Frame-Options)
100% In-Browser Privacy Guarantee
Your files and data remain strictly on your device. All computations, image processing, and PDF manipulations happen locally in your web browser via WebAssembly and HTML5 APIs. No files are uploaded or stored on any remote servers.