HTTP Status Codes
Look up HTTP response status codes with plain-language explanations, search, and category filters locally in your browser.
This tool runs entirely in your browser. Your input is never uploaded.
- 100
Continue
The client should continue with the request body.
- 101
Switching Protocols
The server is switching protocols as requested by the client.
- 102
Processing
The server has received the request and is still processing; no response is available yet.
- 103
Early Hints
Early hints about resources the page will need, sent before the final response.
- 200
OK
The request succeeded. The meaning depends on the HTTP method.
- 201
Created
A new resource was created as a result of the request.
- 202
Accepted
The request was accepted for processing but is not complete yet.
- 203
Non-Authoritative Information
The returned metadata came from a local or third-party copy, not the origin server.
- 204
No Content
The request succeeded and there is no content to send in the response body.
- 205
Reset Content
The client should reset the document view that caused the request.
- 206
Partial Content
The server is delivering only part of the resource due to a range header.
- 300
Multiple Choices
The request has multiple possible responses; the client should choose one.
- 301
Moved Permanently
The resource has permanently moved to the URL given in Location.
- 302
Found
The resource temporarily lives at a different URL; keep using the original.
- 303
See Other
Fetch the resource from another URI using GET.
- 304
Not Modified
The cached version is still valid; the body is omitted.
- 307
Temporary Redirect
Temporary redirect that keeps the original HTTP method.
- 308
Permanent Redirect
Permanent redirect that keeps the original HTTP method.
- 400
Bad Request
The server cannot process the request due to malformed syntax or invalid input.
- 401
Unauthorized
Authentication is required and has failed or has not been provided.
- 402
Payment Required
Reserved for payment; not commonly used in practice.
- 403
Forbidden
The server understood the request but refuses to authorize it.
- 404
Not Found
The requested resource could not be found on the server.
- 405
Method Not Allowed
The HTTP method is not supported by this resource.
- 406
Not Acceptable
The resource cannot produce a response matching the Accept headers.
- 407
Proxy Authentication Required
Authentication with the proxy is required first.
- 408
Request Timeout
The client took too long to send the request; the server timed out waiting.
- 409
Conflict
The request conflicts with the current state of the resource.
- 410
Gone
The resource is gone permanently and no forwarding address exists.
- 411
Length Required
The server requires a Content-Length header for this request.
- 412
Precondition Failed
A precondition in the request headers evaluated to false.
- 413
Content Too Large
The request body is larger than the server is willing to process.
- 414
URI Too Long
The request URL is longer than the server can interpret.
- 415
Unsupported Media Type
The media format of the request body is not supported.
- 416
Range Not Satisfiable
The requested range cannot be satisfied by the resource.
- 417
Expectation Failed
The expectation given in the Expect header could not be met.
- 418
I'm a teapot
The server refuses to brew coffee because it is a teapot.
- 421
Misdirected Request
The request was sent to a server unable to produce a response.
- 422
Unprocessable Content
The request was well-formed but contained semantic errors.
- 423
Locked
The source or destination resource is locked.
- 424
Failed Dependency
A dependency of this request failed.
- 425
Too Early
The server is unwilling to risk processing a request that might be replayed.
- 426
Upgrade Required
The client must switch to a different protocol to continue.
- 428
Precondition Required
The request must be conditional to avoid lost-update problems.
- 429
Too Many Requests
The client has sent too many requests in a given amount of time.
- 431
Request Header Fields Too Large
The request header fields are too large to process.
- 451
Unavailable For Legal Reasons
The resource is unavailable for legal reasons.
- 500
Internal Server Error
The server hit an unexpected condition that prevented it from fulfilling the request.
- 501
Not Implemented
The server does not support the functionality required to fulfill the request.
- 502
Bad Gateway
The gateway or proxy received an invalid response from an upstream server.
- 503
Service Unavailable
The service is temporarily overloaded or down for maintenance.
- 504
Gateway Timeout
The gateway or proxy timed out waiting for an upstream response.
- 505
HTTP Version Not Supported
The HTTP protocol version used in the request is not supported.
- 507
Insufficient Storage
The server cannot store the representation needed to complete the request.
- 508
Loop Detected
The server detected an infinite loop while processing the request.
- 510
Not Extended
A required extension to the request is not supported.
- 511
Network Authentication Required
Network access requires authentication, such as a captive portal login.
HTTP Status Codes
Browse the most common HTTP response status codes, from informational 1xx responses through successful 2xx, redirections, client errors, and server errors. Every code includes a clear explanation of when the server returns it and what developers usually need to do next.
You can filter by code number, keyword, or category to quickly find the status you need while writing APIs, debugging responses, or reading specification documents. All data stays local in the browser and nothing is sent anywhere.