HTTP Status Code Reference
Complete reference of HTTP status codes with descriptions. Search by code number or name, filter by category.
28 status codes
Server received request headers; client should proceed to send the body.
Server is switching protocols as requested by the client (e.g., to WebSocket).
Request succeeded. Standard response for successful HTTP requests.
Request fulfilled and a new resource was created. Typically returned after POST/PUT.
Request accepted for processing, but processing has not been completed.
Request succeeded but there is no content to return. Common for DELETE requests.
Server is delivering only part of the resource due to a range header sent by the client.
Resource has been permanently moved to a new URL. All future requests should use the new URL.
Resource temporarily located at a different URL. Client should continue using the original URL.
Resource has not been modified since last request. Client can use cached version.
Like 302, but the request method must not change. POST stays POST.
Like 301, but the request method must not change. POST stays POST.
Server cannot process the request due to client error (malformed syntax, invalid parameters).
Authentication is required and has failed or not been provided. Typically needs login.
Server understood the request but refuses to authorize it. Different from 401 — re-authenticating will not help.
The requested resource could not be found on the server. Most recognized HTTP error.
The HTTP method used is not supported for this resource (e.g., POST on a GET-only endpoint).
Server timed out waiting for the request. Client did not produce a request in time.
Request conflicts with current state of the server. Common in concurrent update scenarios.
Resource is no longer available and no forwarding address is known. Permanent removal.
Request entity is larger than the server is willing or able to process.
The media format of the requested data is not supported by the server.
Request was well-formed but semantically erroneous. Common in API validation errors.
User has sent too many requests in a given time period (rate limiting).
Generic server error. Something went wrong on the server side.
Server acting as gateway received an invalid response from the upstream server.
Server is not ready to handle the request. Usually due to maintenance or overload.
Server acting as gateway did not get a response from the upstream server in time.
Instant Search
Search by code number, name, or description. Find the status code you need instantly.
Category Filters
Filter by 1xx, 2xx, 3xx, 4xx, or 5xx categories. Color-coded for quick scanning.
Detailed Descriptions
Each status code includes a clear, practical description explaining when and why it's used.
Premium Developer Resources
Like this tool? Get 20+ premium tools
Unlock AI Code Review, AI Doc Generator, AI SQL Builder, batch processing, and API access. Start your 7-day free trial today.
Free vs Pro
Related Tools
JSON Formatter & Validator
Format, validate, and minify JSON data with syntax highlighting and error detection.
UUID Generator
Generate UUID v4 identifiers. Bulk generate up to 25 at once.
Timestamp Converter
Convert Unix timestamps to human-readable dates and vice versa.
SQL Formatter
Format and beautify SQL queries with customizable keyword casing.