When a request reaches a server, the status code is one visible part of the response. It can help describe how the request was handled, but the number alone rarely explains the full situation. Last updated: TBD. This explanation is based on the official MDN Web Docs and IETF reference material linked below.
A summary in the response
HTTP status codes communicate the result of a request in a response. MDN groups them into classes such as informational responses, successful responses, redirections, client errors, and server errors. The class narrows the kind of outcome; the specific response still needs context.
Read the surrounding details
A status code is not a complete diagnosis of an application or a user’s experience. The response can also include headers and content, and the request being made matters when interpreting what happened. Avoid inferring more than the response and its documentation support.
Use the official references
MDN’s status-code reference provides a browsable overview: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status. For the HTTP semantics specification, consult IETF RFC 9110, including its status-code section: https://www.rfc-editor.org/rfc/rfc9110.html#name-status-codes. When a label seems ambiguous, follow the specification rather than relying on a shorthand summary.