No status codes match your search.
1xx
Informational
4 codesProvisional responses indicating the request was received and processing is continuing. Rarely seen in everyday redirect chains.
100
Continue
The server has received the request headers; the client should proceed to send the body.
101
Switching Protocols
The server is switching protocols as requested, e.g. upgrading to WebSocket.
102
Processing
The server has received the request and is processing it, but no response is available yet.
103
Early Hints
Allows the browser to start preloading resources while the server prepares the full response.
2xx
Success
10 codesThe request was successfully received, understood, and accepted. A 200 at the end of a redirect chain means you've reached the final destination.
200
OK
The request succeeded. The most common response code — the page loaded successfully.
201
Created
The request succeeded and a new resource was created as a result.
202
Accepted
The request has been received but processing is not yet complete.
203
Non-Authoritative Information
The response is from a third-party copy, not the origin server.
204
No Content
The request succeeded but there is no content to return in the response body.
205
Reset Content
The request succeeded; the client should reset the document view.
206
Partial Content
The server is delivering only part of the resource in response to a range request.
207
Multi-Status
Conveys information about multiple resources where multiple status codes are appropriate.
208
Already Reported
Used in a 207 response to avoid enumerating members of a binding multiple times.
226
IM Used
The server has fulfilled a GET request and the response is a result of instance manipulations.
3xx
Redirection
9 codesThe backbone of URL shorteners. Each 3xx tells the browser to look for the resource at a different URL, forming the hops you see in a redirect chain.
300
Multiple Choices
The request has more than one possible response; the user or browser should choose one.
301
Moved Permanently
The resource has permanently moved to a new URL. Browsers and search engines update their records.
302
Found
The resource has temporarily moved. The most common redirect code used by URL shorteners.
303
See Other
The response can be found at another URL using GET. Typically used after a form POST.
304
Not Modified
The cached version of the resource is still valid; the browser should use it.
305
Use Proxy
The requested resource can only be accessed through a specific proxy server.
306
Unused
It has since been deprecated and is now reserved.
307
Temporary Redirect
A temporary redirect that strictly preserves the original HTTP method.
308
Permanent Redirect
Like 301 but strictly preserves the HTTP method. The modern alternative to 301.
4xx
Client Errors
29 codesThe request itself has a problem — a bad URL, missing authentication, or a resource that no longer exists. A 4xx at the end of a chain means the destination has an issue.
400
Bad Request
The server couldn't understand the request due to invalid syntax or a malformed URL.
401
Unauthorised
Authentication is required. The request lacks valid credentials.
402
Payment Required
Reserved for future use; sometimes used to indicate a paywall or payment barrier.
403
Forbidden
The server understood the request but refuses to authorise it. Access is denied.
404
Not Found
The server can't find the requested resource. The URL may be wrong or the page deleted.
405
Method Not Allowed
The HTTP method used is not supported for the target resource.
406
Not Acceptable
The server can't produce a response matching the criteria given by the client.
407
Proxy Authentication Required
Authentication with a proxy server is required before this request can be served.
408
Request Timeout
The server timed out waiting for the client to send a complete request.
409
Conflict
The request conflicts with the current state of the server.
410
Gone
The resource has been permanently deleted and will not be available again.
411
Length Required
The server requires a Content-Length header that was not supplied.
412
Precondition Failed
One or more conditions in the request header fields evaluated to false.
413
Content Too Large
The request body exceeds the limit the server is willing to process.
414
URI Too Long
The URL provided is longer than the server is willing to interpret.
415
Unsupported Media Type
The media format of the request is not supported by the server.
416
Range Not Satisfiable
The requested byte range cannot be fulfilled by the server.
417
Expectation Failed
The expectation given in the Expect request header could not be met.
418
I'm a Teapot
An April Fools' joke from 1998. The server refuses to brew coffee because it is a teapot.
421
Misdirected Request
The request was directed at a server not able to produce a response for that scheme and authority.
422
Unprocessable Content
The request was well-formed but contains semantic errors the server can't process.
423
Locked
The resource being accessed is locked.
424
Failed Dependency
The request failed because it depended on another request that also failed.
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 specified in an Upgrade header.
428
Precondition Required
The origin server requires the request to be conditional to prevent lost updates.
429
Too Many Requests
The user has sent too many requests in a given time. Rate limiting is in effect.
431
Request Header Fields Too Large
The server won't process the request because its header fields are too large.
451
Unavailable For Legal Reasons
The resource can't be provided due to legal demands, such as government censorship.
5xx
Server Errors
13 codesThe server failed to fulfil a valid request. These are problems on the destination server's side — not with the URL itself.
500
Internal Server Error
A generic server-side error. Something unexpected went wrong on the destination server.
501
Not Implemented
The server does not support the functionality required to fulfil the request.
502
Bad Gateway
The server was acting as a gateway and received an invalid response from an upstream server.
503
Service Unavailable
The server is temporarily unable to handle requests — overloaded or down for maintenance.
504
Gateway Timeout
The server acting as a gateway did not receive a timely response from an upstream server.
505
HTTP Version Not Supported
The HTTP protocol version used in the request is not supported by the server.
506
Variant Also Negotiates
The server has an internal configuration error in content negotiation.
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
Further extensions to the request are required for the server to fulfil it.
511
Network Authentication Required
The client needs to authenticate to gain network access, e.g. a captive portal.
521
Web Server Is Down
Cloudflare-specific: the origin web server refused the connection from Cloudflare.
525
SSL Handshake Failed
Cloudflare-specific: the SSL/TLS handshake between Cloudflare and the origin server failed.