HTTP Status Codes
Quick reference guide for all HTTP status codes with detailed descriptions
About this ToolHow it works, benefits & use casesTap to collapse
A searchable, browsable reference for HTTP status codes that gets you to the right answer faster than scrolling an RFC. Every code is grouped into its standard class — 1xx informational, 2xx success, 3xx redirection, 4xx client error, and 5xx server error — and shown as a card with the code, its reason phrase, a colour-coded category badge, and a short description of when it applies. Type into the search box to filter by code number, name, or description across the whole list, or click a category chip to view just one class. A running count tells you how many codes match, and each card has a copy button that puts "404 Not Found" style text on your clipboard. The whole reference lives in your browser, so it loads instantly and works offline once the page is open.
How to Use
- 1Type a number, name, or keyword into "Search status codes" to filter the list live.
- 2Or click a category chip — 1xx, 2xx, 3xx, 4xx, or 5xx — to browse just that class.
- 3Read each card for the code, reason phrase, category badge, and description.
- 4Click the copy button on any card to copy the "code message" text (for example "404 Not Found").
- 5Check the result count and the category reference at the bottom for a quick refresher on the five classes.
Key Benefits
- Full status code reference grouped into the five standard classes
- Live search by code number, reason phrase, or description text
- Color-coded category badges to spot the class at a glance
- One-click copy of the "code message" string for each code
- Plain-language description of what each code means and when to use it
- Live match count so you know how many results your filter returns
- Loads instantly and works offline once the page is open
Common Use Cases
- Choosing the correct status code to return from an API endpoint or handler
- Looking up an unfamiliar code you saw in a log, response, or browser console
- Settling whether to use 401 vs 403, or 301 vs 302 vs 307, during code review
- Copying a code and reason phrase into documentation or a test assertion
- Refreshing your memory on the difference between the 4xx and 5xx classes
58 codes found
100Continue
The server has received the request headers, and the client should proceed to send the request body.
101Switching Protocols
The requester has asked the server to switch protocols and the server has agreed to do so.
102Processing
The server has received and is processing the request, but no response is available yet.
103Early Hints
Used to return some response headers before final HTTP message.
200OK
The request has succeeded. The meaning of success depends on the HTTP method used.
201Created
The request has been fulfilled and resulted in a new resource being created.
202Accepted
The request has been accepted for processing, but the processing has not been completed.
203Non-Authoritative Information
The server successfully processed the request but is returning information that may be from another source.
204No Content
The server successfully processed the request and is not returning any content.
205Reset Content
The server successfully processed the request, but is not returning any content. Requires requester to reset the document view.
206Partial Content
The server is delivering only part of the resource due to a range header sent by the client.
300Multiple Choices
Indicates multiple options for the resource that the client may follow.
301Moved Permanently
This and all future requests should be directed to the given URI.
302Found
The resource was found but at a different URI. The client should continue to use the original URI.
303See Other
The response to the request can be found under another URI using a GET method.
304Not Modified
Indicates that the resource has not been modified since the version specified by the request headers.
307Temporary Redirect
The request should be repeated with another URI, but future requests should still use the original URI.
308Permanent Redirect
The request and all future requests should be repeated using another URI.
400Bad Request
The server cannot or will not process the request due to client error (e.g., malformed request syntax).
401Unauthorized
Authentication is required and has failed or has not yet been provided.
402Payment Required
Reserved for future use. Originally intended for digital payment systems.
403Forbidden
The request was valid, but the server is refusing to respond to it. Unlike 401, authentication will not help.
404Not Found
The requested resource could not be found but may be available in the future.
405Method Not Allowed
A request method is not supported for the requested resource.
406Not Acceptable
The requested resource is capable of generating only content not acceptable according to the Accept headers.
407Proxy Authentication Required
The client must first authenticate itself with the proxy.
408Request Timeout
The server timed out waiting for the request.
409Conflict
Indicates that the request could not be processed because of conflict in the request.
410Gone
Indicates that the resource requested is no longer available and will not be available again.
411Length Required
The request did not specify the length of its content, which is required by the requested resource.
412Precondition Failed
The server does not meet one of the preconditions that the requester put on the request.
413Payload Too Large
The request is larger than the server is willing or able to process.
414URI Too Long
The URI provided was too long for the server to process.
415Unsupported Media Type
The request entity has a media type which the server or resource does not support.
416Range Not Satisfiable
The client has asked for a portion of the file, but the server cannot supply that portion.
417Expectation Failed
The server cannot meet the requirements of the Expect request-header field.
418I'm a teapot
Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot". (April Fools' joke)
421Misdirected Request
The request was directed at a server that is not able to produce a response.
422Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
423Locked
The resource that is being accessed is locked.
424Failed Dependency
The request failed due to failure of a previous request.
425Too Early
Indicates that the server is unwilling to risk processing a request that might be replayed.
426Upgrade Required
The client should switch to a different protocol.
428Precondition Required
The origin server requires the request to be conditional.
429Too Many Requests
The user has sent too many requests in a given amount of time ("rate limiting").
431Request Header Fields Too Large
The server is unwilling to process the request because either an individual header field or all the header fields collectively are too large.
451Unavailable For Legal Reasons
A server operator has received a legal demand to deny access to a resource or to a set of resources.
500Internal Server Error
A generic error message when the server encounters an unexpected condition.
501Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfill the request.
502Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
503Service Unavailable
The server is currently unavailable (overloaded or down for maintenance).
504Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
505HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
506Variant Also Negotiates
Transparent content negotiation for the request results in a circular reference.
507Insufficient Storage
The server is unable to store the representation needed to complete the request.
508Loop Detected
The server detected an infinite loop while processing the request.
510Not Extended
Further extensions to the request are required for the server to fulfill it.
511Network Authentication Required
The client needs to authenticate to gain network access.
HTTP Status Code Categories
1xx Informational: Request received, continuing process
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 an apparently valid request
Was this tool helpful?
Share Your Experience
Help others discover this tool!
Related guide
Related tools
- Code Block FormatterFormat code blocks for Markdown
- cURL to Code ConverterConvert cURL commands to code in various languages
- HTTP Header ParserParse and analyze HTTP headers
- ASCII ConverterConvert between ASCII and text
- Morse Code TranslatorTranslate text to Morse code and back
- Security Headers GeneratorGenerate hardened HTTP security headers with a live A+ to F grade, then export to nginx, Apache, Caddy, Vercel, Netlify, Next.js, Express, or Cloudflare; or audit a site's existing headers
Type into the "Search status codes" box and the list filters instantly. Search works across the code number, the reason phrase, and the description, so you can look up "418", "teapot", or "rate limit" and find the relevant entries.
1xx is informational (request received, continuing), 2xx is success, 3xx is redirection (further action needed), 4xx is a client error (bad request that cannot be fulfilled), and 5xx is a server error (the server failed to fulfil a valid request). The reference section at the bottom summarises each class.