Skip to main content
JoliTools

HTTP Status Codes

Look up HTTP status codes and understand what each response means.

39 of 39 codes

About this tool

HTTP status codes are numeric responses sent by a web server to describe the result of a request. They help browsers, applications, developers, and website owners understand whether a request succeeded, needs further action, or encountered a problem. The HTTP Status Codes reference explains common response codes in straightforward language. Each code belongs to a category that indicates the general type of response. Knowing these codes makes it easier to investigate website errors, understand redirects, and troubleshoot communication between applications and servers.

Imagine someone opens a website page that no longer exists. The server may respond with status code 404, which means Not Found. If a page has moved permanently, the server may instead return 301, indicating a permanent redirect. A response of 200 means the request was successful, while 500 indicates an internal server error. These examples show why status codes are useful when checking a website or diagnosing a problem. The code provides a starting point for understanding what happened, although additional information may be needed to identify the exact cause.

How to use the http status codes

  1. 1Find the HTTP status code you want to understand.
  2. 2Read its official name and general meaning.
  3. 3Check the category to understand the type of response.
  4. 4Use the explanation to investigate your website or application behavior.

Good to know

HTTP response codes are grouped into five main classes. Codes from 100 to 199 provide informational responses. Codes from 200 to 299 indicate successful requests. Codes from 300 to 399 relate to redirection. Codes from 400 to 499 describe client side errors, and codes from 500 to 599 describe server side errors. A 404 error usually means the requested resource could not be found, while a 403 response means access is forbidden. A 401 response generally indicates that authentication is required. Do not assume that every error is caused by the same problem simply because the status code matches. Server configuration, permissions, authentication, application logic, and network conditions can all affect the result. Status codes also do not reveal every detail about a server failure. Check the response body, server logs, and application settings when investigating a specific issue. This reference is intended as an educational guide, not a replacement for testing or server diagnostics.

Frequently asked questions

HTTP status codes are numeric responses that explain what happened when a browser or application made a request to a server.

More free tools you might find useful.

Part of Developer Tools on JoliTools, free tools, no sign-up.