loot.toolsHTTP Status Codes
Look up any HTTP status code by number, name, or meaning. Codes are grouped by class from 1xx informational through 5xx server errors, each with a plain-English explanation.
1xx Informational
100
Continue
The server received the request headers and the client should send 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 working on it, but no response is available yet.
103
Early Hints
Used to return some response headers before the final response, often to preload resources.
2xx Success
200
OK
The request succeeded. The meaning depends on the method used.
201
Created
The request succeeded and a new resource was created as a result.
202
Accepted
The request was received but not yet acted upon. Processing happens later.
203
Non-Authoritative Information
The returned metadata is from a copy, not the origin server.
204
No Content
The request succeeded but there is no content to send back.
205
Reset Content
Tells the client to reset the document that sent the request.
206
Partial Content
The server is delivering only part of the resource, used for range requests.
207
Multi-Status
Conveys information about multiple resources, used in WebDAV.
226
IM Used
The server fulfilled a GET request and the response is a result of instance manipulations.
3xx Redirection
300
Multiple Choices
The request has more than one possible response. The client should pick one.
301
Moved Permanently
The resource has a new permanent URL. Update your links.
302
Found
The resource is temporarily at a different URL. Keep using the original.
303
See Other
The response can be found at another URL using a GET request.
304
Not Modified
The cached version is still valid, so no need to re-send the resource.
307
Temporary Redirect
The resource is temporarily elsewhere, and the method must not change.
308
Permanent Redirect
The resource is permanently elsewhere, and the method must not change.
4xx Client Error
400
Bad Request
The server can't process the request due to a client error like malformed syntax.
401
Unauthorized
Authentication is required and has failed or not been provided.
402
Payment Required
Reserved for future use, sometimes used by APIs for billing or rate limits.
403
Forbidden
The server understood the request but refuses to authorize it.
404
Not Found
The server can't find the requested resource. The classic broken link.
405
Method Not Allowed
The request method is known but not supported for this resource.
406
Not Acceptable
The server can't produce a response matching the Accept headers.
407
Proxy Authentication Required
Authentication with a proxy is needed before the request can proceed.
408
Request Timeout
The server timed out waiting for the request.
409
Conflict
The request conflicts with the current state of the resource.
410
Gone
The resource is permanently gone with no forwarding address.
411
Length Required
The server requires a Content-Length header that wasn't provided.
412
Precondition Failed
A precondition in the request headers evaluated to false.
413
Payload Too Large
The request body is larger than the server is willing to process.
414
URI Too Long
The requested URL is longer than the server will interpret.
415
Unsupported Media Type
The request's media format isn't supported by the server.
416
Range Not Satisfiable
The requested range can't be fulfilled for the resource.
417
Expectation Failed
The expectation in the Expect header couldn't be met.
418
I'm a Teapot
An April Fools' joke from 1998. The server refuses to brew coffee.
422
Unprocessable Entity
The request was well-formed but had semantic errors, common in form validation.
425
Too Early
The server is unwilling to process a request that might be replayed.
426
Upgrade Required
The client should switch to a different protocol.
428
Precondition Required
The server requires the request to be conditional to avoid lost updates.
429
Too Many Requests
The client sent too many requests in a given time, hitting a rate limit.
431
Request Header Fields Too Large
The server won't process the request because its headers are too large.
451
Unavailable For Legal Reasons
The resource is blocked for legal reasons like a government takedown.
5xx Server Error
500
Internal Server Error
A generic error meaning the server hit an unexpected condition.
501
Not Implemented
The server doesn't support the functionality to fulfill the request.
502
Bad Gateway
The server, acting as a gateway, got an invalid response upstream.
503
Service Unavailable
The server is down for maintenance or overloaded. Try again later.
504
Gateway Timeout
The server, acting as a gateway, didn't get a timely upstream response.
505
HTTP Version Not Supported
The HTTP version used in the request isn't supported.
507
Insufficient Storage
The server can't store the representation needed to complete the request.
508
Loop Detected
The server detected an infinite loop while processing the request.
511
Network Authentication Required
The client needs to authenticate to gain network access, common on captive portals.