~/devtools / http-status
tool::http-status
HTTP Status
Codes
Browse and search all HTTP status codes from 1xx to 5xx with descriptions.
61 / 61
Client should continue with the request.
Server is switching protocols as requested.
Server has received the request but has not yet completed it.
Used to preload resources while the server is still processing.
The request has succeeded.
The request has been fulfilled and a new resource has been created.
The request has been accepted but not yet acted upon.
The response is from a transforming proxy, not the origin server.
The server successfully processed the request but returns no content.
The server processed the request; the client should reset the document view.
The server is returning partial content due to a Range header.
Multiple status codes for multiple independent operations (WebDAV).
Members of a DAV binding have already been enumerated.
The server fulfilled the request using instance manipulations.
Multiple options for the requested resource.
The resource has permanently moved to a new URL.
The resource is temporarily at a different URL.
Redirect to another resource using GET.
The cached version is still valid; no new content to return.
Temporary redirect preserving the original HTTP method.
Permanent redirect preserving the original HTTP method.
The server could not understand the request due to invalid syntax.
Authentication is required and has failed or not been provided.
Reserved for future use; some services use it for payment walls.
The server refuses to fulfill the request (authenticated but unauthorized).
The requested resource could not be found.
The HTTP method is not supported for this resource.
No content matching the Accept headers is available.
Authentication with a proxy is required.
The server timed out waiting for the request.
The request conflicts with the current state of the server.
The resource has been permanently deleted and will not return.
The Content-Length header is required but not provided.
One or more conditions in the request headers evaluated to false.
The request body exceeds the server's size limit.
The request URI is longer than the server can process.
The media type of the request is not supported.
The range specified in the Range header cannot be fulfilled.
The expectation in the Expect header cannot be met.
The server refuses to brew coffee; it is a teapot (RFC 2324).
The request was directed at a server unable to produce a response.
The request is well-formed but contains semantic errors.
The resource being accessed is locked (WebDAV).
The request failed because a previous request failed (WebDAV).
The server is unwilling to process a potentially replayed request.
The client should switch to a different protocol.
The server requires the request to be conditional.
The user has sent too many requests in a given time (rate limiting).
Request headers are too large for the server to process.
The resource is unavailable due to legal restrictions.
The server encountered an unexpected condition.
The server does not support the requested functionality.
The gateway received an invalid response from an upstream server.
The server is temporarily unable to handle the request.
The gateway did not receive a timely response from an upstream server.
The HTTP version used in the request is not supported.
A circular reference in transparent content negotiation.
The server is unable to store the representation (WebDAV).
An infinite loop was detected while processing the request (WebDAV).
Further extensions to the request are required.
Network authentication is required before accessing resources.
ad · 300×250
// about this tool
About HTTP Status Codes
HTTP status codes are three-digit numbers that a server returns in response to a client's request. The first digit classifies the response: 1xx for informational, 2xx for success, 3xx for redirection, 4xx for client errors, and 5xx for server errors. This system was introduced in HTTP/1.0 (RFC 1945, 1996) and continues through HTTP/2 and HTTP/3 today.
The most frequently encountered codes in practice are 200 (OK), 201 (Created), 301 (Moved Permanently), 302 (Found), 400 (Bad Request), 401 (Unauthorized), 403 (Forbidden), 404 (Not Found), and 500 (Internal Server Error). Understanding subtle distinctions — like 401 vs 403 (authentication failure vs authorization denial) or 301 vs 302 (permanent vs temporary redirect) — is essential for correct API design and SEO.
This tool lists all standard HTTP status codes from 1xx to 5xx, organized by category tabs with real-time search by code number or name. Click any code to copy it to the clipboard. Use it as a quick reference while designing REST APIs, debugging server responses, or learning web development.
Common Use Cases
- ▸Look up the exact meaning of an unfamiliar HTTP status code
- ▸Reference correct status codes when designing REST APIs
- ▸Debug HTTP errors returned by servers or third-party APIs
- ▸Verify correct use of redirect codes (301 vs 302 vs 307 vs 308)
- ▸Check authentication error distinctions (401 vs 403)
Frequently Asked Questions
Q. What is the difference between 401 and 403?
401 Unauthorized means authentication is required or has failed — the server doesn't know who you are. 403 Forbidden means authentication succeeded but the authenticated user does not have permission to access the resource — the server knows who you are but won't let you in.
Q. When should I use 301 vs 302 vs 307 vs 308?
301 (Moved Permanently) and 308 (Permanent Redirect) are for permanent URL changes — search engines transfer link equity to the new URL. 302 (Found) and 307 (Temporary Redirect) are for temporary redirects — search engines keep indexing the original URL. The key difference between 301/302 and 307/308 is that 307/308 preserve the HTTP method (e.g. POST stays POST), while 301/302 historically changed POST to GET.
Q. Is 418 I'm a Teapot a real HTTP status code?
Yes — it was defined in RFC 2324 as an April Fools' joke in 1998 and is registered in the IANA HTTP Status Code Registry. It is occasionally used in real APIs as a humorous rejection response. It is not intended for production use per the spec, but it's technically valid and widely recognized.