Continue
The request headers were received; the client can continue sending the request body.
Inspect & test
HTTP Status Lookup
Search common HTTP response codes by number, name, or meaning.
30 status codes
Switching Protocols
The server is switching protocols as requested.
OK
The request succeeded.
Created
The request succeeded and created a resource.
Accepted
The request was accepted for processing, but processing is not complete.
No Content
The request succeeded and there is no response body.
Partial Content
The server is returning the requested range of a resource.
Moved Permanently
The resource has a new permanent URL.
Found
The resource is temporarily available at another URL.
Not Modified
The cached representation can be used; the resource has not changed.
Temporary Redirect
The request should be repeated at another URL using the same method.
Permanent Redirect
The resource has a permanent URL change; the request method is preserved.
Bad Request
The server cannot process the request due to a client-side issue.
Unauthorized
Authentication is required or was not accepted.
Forbidden
The server understood the request but refuses to authorize it.
Not Found
The requested resource could not be found.
Method Not Allowed
The resource does not support the request method.
Request Timeout
The server timed out waiting for the request.
Conflict
The request conflicts with the current state of the resource.
Gone
The resource is no longer available and is not expected to return.
Content Too Large
The request content exceeds the server's accepted size.
Unsupported Media Type
The server does not support the request's media format.
I'm a Teapot
An April Fools' status defined by RFC 2324.
Unprocessable Content
The request syntax is valid, but its instructions cannot be processed.
Too Many Requests
The client sent too many requests in a given amount of time.
Internal Server Error
The server encountered an unexpected condition.
Not Implemented
The server does not support the functionality required to fulfill the request.
Bad Gateway
A gateway received an invalid response from an upstream server.
Service Unavailable
The server is temporarily unable to handle the request.
Gateway Timeout
A gateway did not receive a timely response from an upstream server.
Practical guide
Using the HTTP Status Lookup
Search common HTTP response codes and definitions.
Example
Input
Search: 404Expected result
404 Not Found — The requested resource could not be found.Supported inputs
- Search by a common status code, status name, or words in its description.
Limitations
- The directory covers a curated set of common HTTP status codes, not every registered or extension code.
Frequently asked questions
Why is a status code missing?
This lookup contains common codes rather than the complete IANA registry. Consult the relevant HTTP specification for less common codes.
Does this send a request?
No. It filters a local reference list and does not contact a server.