HTTP Status Code Reference
Look up and search HTTP response status codes with clear, accurate descriptions, entirely from a local reference table in your browser.
100
ContinueThe initial part of a request has been received and the client should continue sending the rest of it.
101
Switching ProtocolsThe server agrees to switch protocols as requested by the client, such as upgrading to WebSockets.
200
OKThe request succeeded and the response body contains the requested resource or result.
201
CreatedThe request succeeded and a new resource was created as a result, typically returned by POST requests.
202
AcceptedThe request has been accepted for processing, but the processing has not been completed yet.
204
No ContentThe request succeeded but there is no content to return in the response body.
206
Partial ContentThe server is delivering only part of the resource due to a range header sent by the client.
301
Moved PermanentlyThe requested resource has been permanently moved to a new URL given in the Location header.
302
FoundThe requested resource temporarily resides at a different URL, and future requests should still use the original URL.
303
See OtherThe response to the request can be found at another URL using a GET request, commonly used after a POST.
304
Not ModifiedThe cached version of the resource is still valid, so the client should use it instead of re-downloading.
307
Temporary RedirectThe resource temporarily resides at a different URL, and the request method and body must be repeated unchanged.
308
Permanent RedirectThe resource has permanently moved to a new URL, and the request method and body must be repeated unchanged.
400
Bad RequestThe server could not understand the request due to malformed syntax or invalid parameters.
401
UnauthorizedThe request lacks valid authentication credentials for the requested resource.
402
Payment RequiredReserved for future use; originally intended for digital payment systems.
403
ForbiddenThe server understood the request but refuses to authorize it, regardless of authentication.
404
Not FoundThe server cannot find the requested resource, or the endpoint does not exist.
405
Method Not AllowedThe HTTP method used is not supported for the requested resource.
406
Not AcceptableThe server cannot produce a response matching the content types acceptable to the client.
408
Request TimeoutThe server timed out waiting for the request to be completed by the client.
409
ConflictThe request conflicts with the current state of the target resource, such as an edit conflict.
410
GoneThe requested resource is no longer available and has been permanently removed.
411
Length RequiredThe server requires a Content-Length header, which was not specified in the request.
412
Precondition FailedA precondition given in a conditional request header was not met by the server.
413
Payload Too LargeThe request body is larger than the server is willing or able to process.
414
URI Too LongThe requested URI is longer than the server is willing to interpret.
415
Unsupported Media TypeThe request body's media type is not supported by the server or resource.
418
I'm a TeapotA humorous status code from an April Fools' RFC, indicating the server refuses to brew coffee because it is a teapot.
422
Unprocessable EntityThe request is well-formed but contains semantic errors, such as failing validation rules.
425
Too EarlyThe server is unwilling to risk processing a request that might be replayed, sent in an early-data TLS handshake.
426
Upgrade RequiredThe server refuses to process the request using the current protocol and requires an upgrade.
428
Precondition RequiredThe origin server requires the request to be conditional, typically to prevent lost update conflicts.
429
Too Many RequestsThe client has sent too many requests in a given time period and is being rate limited.
431
Request Header Fields Too LargeThe server refuses to process the request because its header fields are too large.
451
Unavailable For Legal ReasonsThe resource is unavailable due to a legal demand, such as government-mandated content removal.
500
Internal Server ErrorThe server encountered an unexpected condition that prevented it from fulfilling the request.
501
Not ImplementedThe server does not support the functionality required to fulfill the request.
502
Bad GatewayThe server, acting as a gateway or proxy, received an invalid response from an upstream server.
503
Service UnavailableThe server is temporarily unable to handle the request, often due to overload or maintenance.
504
Gateway TimeoutThe server, acting as a gateway or proxy, did not receive a timely response from an upstream server.
505
HTTP Version Not SupportedThe server does not support the HTTP protocol version used in the request.
507
Insufficient StorageThe server is unable to store the representation needed to complete the request due to storage limits.
511
Network Authentication RequiredThe client needs to authenticate to gain network access, typically shown by captive portals.
Frequently Asked Questions
Is my data sent to a server when using the HTTP Status Code Reference?
No. The HTTP Status Code Reference is a fully client-side utility. All data processing, calculations, and conversions are handled locally in your browser. No input text, payloads, or keys are uploaded to any external server.
What do the 1xx-5xx status code ranges broadly mean?
1xx codes are informational responses, 2xx indicate success, 3xx signal redirection, 4xx indicate a client-side error such as a bad request or missing resource, and 5xx indicate a server-side error.
Does this tool call an external API to fetch status code data?
No. The status code list is a fully static local reference table bundled with the page, so lookups work instantly and offline without any network request.
Is this reference exhaustive of every registered status code?
It covers all commonly encountered and referenced IANA HTTP status codes used in everyday API and web development, though it is not an exhaustive listing of every rarely-used registered code.
Does the HTTP Status Code Reference store history or cache my inputs?
No. The application runs entirely in browser memory. Once you refresh the tab, navigate away, or close the window, all inputted details, logs, and outputs are completely cleared.
Is the HTTP Status Code Reference compatible with mobile devices?
Yes. The interface is optimized to be fully responsive. You can perform calculations, conversions, and formats on all modern mobile, tablet, and desktop web browsers.
Does the HTTP Status Code Reference work offline?
Yes. Once loaded, all code and assets required to run the HTTP Status Code Reference reside in your browser cache, enabling offline use without an active network connection.