wtoolsy.com
Network, DNS, IP
Developer tools
SEO and page analysis
Finance and calculators
Universal
Articles
All articles

HTTP Codes List

HTTP status codes are three-digit responses sent by a server in response to a client request, most often from a web browser. They inform whether the request was successful, requires redirection, or if a user-side or server-side error occurred.

Each HTTP code belongs to one of five categories: informational (1xx), success (2xx), redirection (3xx), client errors (4xx), and server errors (5xx). Thanks to these codes, browsers, search engine robots, and web applications can correctly interpret server responses and react accordingly.

Knowledge of HTTP codes is particularly important for developers, server administrators, and SEO specialists analyzing website performance. Below you will find a complete list of the most important HTTP status codes along with a description of their meaning and application.

1xx

Informational

CodeNameDescription
100ContinueServer received request headers, client can continue sending content.
101Switching ProtocolsServer is switching protocols according to the client's request (e.g., WebSocket).
103Early HintsInterim response with headers before the server sends the actual response.
2xx

Success

CodeNameDescription
200OKThe request was successful.
201CreatedResource successfully created.
202AcceptedRequest accepted but not yet processed.
204No ContentSuccess, but response contains no content.
206Partial ContentServer returns only part of the resource (e.g., for file downloads).
3xx

Redirects

CodeNameDescription
301Moved PermanentlyResource permanently moved to a new address.
302FoundResource temporarily available at a different address.
303See OtherResponse to the request is available under a different URI (GET).
304Not ModifiedResource has not changed since the last request — use cache.
307Temporary RedirectTemporary redirect preserving the HTTP method.
308Permanent RedirectPermanent redirect preserving the HTTP method.
4xx

Client Errors

CodeNameDescription
400Bad RequestServer cannot process the request due to a client-side error.
401UnauthorizedAuthentication required.
403ForbiddenNo permission for the resource.
404Not FoundResource does not exist.
405Method Not AllowedHTTP method not allowed for this resource.
408Request TimeoutClient timed out while sending the request.
409ConflictConflict with the current state of the resource.
410GoneResource permanently removed.
413Content Too LargeRequest content exceeds server limit.
414URI Too LongURL address is too long.
415Unsupported Media TypeServer does not support the data format.
418I'm a teapotJoke: the server refuses to brew coffee because it is a teapot
422Unprocessable EntityRequest is syntactically correct but impossible to process.
429Too Many RequestsRequest limit exceeded (rate limiting).
444No ResponseThe server decided not to respond to the client.
499Client Closed RequestThe client (e.g., browser) closed the connection before the server could send a response
5xx

Server Errors

CodeNameDescription
500Internal Server ErrorGeneral server error.
501Not ImplementedServer does not support the requested functionality.
502Bad GatewayProxy server received an invalid response.
503Service UnavailableServer temporarily unavailable.
504Gateway TimeoutProxy server received an invalid response.
505HTTP Version Not SupportedThe server does not support the HTTP protocol version used in the request.

Most common HTTP errors

Some HTTP status codes appear much more often than others and are well known to internet users. They most often concern page availability issues, server configuration errors, or invalid URLs.

404 Not Found

A 404 error means the server is working correctly but cannot find the resource at the specified URL. It most often appears when a page has been deleted, the address is wrong, or a link leads to a non-existent subpage.

500 Internal Server Error

Code 500 signifies a general server error. It occurs when an application or server configuration encounters an unexpected problem and is unable to handle the request properly.

502 Bad Gateway

A 502 error appears when a server acting as a gateway or proxy receives an invalid response from an upstream server. It often occurs in architectures with load balancers or reverse proxies.

503 Service Unavailable

Code 503 means the server is temporarily unavailable. This is most often due to server overload, maintenance work, or resource limits.

Related tools

If you are analyzing server performance or diagnosing website issues, the following tools may be helpful.