Home / Developer Tools / HTTP Status Codes Reference HTTP Status Codes Reference Complete reference of all HTTP response status codes from 1xx to 5xx. Search by code number or description, filter by category, and see common use cases for each status code.
All(61) 1xx Informational(4) 2xx Success(10) 3xx Redirection(7) 4xx Client Error(29) 5xx Server Error(11)
Showing 61 of 61 status codes
100 Continue Informational
The server has received the request headers and the client should proceed to send the request body.
101 Switching Protocols Informational
The server is switching to a different protocol as requested by the client via the Upgrade header.
102 Processing Informational
The server has received and is processing the request, but no response is available yet. Prevents the client from timing out.
103 Early Hints Informational
Used to return some response headers before the final HTTP message, allowing the browser to start preloading resources.
200 OK Success
The request has succeeded. The meaning depends on the HTTP method: GET returns the resource, POST returns the result of the action.
201 Created Success
The request has been fulfilled and a new resource has been created. Typically returned after POST or PUT requests.
202 Accepted Success
The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon.
203 Non-Authoritative Information Success
The returned metadata is not exactly the same as available from the origin server, but collected from a local or third-party copy.
204 No Content Success
The server has successfully fulfilled the request and there is no additional content to return in the response body.
205 Reset Content Success
The server has fulfilled the request and the client should reset the document view (e.g., clear a form).
206 Partial Content Success
The server is delivering only part of the resource due to a Range header sent by the client.
207 Multi-Status Success
Provides status for multiple independent operations in a single response (WebDAV).
208 Already Reported Success
Used inside a DAV: propstat response to avoid enumerating internal members of multiple bindings to the same collection repeatedly.
226 IM Used Success
The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations.
300 Multiple Choices Redirection
The request has more than one possible response. The user or user agent should choose one of them.
301 Moved Permanently Redirection
The resource has been permanently moved to a new URL. All future requests should use the new URL. Search engines transfer link equity.
302 Found Redirection
The resource is temporarily located at a different URL. The client should continue to use the original URL for future requests.
303 See Other Redirection
The response to the request can be found at another URL using a GET method. Often used after POST to redirect to a result page.
304 Not Modified Redirection
The resource has not been modified since the last request. The client can use the cached version, saving bandwidth.
307 Temporary Redirect Redirection
The resource is temporarily at a different URL. Unlike 302, the request method must NOT be changed (POST stays POST).
308 Permanent Redirect Redirection
The resource has permanently moved to a new URL. Like 301, but the HTTP method must NOT be changed.
400 Bad Request Client Error
The server cannot process the request due to malformed syntax, invalid request message framing, or deceptive request routing.
401 Unauthorized Client Error
The request requires user authentication. The client must authenticate itself to get the requested response.
402 Payment Required Client Error
Reserved for future use. Originally intended for digital payment systems, now sometimes used for paywalled content.
403 Forbidden Client Error
The server understood the request but refuses to authorize it. Unlike 401, re-authenticating will not help — the user simply lacks permission.
404 Not Found Client Error
The server cannot find the requested resource. The URL is not recognised. This is the most common error on the web.
405 Method Not Allowed Client Error
The request HTTP method is not supported for the target resource. The response must include an Allow header listing valid methods.
406 Not Acceptable Client Error
The server cannot produce a response matching the Accept headers sent by the client.
407 Proxy Authentication Required Client Error
Similar to 401, but the client must first authenticate with a proxy server.
408 Request Timeout Client Error
The server timed out waiting for the request. The client did not produce a request within the time the server was prepared to wait.
409 Conflict Client Error
The request conflicts with the current state of the server, such as an edit conflict between multiple simultaneous updates.
410 Gone Client Error
The resource is no longer available at the server and no forwarding address is known. Unlike 404, this is a permanent condition.
411 Length Required Client Error
The server refuses the request because the Content-Length header is missing.
412 Precondition Failed Client Error
One or more conditions given in the request header fields evaluated to false when tested on the server.
413 Content Too Large Client Error
The request body is larger than the server is willing or able to process.
414 URI Too Long Client Error
The URI requested by the client is longer than the server is willing to interpret.
415 Unsupported Media Type Client Error
The media format of the requested data is not supported by the server, so the server rejects the request.
416 Range Not Satisfiable Client Error
The range specified in the Range header of the request cannot be fulfilled. The range may be outside the size of the target resource.
417 Expectation Failed Client Error
The expectation given in the Expect header of the request could not be met by the server.
418 I'm a Teapot Client Error
The server refuses the attempt to brew coffee with a teapot. Defined in RFC 2324 (Hyper Text Coffee Pot Control Protocol) as an April Fools' joke.
421 Misdirected Request Client Error
The request was directed at a server that is not able to produce a response. Sent by a server that is not configured for the request URI's scheme and authority combination.
422 Unprocessable Content Client Error
The server understands the content type and syntax of the request, but the contained instructions are semantically invalid.
423 Locked Client Error
The resource that is being accessed is locked (WebDAV).
424 Failed Dependency Client Error
The request failed because it depended on another request that also failed (WebDAV).
425 Too Early Client Error
The server is unwilling to risk processing a request that might be replayed, to avoid potential replay attacks.
426 Upgrade Required Client Error
The server refuses to perform the request using the current protocol but might do so after the client upgrades to a different protocol.
428 Precondition Required Client Error
The server requires the request to be conditional (e.g., include If-Match header) to prevent lost updates.
429 Too Many Requests Client Error
The user has sent too many requests in a given amount of time (rate limiting). Retry-After header may indicate when to retry.
431 Request Header Fields Too Large Client Error
The server refuses the request because the header fields are too large, either individually or in total.
451 Unavailable For Legal Reasons Client Error
The resource is unavailable due to legal demands — such as government censorship or court-ordered takedown. Named after Fahrenheit 451.
500 Internal Server Error Server Error
The server has encountered a situation it does not know how to handle. A generic catch-all server error.
501 Not Implemented Server Error
The request method is not supported by the server and cannot be handled. Servers are required to support GET and HEAD.
502 Bad Gateway Server Error
The server, while acting as a gateway or proxy, received an invalid response from the upstream server.
503 Service Unavailable Server Error
The server is not ready to handle the request. Common causes are maintenance downtime or server overload.
504 Gateway Timeout Server Error
The server, while acting as a gateway or proxy, did not get a response in time from the upstream server.
505 HTTP Version Not Supported Server Error
The HTTP version used in the request is not supported by the server.
506 Variant Also Negotiates Server Error
The server has an internal configuration error: the chosen variant resource is itself configured to engage in content negotiation, creating a circular reference.
507 Insufficient Storage Server Error
The server is unable to store the representation needed to complete the request (WebDAV).
508 Loop Detected Server Error
The server detected an infinite loop while processing the request (WebDAV).
510 Not Extended Server Error
Further extensions to the request are required for the server to fulfill it.
511 Network Authentication Required Server Error
The client needs to authenticate to gain network access. Intended for use by intercepting proxies (captive portals).
Related Tools You Might Like Regex Tester & Debugger — Free Online Tool Test and debug regular expressions with real-time matching, live highlighting, capture groups, and a built-in cheatsheet. Free regex tester with flags support (g, i, m, s)
JWT Decoder Decode and inspect JSON Web Tokens — view header, payload claims, expiration status, and signature
Diff Checker Compare two texts and find differences with unified and side-by-side views
SQL Formatter & Beautifier Format, beautify, and minify SQL queries online. Supports MySQL, PostgreSQL, SQLite, SQL Server, Oracle dialects with configurable indentation and keyword casing
HTML Beautifier & Formatter Beautify, format, and minify HTML with proper indentation and void element handling
XML Formatter & Beautifier Format, beautify, and minify XML with proper indentation, comment handling, and attribute sorting
Frequently Asked Questions What are HTTP status codes? HTTP status codes are three-digit numbers returned by a web server in response to a client request. They indicate whether the request was successful, redirected, resulted in a client error, or caused a server error. Status codes are grouped into five classes: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error).
What does HTTP 404 mean? HTTP 404 (Not Found) means the server cannot find the requested resource. The URL is not recognised. This is the most common error on the web, typically caused by broken links, typos in URLs, or deleted pages.
What is the difference between 401 and 403? HTTP 401 (Unauthorized) means the request requires authentication — the client has not provided valid credentials. HTTP 403 (Forbidden) means the server understood the request but refuses to authorize it — the client is authenticated but lacks the necessary permissions. Re-authenticating will fix a 401 but not a 403.
What does HTTP 500 Internal Server Error mean? HTTP 500 is a generic catch-all error indicating the server encountered an unexpected condition that prevented it from fulfilling the request. Common causes include unhandled exceptions in application code, database connection failures, and misconfigured servers.
When should I use 301 vs 302 redirect? Use 301 (Moved Permanently) when a resource has permanently moved to a new URL — search engines will transfer link equity to the new URL. Use 302 (Found) for temporary redirects where the original URL will be valid again in the future, such as during maintenance. For POST requests, prefer 303 (See Other) or 307 (Temporary Redirect) to control whether the method changes.
What does HTTP 429 Too Many Requests mean? HTTP 429 means the user or client has sent too many requests in a given time period (rate limiting). The server may include a Retry-After header indicating how long to wait before making new requests. Common in APIs, DDoS protection, and login throttling.
