HTTP Status Code Query
Quickly look up HTTP status code meanings, understand network request responses, server errors, and client errors.
Green Tool
1xx Status: Informational Response
1xx series status codes indicate that the request has been received and the requestor should continue with the action.
100
Continue
The requestor should continue with the request. The server returns this code to indicate that it has received the first part of the request and is waiting for the rest.
The server has received the request headers and the client should proceed to send the request body.
101
Switching Protocols
The requestor has asked the server to switch protocols, and the server has confirmed and is ready to switch.
The requester has asked the server to switch protocols and the server has agreed to do so.
2xx Status: Success
2xx series status codes indicate that the request was successfully processed.
200
Success
The server has successfully processed the request. Usually, this means the server has provided the requested web page.
Standard response for successful HTTP requests.
201
Created
The request was successful, and the server created a new resource.
The request has been fulfilled, resulting in the creation of a new resource.
202
Accepted
The server has accepted the request but has not yet processed it.
The request has been accepted for processing, but the processing has not been completed.
203
Non-Authoritative Information
The server has successfully processed the request, but the returned information may be from another source.
The server is a transforming proxy that received a 200 OK from its origin, but is returning a modified version of the origin's response.
204
No Content
The server successfully processed the request but did not return any content.
The server successfully processed the request and is not returning any content.
205
Reset Content
The server successfully processed the request but did not return any content. This response requires the browser to reset the content it displays.
The server successfully processed the request, but is not returning any content. This response requires that the requester reset the document view.
206
Partial Content
The server successfully returned part of the resource because the client sent a
range header.The server is delivering only part of the resource due to a range header sent by the client.
3xx Status: Redirection
3xx series status codes indicate that further action is needed to complete the request. Usually, these status codes are used for redirection.
300
Multiple Choices
The server can perform multiple actions for different requests. The server can perform the corresponding action based on the requestor's choice, or provide a list of actions for the requestor to choose from.
Indicates that multiple options for the resource from which the client may choose.
301
Moved Permanently
The requested web page has been permanently moved to a new location. For GET or HEAD requests, when the server returns this response, it will automatically redirect the requestor to the new location.
Indicates the resource had been moved to another location permanently. This and all future requests should be directed to the given URI.
302
Found (Moved Temporarily)
Tells the client to get the required resource from another URL (this status has been superseded by 303 and 307 statuses).
Tells the client to look at (browse to) another URL (302 code has been superseded by 303 and 307).
303
See Other
The server returns this code when the requestor should use a separate GET request to a different location to obtain the resource.
The response to the request can be found under another URI using the GET method.
304
Not Modified
The web page has not been modified since the last request. When the server returns this response, it will not return the content of the web page.
Indicates that the resource has not been modified since the version specified by the request headers
If-Modified-Since or If-None-Match.
305
Use Proxy
The requestor can only access the requested resource using a proxy. The resource address will be included in the response (for security reasons, many clients will not comply with this response status).
The requested resource is available only through a proxy, the address for which is provided in the response.
306
Switch Proxy
Subsequent requests should use the specified proxy (this status code is no longer used in the latest HTTP specification).
No longer used. Subsequent requests should use the specified proxy.
307
Temporary Redirect
The requestor should re-initiate a request with another URL, but subsequent requests should still use the original URL.
The request should be repeated with another URI; however, future requests should still use the original URI.
308
Permanent Redirect
The current request and all future requests should be made to another URL.
The request and all future requests should be repeated using another URI.
4xx Status: Client Error
4xx series status codes indicate that a client request may have caused an error, preventing the server from processing it.
400
Bad Request
The server does not understand the syntax of the client's request, such as incorrect request syntax, excessively large request body, or deceptive request paths.
The server cannot or will not process the request due to an apparent client error.
401
Unauthorized
Access to the resource requires authentication, but no authorization was provided or incorrect authorization was provided during the request. For web pages that require login, the server may return this response.
The resource which authentication is required and not yet been provided (or failed).
402
Payment Required
Reserved for future use. Usually used in scenarios where payment is required, such as digital cash or online payments. An example is: Google Developer APIs use status 402 to indicate that the daily request limit has been exceeded.
Reserved for future use. Might be used as part of some form of digital cash or micropayment scheme, but that has not yet happened.
403
Forbidden
The server has received the request but refuses to provide the service. This status usually occurs because the requestor does not have sufficient permissions to access the requested resource.
The request contained valid data and was understood by the server, but the server is refusing action. This may be due to the user not having the necessary permissions for a resource or needing an account of some sort, or attempting a prohibited action.
404
Not Found
The server cannot find the requested web page or resource.
The requested resource could not be found but may be available in the future.
405
Method Not Allowed
The server does not support the current request method. For example: some resources only support GET and POST requests, and if a HEAD request is made, the server will return this status.
A request method is not supported for the requested resource.
