HTTP Response Status Codes Explained

What Does an HTTP Response Status Code Mean?

An HTTP response status code is a three-digit number a server sends after receiving an HTTP request. The response status tells a browser, app, search crawler, or API client whether the request succeeded, requires another action, or encountered a problem.

The first digit identifies the broad result category. The remaining digits identify a more specific result. A response may also include headers and a body containing a page, data, or a website-specific message.

The HTTP status response code does not always describe everything the visitor sees. A server might return a normal page with a 200 code while displaying an error message inside the page. It might also return a redirect code that correctly sends the browser to a different location.

What Do the HTTP Status Code Categories Mean?

HTTP response status codes are divided into five classes:

• 1xx — Informational: The server received the request and the exchange is continuing. Visitors rarely see these codes directly.
• 2xx — Successful: The server received, understood, and accepted the request. A 2xx response does not guarantee that every part of the displayed content is correct.
• 3xx — Redirection: The client may need to use another location or rely on cached content. Redirects are often intentional and are not automatically errors.
• 4xx — Client-side request issue: The server could not fulfill the request because of the requested resource, credentials, permissions, request format, or request rate.
• 5xx — Server-side issue: The server or an upstream system failed while handling an otherwise valid-looking request.

These categories summarize the general meaning of HTTP status response codes. The exact code, response headers, request method, and application behavior provide the necessary context.

What Do Common HTTP Response Status Codes Mean?

• 200 OK: The request succeeded. The response normally contains the requested representation or result.
• 301 Moved Permanently: The resource has a new permanent location. Browsers and search systems may remember the redirect.
• 302 Found: The resource is temporarily available at another location. The client generally continues using the original address for later requests.
• 400 Bad Request: The server could not process the request because it appeared malformed or invalid.
• 401 Unauthorized: Authentication is required or the supplied authentication was not accepted. Despite its name, this code is primarily about authentication.
• 403 Forbidden: The server understood the request but refuses to authorize it. Signing in again may not help if the account lacks permission.
• 404 Not Found: The server did not find the requested resource. The address may be wrong, or the resource may have moved or been removed.
• 429 Too Many Requests: The client sent more requests than the server currently allows. The response may indicate how long to wait before retrying.
• 500 Internal Server Error: The server encountered an unexpected condition and could not complete the request.
• 502 Bad Gateway: A server acting as a gateway or proxy received an invalid response from another server.
• 503 Service Unavailable: The server is temporarily unable to handle the request, commonly because of maintenance, overload, or a dependent service.

How Can You Check the HTTP Response Status Code?

Use one of these methods to inspect the response HTTP status code:

1. Browser developer tools: Open the browser menu, select Developer Tools, and choose the Network panel. Reload the page, select the relevant request, and read the Status column or response details. Check the document request as well as failed image, script, and API requests.
2. Command-line utility: Use a tool such as curl with its option for displaying response headers. The first response line shows the protocol and code. If redirects are followed automatically, inspect each response because the final code can hide an earlier 301 or 302.
3. API client: Send the request in an API testing application and inspect the displayed status, headers, and body. Confirm that the request method, authentication, parameters, and body match what the server expects.

A browser page can trigger many requests, each with its own response status code. Identify the request that matters before interpreting the result.

What Should You Do About an HTTP Error Status?

For a visitor, start with simple checks:

1. Confirm that the address was entered correctly and remove accidental extra characters.
2. Reload once. Avoid rapid repeated attempts when the response status is 429.
3. For 401, sign in again or confirm that the correct account is being used. For 403, check whether the account has permission.
4. For 404, return to the site navigation and locate the page again.
5. For 500, 502, or 503, wait briefly and retry. If only one network or browser is affected, test another connection or clear relevant cached data.

Site administrators should reproduce the request, record the method and time, and inspect server and application logs. Check redirect rules for 3xx codes, authentication and authorization rules for 401 or 403, routing for 404, rate limits for 429, and application or upstream-service health for 5xx responses.

Do not treat every non-2xx response as a failure. A 301 can be the intended permanent redirect, a 304 can confirm that cached content remains valid, and some APIs use specific non-2xx codes to describe expected conditions.

What Are the Most Common Questions About Response Status Codes?

Is a redirect an HTTP error? No. A 3xx response usually tells the client to take another step, and that behavior may be intentional.

What is the difference between 4xx and 5xx? A 4xx code points to the request, credentials, permissions, resource, or request rate. A 5xx code means the server or an upstream system failed while processing the request.

Why do I see an error message with a 200 response? The website may have returned an error message inside a technically successful HTTP response. The visible message and the HTTP response status code are separate signals.

Can the same page produce several response status codes? Yes. The page document, images, scripts, fonts, and API calls are separate requests and can return different codes.

Which HTTP status response code should I trust? Inspect the code for the specific request you are diagnosing, then read its headers and body. A final browser page alone may not reveal earlier redirects or failed background requests.