Web error codes are HTTP status codes: three-digit numbers that tell a browser or other client how a server handled a request. The first digit identifies one of five classes: 1xx means processing continues, 2xx means success, 3xx means redirection, 4xx means the request cannot be fulfilled as sent, and 5xx means a server could not complete an apparently valid request.
What do web error codes mean?
An HTTP status code is part of the response exchanged between a client—such as a browser—and a server. The code is a protocol signal, not a complete diagnosis of what happened to a particular visitor. A website can customize the page it displays without changing the status code’s meaning.
![Computer Networking Bible: [3 in 1] The Complete Crash Course to Effectively Design, Implement and Manage Networks. Including Sections on Security, Performance and Scalability](https://m.media-amazon.com/images/I/41H4YJnxKgL._SL160_.jpg)
As an Amazon Associate I earn from qualifying purchases.
Under RFC 9110, the HTTP standard published by the IETF in June 2022, status codes are three-digit integers from 100 through 599. The first digit identifies the response class; the final two digits do not define a general category.
| Class | Meaning | What it generally signals |
|---|---|---|
| 1xx | Informational | The request was received and processing continues. |
| 2xx | Successful | The request was successfully received, understood, and accepted. |
| 3xx | Redirection | Further action is needed to complete the request, often following a redirect. |
| 4xx | Client error | The request cannot be fulfilled as sent, or the server considers it to have a client-side problem. |
| 5xx | Server error | The server failed to fulfill an apparently valid request. |
“Client error” does not necessarily mean a visitor made a mistake. Authentication, permissions, a missing or changed resource, and application behavior can all lead to a 4xx response.
#1 Best Overall
Which common web error codes should you recognize?
| Code | Plain-language meaning | What it tells you—and what it does not | Practical next step |
|---|---|---|---|
| 400 Bad Request | The server cannot or will not process the request because it sees a request problem. | It may involve malformed syntax or invalid message framing; the code alone does not identify the exact cause. | Check the address or form data and try again. If it persists, report the issue to the site. |
| 401 Unauthorized | Valid authentication credentials are missing. | Despite its name, 401 concerns authentication, not necessarily permission. RFC 9110 requires a 401 response to include a WWW-Authenticate challenge. |
Sign in or provide the requested credentials. |
| 403 Forbidden | The server understood the request but refuses to fulfill it. | The response does not, by itself, explain the site’s access policy or whether sign-in would help. | Check whether you are signed into the right account or have access; contact the site if access should be available. |
| 404 Not Found | The origin server did not find a current representation for the requested resource, or is unwilling to disclose that one exists. | A 404 alone does not say whether the address is mistyped, the page moved, or the resource is unavailable for another reason. | Check the URL, then navigate from the site’s home page or search for the content. |
| 500 Internal Server Error | The server encountered an unexpected condition that prevented it from completing the request. | It identifies a server-side failure, not its underlying cause. | A visitor can retry later or notify the site. Site owners should inspect application and server logs. |
| 501 Not Implemented | The server does not support functionality required to fulfill the request. | This differs from a temporary overload: the required functionality is not supported by that server. | Visitors can report it to the site. Site owners should check whether the requested method or feature is supported. |
| 502 Bad Gateway | A gateway or proxy received an invalid response from an upstream server. | The failure is between servers or in the upstream response, rather than necessarily in the visitor’s request. | Visitors can try again later or report the problem. Site owners should check gateway and upstream-service logs. |
| 503 Service Unavailable | The server is currently unable to handle the request, typically because of temporary overload or scheduled maintenance. | The condition is expected to ease after some delay, but the code does not guarantee when service will return. A response may include Retry-After to suggest a wait. |
Wait for the suggested interval if one is provided, then retry. Site owners should check capacity, maintenance, and service health. |
| 504 Gateway Timeout | A gateway or proxy did not receive a timely response from an upstream server needed to complete the request. | It signals a delayed upstream response, not an invalid one. | Visitors can retry later or contact the site. Site owners should investigate upstream response times and gateway timeouts. |
What does a 404 error mean?
A 404 means the server did not find a current representation for the requested resource, or is unwilling to reveal that it exists. It does not establish why. The page may have moved, the address may be wrong, or the site may be using the response to avoid disclosing a resource’s existence.
Start by checking the address for typing errors. If it looks right, use the site’s navigation or search to find the content. A custom 404 page may offer those options, but its design does not alter the status code’s protocol meaning.
What is the difference between a 502 and a 504 error?
Both codes involve a gateway or proxy communicating with an upstream server, but they describe different failures. A 502 means the gateway received an invalid upstream response. A 504 means it did not receive a timely response. Neither code, by itself, identifies the specific server, configuration, or application fault.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Is a 500 error my fault or the website’s?
A 500 means the server encountered an unexpected condition that prevented it from fulfilling the request. It is a server-side response, but the code alone cannot identify the cause or prove whether a particular request triggered it. A visitor generally cannot diagnose or repair the website’s server from the code alone; retrying later or reporting the error is a reasonable step.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How can you verify what a status code means?
For standardized definitions, consult RFC 9110, the IETF’s HTTP semantics specification. The IANA HTTP Status Code Registry lists assignments and links to their defining standards. MDN’s HTTP response status codes reference provides a readable overview of commonly encountered codes.
Not every code shown by a particular product or server is universally standardized. Some software uses custom responses or additional substatus details; a code missing from a general reference may be specific to that software. Check the relevant product documentation when the exact implementation matters.
Quick Recap
Best Value
- Used Book in Good Condition
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
