HTTP Status Codes
Search and browse HTTP status codes with their meanings, grouped by category.
Continue (Informational)
The server has received the request headers and the client should proceed to send the request body.
Switching Protocols (Informational)
The requester has asked the server to switch protocols.
OK (Success)
The request succeeded.
Created (Success)
The request succeeded and a new resource was created.
Accepted (Success)
The request has been received but not yet acted upon.
No Content (Success)
The request succeeded but there's no content to return.
Partial Content (Success)
Only part of the resource is being delivered, matching a Range header.
Moved Permanently (Redirection)
The resource has been permanently moved to a new URL.
Found (Redirection)
The resource temporarily resides at a different URL.
See Other (Redirection)
The response can be found at another URL using a GET request.
Not Modified (Redirection)
The resource hasn't changed since the last request, so the cached version can be used.
Temporary Redirect (Redirection)
Like 302, but guarantees the method and body won't change on redirect.
Permanent Redirect (Redirection)
Like 301, but guarantees the method and body won't change on redirect.
Bad Request (Client Error)
The server couldn't understand the request due to invalid syntax.
Unauthorized (Client Error)
Authentication is required and has failed or not been provided.
Payment Required (Client Error)
Reserved for future use, originally intended for digital payment systems.
Forbidden (Client Error)
The client doesn't have access rights to the content.
Not Found (Client Error)
The server can't find the requested resource.
Method Not Allowed (Client Error)
The request method is known but not supported by this resource.
Not Acceptable (Client Error)
No content matching the request's Accept headers is available.
Request Timeout (Client Error)
The server timed out waiting for the request.
Conflict (Client Error)
The request conflicts with the current state of the server.
Gone (Client Error)
The requested content has been permanently deleted and won't return.
Length Required (Client Error)
The request didn't specify the length of its content, which is required.
Payload Too Large (Client Error)
The request entity is larger than limits the server is willing to process.
URI Too Long (Client Error)
The URI requested is longer than the server is willing to interpret.
Unsupported Media Type (Client Error)
The media format of the requested data isn't supported.
I'm a Teapot (Client Error)
A 1998 April Fools' joke from RFC 2324 - servers occasionally use it as an easter egg.
Unprocessable Entity (Client Error)
The request was well-formed but contains semantic errors.
Too Early (Client Error)
The server is unwilling to risk processing a request that might be replayed.
Too Many Requests (Client Error)
The user has sent too many requests in a given amount of time (rate limiting).
Unavailable For Legal Reasons (Client Error)
The resource is unavailable due to a legal demand to deny access.
Internal Server Error (Server Error)
The server encountered an unexpected condition it doesn't know how to handle.
Not Implemented (Server Error)
The request method isn't supported by the server.
Bad Gateway (Server Error)
The server, acting as a gateway, received an invalid response from an upstream server.
Service Unavailable (Server Error)
The server isn't ready to handle the request, often due to maintenance or overload.
Gateway Timeout (Server Error)
The server, acting as a gateway, didn't get a response in time from an upstream server.
HTTP Version Not Supported (Server Error)
The HTTP version used in the request isn't supported by the server.
Network Authentication Required (Server Error)
The client needs to authenticate to gain network access, often seen on captive portals.
Recommended Settings
Pro Tips
- •The first digit of a status code tells you its category: 1xx informational, 2xx success, 3xx redirection, 4xx client error, 5xx server error
- •404 and 500 are by far the most commonly encountered codes, but understanding the full range helps you build more precise APIs
- •418 'I'm a Teapot' is a real, officially registered status code that started as an April Fools' joke in 1998
- •Search by category name (like 'redirect' or 'error') as well as by code number to explore related statuses
Most Popular
Most developers look up 4xx and 5xx codes when debugging why an API request failed
When to Use This Tool
Quickly find what a status code you haven't seen before actually means.
Pick the most semantically accurate status code when designing an API response.
Understand exactly why a request failed based on the status code returned.
Study how HTTP status codes are organized into meaningful categories.
How It Works
Search a curated reference list of standard HTTP status codes and their official meanings
Filter results instantly as you type, matching against the code, name, or description
Color-code each result by its category (informational, success, redirection, client error, server error)
100% Private
Files never leave your device. All processing happens locally in your browser.
Lightning Fast
Powered by Client-side static reference lookup for optimal performance on modern browsers.
Open Source
Built with verified, open-source libraries. Fully transparent.
Frequently Asked Questions
What's the difference between 401 and 403?
401 Unauthorized means authentication is missing or failed - the server doesn't know who you are. 403 Forbidden means the server knows who you are but you don't have permission to access the resource.
Why do I see 429 errors?
429 Too Many Requests means you've hit a rate limit - the server is asking you to slow down and retry after some time.
Is this list complete?
This covers the standard, widely used HTTP status codes defined in the relevant RFCs. A few very rarely used or vendor-specific codes aren't included.
Is my search sent anywhere?
No. Searching happens entirely locally against a static list in your browser.