HTTP Status Code Checker
Comprehensive reference guide for all HTTP status codes with search and filtering
Advertisement
Continue
The server has received the request headers, and the client should proceed to send the request body.
Switching Protocols
The requester has asked the server to switch protocols.
Processing
The server has received and is processing the request, but no response is available yet.
Early Hints
Used to return some response headers before final HTTP message.
OK
Standard response for successful HTTP requests.
Created
The request has been fulfilled and a new resource has been created.
Accepted
The request has been accepted for processing, but the processing has not been completed.
Non-Authoritative Information
The server successfully processed the request but is returning information from another source.
No Content
The server successfully processed the request but is not returning any content.
Reset Content
The server successfully processed the request, but is not returning any content and requires the requester to reset the document view.
Partial Content
The server is delivering only part of the resource due to a range header sent by the client.
Multiple Choices
The request has more than one possible response.
Moved Permanently
This and all future requests should be directed to the given URI.
Found
The resource was found but at a different URI.
See Other
The response can be found under a different URI using GET method.
Not Modified
The resource has not been modified since the last request.
Temporary Redirect
The request should be repeated with another URI but future requests should use the original URI.
Permanent Redirect
The request and all future requests should be repeated using another URI.
Bad Request
The server cannot process the request due to a client error (e.g., malformed request syntax).
Unauthorized
Authentication is required and has failed or has not been provided.
Payment Required
Reserved for future use. Originally intended for digital payment systems.
Forbidden
The client does not have access rights to the content.
Not Found
The server cannot find the requested resource.
Method Not Allowed
The request method is not supported for the requested resource.
Not Acceptable
The requested resource is capable of generating only content not acceptable according to the Accept headers.
Proxy Authentication Required
The client must first authenticate itself with the proxy.
Request Timeout
The server timed out waiting for the request.
Conflict
The request conflicts with the current state of the server.
Gone
The requested resource is no longer available and will not be available again.
Length Required
The request did not specify the length of its content, which is required.
Precondition Failed
The server does not meet one of the preconditions specified in the request headers.
Payload Too Large
The request entity is larger than limits defined by server.
URI Too Long
The URI provided was too long for the server to process.
Unsupported Media Type
The request entity has a media type which the server does not support.
Range Not Satisfiable
The client has asked for a portion of the file, but the server cannot supply that portion.
Expectation Failed
The server cannot meet the requirements of the Expect request-header field.
I'm a teapot
The server refuses to brew coffee because it is a teapot (April Fools' joke from RFC 2324).
Misdirected Request
The request was directed at a server that is not able to produce a response.
Unprocessable Entity
The request was well-formed but unable to be followed due to semantic errors.
Locked
The resource that is being accessed is locked.
Failed Dependency
The request failed due to failure of a previous request.
Too Early
The server is unwilling to risk processing a request that might be replayed.
Upgrade Required
The client should switch to a different protocol.
Precondition Required
The origin server requires the request to be conditional.
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
Request Header Fields Too Large
The server is unwilling to process the request because header fields are too large.
Unavailable For Legal Reasons
The resource is unavailable due to legal reasons.
Internal Server Error
A generic error message when the server encounters an unexpected condition.
Not Implemented
The server does not support the functionality required to fulfill the request.
Bad Gateway
The server received an invalid response from an upstream server.
Service Unavailable
The server is currently unavailable (overloaded or down for maintenance).
Gateway Timeout
The server did not receive a timely response from an upstream server.
HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
Variant Also Negotiates
Transparent content negotiation results in a circular reference.
Insufficient Storage
The server is unable to store the representation needed to complete the request.
Loop Detected
The server detected an infinite loop while processing the request.
Not Extended
Further extensions to the request are required for the server to fulfill it.
Network Authentication Required
The client needs to authenticate to gain network access.
Advertisement
Understanding HTTP Status Codes
HTTP status codes are three-digit numbers returned by web servers to indicate the result of an HTTP request. Every time you visit a website, submit a form, or make an API request, the server responds with a status code that tells your browser or application whether the request was successful, if there was an error, or if further action is needed.
Status codes are organized into five categories based on their first digit: 1xx codes provide informational responses, 2xx codes indicate success, 3xx codes handle redirections, 4xx codes represent client errors, and 5xx codes indicate server errors. Understanding these codes is essential for web developers, debugging API integrations, and troubleshooting website issues.
The most commonly encountered status codes include 200 OK (successful request), 301 Moved Permanently (permanent redirect), 404 Not Found (resource doesn't exist), and 500 Internal Server Error (server-side problem). Each code provides specific information about what happened during the request-response cycle, helping developers quickly identify and fix issues.
This tool provides a comprehensive, searchable reference for all standard HTTP status codes defined in the HTTP specification. Whether you're debugging a web application, designing a RESTful API, or learning about web protocols, you can quickly look up any status code to understand its meaning and appropriate use cases.
Frequently Asked Questions
What is an HTTP status code?
An HTTP status code is a 3-digit number returned by a web server to indicate the result of an HTTP request. The first digit indicates the category: 1xx (informational), 2xx (success), 3xx (redirection), 4xx (client error), or 5xx (server error).
What does a 404 error mean?
A 404 Not Found error means the server cannot find the requested resource. This is usually because the URL is incorrect, the page has been moved or deleted, or the resource never existed. It's one of the most common HTTP status codes.
What's the difference between 301 and 302 redirects?
A 301 Moved Permanently redirect indicates the resource has permanently moved to a new URL, and search engines should update their indexes. A 302 Found redirect is temporary, meaning the resource might return to the original URL, so search engines keep the original URL indexed.
What causes a 500 Internal Server Error?
A 500 Internal Server Error is a generic error message indicating the server encountered an unexpected condition that prevented it from fulfilling the request. Common causes include server misconfigurations, programming errors, database connection issues, or resource exhaustion.
What does 429 Too Many Requests mean?
A 429 Too Many Requests status code indicates rate limiting is in effect. The client has sent too many requests in a given timeframe, and the server is refusing to process additional requests until the rate limit resets. This is commonly used in APIs to prevent abuse.
What is a 418 I'm a teapot status code?
418 I'm a teapot is a humorous HTTP status code from RFC 2324 (Hyper Text Coffee Pot Control Protocol) created as an April Fools' joke in 1998. It indicates the server refuses to brew coffee because it is, permanently, a teapot. Some servers actually implement this as an Easter egg.