HTTP status codes
Searchable list of HTTP status codes with plain-English meanings.
Runs in this tab. The file stays here.
55 of 55 entries
100 · Continue
Request received; client may continue.
101 · Switching Protocols
Server is switching protocols.
102 · Processing
Server is still working on the request (WebDAV).
103 · Early Hints
Preload hints sent before the final response.
200 · OK
Request succeeded.
201 · Created
Resource created.
202 · Accepted
Request accepted for processing.
203 · Non-Authoritative Information
Response modified by a transforming proxy.
204 · No Content
Success with empty body.
205 · Reset Content
Success; client should reset the document view.
206 · Partial Content
Part of the resource returned for a Range request.
207 · Multi-Status
Multiple status codes in one body (WebDAV).
226 · IM Used
Response is the result of instance manipulations (RFC 3229).
300 · Multiple Choices
Several representations are available.
301 · Moved Permanently
Resource has a new permanent URI.
302 · Found
Temporary redirect.
303 · See Other
Fetch the result with GET at another URI.
304 · Not Modified
Cached response is still valid.
307 · Temporary Redirect
Retry with same method at new URI.
308 · Permanent Redirect
Permanent redirect; keep method.
400 · Bad Request
Malformed or invalid request.
401 · Unauthorized
Authentication required.
403 · Forbidden
Authenticated but not allowed.
404 · Not Found
Resource does not exist.
405 · Method Not Allowed
HTTP method not supported.
406 · Not Acceptable
No representation matches the Accept headers.
407 · Proxy Authentication Required
Authenticate with the proxy first.
408 · Request Timeout
Client took too long.
409 · Conflict
State conflict with current resource.
410 · Gone
Resource permanently removed.
411 · Length Required
Content-Length header is required.
412 · Precondition Failed
A conditional header evaluated to false.
413 · Payload Too Large
Request body too large.
414 · URI Too Long
Request URI exceeds what the server accepts.
415 · Unsupported Media Type
Payload format not supported.
416 · Range Not Satisfiable
Requested range is outside the resource.
417 · Expectation Failed
Server cannot meet the Expect header.
418 · I'm a teapot
April Fools' joke status (RFC 2324).
421 · Misdirected Request
Sent to a server that cannot respond for this URI.
422 · Unprocessable Entity
Semantically invalid payload.
423 · Locked
Resource is locked (WebDAV).
425 · Too Early
Server will not risk replaying the request.
426 · Upgrade Required
Switch to a different protocol to continue.
428 · Precondition Required
Request must be conditional.
429 · Too Many Requests
Rate limit exceeded.
431 · Request Header Fields Too Large
Headers are too large.
451 · Unavailable For Legal Reasons
Blocked for legal reasons.
500 · Internal Server Error
Unexpected server failure.
501 · Not Implemented
Method not supported by server.
502 · Bad Gateway
Invalid response from upstream.
503 · Service Unavailable
Server temporarily overloaded.
504 · Gateway Timeout
Upstream timed out.
505 · HTTP Version Not Supported
Server does not support this HTTP version.
507 · Insufficient Storage
Server cannot store the representation (WebDAV).
511 · Network Authentication Required
Client must authenticate to gain network access.
This runs in your browser. Nothing is uploaded.
About HTTP status codes
A searchable list of 55 HTTP status codes with one-line meanings. The data is bundled with the page, so it works offline once loaded.
Type a code or a word into the search box and the list narrows to matching entries, each shown as the code and name on one line with a short description under it. A counter above the list tells you how many of the 55 entries match. The search looks at the number, the name and the description, so 404, found and rate limit all work, though a short search like 4 matches a lot.
The list covers the standard 1xx to 5xx codes plus 226 and the joke 418, and it includes the WebDAV ones such as 207 and 423. Entries stay short on purpose. The aim is to remind you whether a 401 or a 403 is the one you want, or what 409 and 422 are for, not to replace the RFCs. It does not group the codes by class, so use the search box to narrow by first digit if you need to.
There is no copy button and no links to the specifications, and the list leaves out many vendor codes such as the 499 some proxies use and the 5xx variants from CDNs. It also says nothing about how your own server should use a code, only what the standard means. When a precise answer matters, for example redirect behaviour for POST requests, read the relevant RFC. The lookup is local, so no request is made when you search.
How to use HTTP status codes
- 1Type a status code or a keyword into the search box.
- 2Read the code, name and description in each matching entry.
- 3Clear the box to see all 55 entries again.
What it won't do
- 55 entries with one-line descriptions, not the full RFC text.
- No grouping by class, no copy button and no specification links.
- Vendor-specific codes are mostly absent.
Common questions
What is the difference between a 401 and a 403 status code?
401 means the request lacks valid credentials, so authenticating may fix it. 403 means the server understood who you are and refuses anyway, so logging in again will not help.
Does the HTTP status code list include non-standard codes?
Only a few. It has 418 (a joke code from RFC 2324) and the WebDAV set, but not vendor codes like 499 or CDN-specific 5xx errors. If you need those, check your proxy or CDN documentation.
Which status code should I use for a rate limit or a missing resource?
Use 429 Too Many Requests for rate limits and 404 Not Found for a resource that does not exist. Search for either number here to see the one-line meaning, then check the RFC if you need exact header behaviour.
Does the HTTP status code search send my query anywhere?
No. The list ships with the page and the filter runs in the tab, so nothing is requested when you type.
Related tools
Why this one doesn't upload your file
There is no server to upload to. This page is a static file, and the work happens in your browser using the same graphics and WebAssembly code that renders every other site you visit. Your file is read from disk into memory, processed, and handed back as a download. Once the page has loaded you can disconnect from the network entirely and it keeps working. The longer explanation