iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Web error codes are usually HTTP status codes: three-digit signals in a web response that indicate whether a request is continuing, succeeded, needs redirection, could not be fulfilled as sent, or failed on the server. The first digit identifies the class: 1xx, 2xx, 3xx, 4xx, or 5xx. The code is separate from the page’s wording or design, so a site can show a custom error page without changing the status code’s meaning.
What do web error codes mean?
When a browser requests a page or other resource, the server returns an HTTP response. Its status code is a three-digit integer from 100 through 599. The first digit identifies the response class; the last two digits identify a more specific status within that class, not a separate general category. RFC 9110 defines the five classes:
- 1xx — Informational: The request was received and processing is continuing.
- 2xx — Successful: The request was successfully received, understood, and accepted.
- 3xx — Redirection: Further action is needed to complete the request, commonly following a redirect.
- 4xx — Client error: The request appears to have a problem or cannot be fulfilled as sent.
- 5xx — Server error: The server failed to fulfill a request that appears valid.
These are protocol signals, not full diagnoses. A 4xx response does not prove that a visitor personally caused the problem: the URL, sign-in state, permissions, or application behavior may be involved. A 5xx response points to the server side of the exchange, but the code alone does not reveal the underlying fault.
Recommended Free Tools
Common HTTP error codes and what to do
The practical meaning of a code depends on what it says about the request and where the failure occurred. The suggestions below are starting points, not guarantees that a particular action will resolve the issue.
#1 Best Overall
| 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 considers it malformed or otherwise a client error. | The request was rejected; the code alone does not identify which part was invalid. | Check the address or form data and try again. If it persists, report the page and action to the site. |
| 401 Unauthorized | Valid authentication credentials are absent, so the request was not applied. | Despite its name, this is an authentication response, not simply a statement that access is forbidden. RFC 9110 requires a 401 response to include a WWW-Authenticate challenge. |
Sign in or check whether your session has expired. If you are already signed in, contact the site. |
| 403 Forbidden | The server understood the request but refuses to fulfill it. | The request was understood, but access is refused; the code does not say whether the cause is account permissions, site policy, or another restriction. | Check that you are using the intended account and have permission. Ask the site owner 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 does not establish why the resource was not found; it may not reveal whether the item was removed, moved, or intentionally hidden. | Check the URL for a typo, navigate from the site’s current pages, or contact the site if you expected the resource to exist. |
| 500 Internal Server Error | The server encountered an unexpected condition that prevented it from fulfilling the request. | It signals a server-side failure but does not identify its cause. | As a visitor, you can try again later or tell the site. If you operate the site, investigate server and application logs. |
| 501 Not Implemented | The server does not support functionality required to fulfill the request. | This is a missing or unsupported server capability, not necessarily a temporary outage. | Contact the site or service provider; a visitor generally cannot add the missing server functionality. |
| 502 Bad Gateway | A server acting as a gateway or proxy received an invalid response from an inbound server. | The failure involves communication between servers, but the code does not identify which component caused it. | A visitor can retry later. A site operator should investigate the 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 be temporary, but the code does not guarantee when service will return. The response may include Retry-After to suggest how long to wait. |
Wait for the indicated interval if one is provided, then retry. Site operators should check service health and load. |
| 504 Gateway Timeout | A gateway or proxy did not receive a timely response from an upstream server needed to complete the request. | It indicates an upstream response was late or absent, not that the upstream server necessarily returned invalid data. | A visitor can try again later. A site operator should inspect gateway timeouts and upstream response times. |
What does a 404 error mean?
A 404 means the origin server did not find a current representation for the requested resource, or is unwilling to disclose that one exists. It does not, by itself, explain why. The resource might have been moved or removed, the address could be mistyped, or the server might be withholding information about it. Check the URL and look for the resource through the site’s current navigation; if you own the site, check the requested path and the application or server handling it.
What is the difference between 4xx and 5xx errors?
A 4xx status describes a request that cannot be fulfilled as sent. A 5xx status describes a server’s failure to complete an apparently valid request. That distinction helps identify where to begin, but it does not assign personal blame: a visitor may encounter a 4xx because of authentication or access rules, while a site owner may need to investigate application behavior.
Visitors generally cannot diagnose or repair a website’s server from a 5xx code alone. If a 5xx error keeps happening on a site you operate, review server and upstream service logs, then use the specific code to narrow the investigation.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsWhat is the difference between a 502 and a 504 error?
Both involve a gateway or proxy communicating with an upstream server, but they describe different failures. A 502 Bad Gateway means the gateway received an invalid response. A 504 Gateway Timeout means it did not receive a response in time. A 503 Service Unavailable instead says the server is currently unable to handle the request, often because of temporary overload or maintenance; RFC 9110 says the response may include Retry-After.
Is a 500 error my fault or the website’s?
A 500 Internal Server Error means the server encountered an unexpected condition that prevented it from fulfilling the request. It points to a server-side failure, not a routine indication that you entered the wrong address or lack permission. The code does not reveal the specific cause. As a visitor, you can retry later or notify the site; the site operator should investigate server and application logs.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Does the error page change what the code means?
No. The status code is part of the HTTP response; the page or other content sent with it is the response representation. A site can replace a generic message with a branded explanation, but that presentation does not alter the standardized meaning of the code.
Rank #4
Where can you verify an HTTP status code?
For authoritative definitions, consult RFC 9110, the IETF specification for HTTP semantics. The IANA HTTP Status Code Registry lists assigned codes and links to their defining standards. MDN’s HTTP response status codes reference offers a readable guide to common responses and notes that codes absent from its list may be non-standard or specific to server software. A code shown by a particular product is not automatically a universally standardized status; some software also reports product-specific substatus information.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
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.
