HTTP Status Codes & Headers Explorer
Instant search directory for HTTP status codes (100–599), RFC definitions, causes, and standard headers.
Continue
Server received request headers and client should proceed to send the body.
Switching Protocols
Server is switching protocols to the one requested in Upgrade header.
Processing
Server has received and is processing the request, but no response is available yet.
Early Hints
Used to return headers before final HTTP message to preload critical assets.
OK
Standard response for successful HTTP requests.
Created
Request succeeded and led to the creation of a new resource.
Accepted
Request has been accepted for processing, but processing is not completed.
No Content
Server successfully processed request and is not returning any content.
Partial Content
Server is delivering only part of the resource due to Range header.
Moved Permanently
Resource has been assigned a new permanent URI.
Found
Resource resides temporarily under a different URI.
Not Modified
Resource has not been modified since version specified in request headers.
Temporary Redirect
Temporary redirect that guarantees the HTTP method will not change.
Permanent Redirect
Permanent redirect that guarantees the HTTP method will not change.
Bad Request
Server cannot or will not process request due to perceived client error.
Unauthorized
Authentication is required and has failed or not yet been provided.
Forbidden
Server understood request but refuses to authorize it.
Not Found
Origin server did not find a current representation for target resource.
Method Not Allowed
Request method is known by server but not supported by target resource.
Request Timeout
Server did not receive complete request within its timeout period.
Conflict
Request could not be completed due to a conflict with resource state.
Gone
Target resource is no longer available at origin server and no forwarding address is known.
Payload Too Large
Request entity is larger than limits defined by server.
I'm a teapot
Server refuses attempt to brew coffee with a teapot (HTCPCP).
Unprocessable Content
Request syntax is valid, but server was unable to process contained instructions.
Too Many Requests
User has sent too many requests in a given amount of time (rate limiting).
Internal Server Error
Server encountered an unexpected condition that prevented it from fulfilling request.
Not Implemented
Server does not support the functionality required to fulfill request.
Bad Gateway
Server acting as gateway/proxy received an invalid response from inbound server.
Service Unavailable
Server is currently unable to handle request due to temporary overload or maintenance.
Gateway Timeout
Server acting as gateway/proxy did not receive timely response from upstream server.