Search and reference HTTP status codes. Find 39 major codes including 200 OK, 404 Not Found, 500 Internal Server Error and more.
The page displays a list of HTTP status codes. You can see the code, name, and description.
Enter a code number or name in the search box to filter results. You can also filter by category (1xx-5xx).
Click on any status code to copy it. Use this for API development or debugging.
Description is also searchable
Showing 39 status codes of 39
HTTP Status Code Reference is a reference tool for searching and browsing the meanings and uses of HTTP response codes returned by web servers to clients. It covers 39 major codes across categories: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error). It's useful for API development, web application debugging, and error investigation.
1xx (Informational) indicates request processing in progress. 2xx (Success) indicates the request was processed successfully. 3xx (Redirection) indicates a redirect to another URL. 4xx (Client Error) indicates a problem with the request. 5xx (Server Error) indicates a server-side problem.
404 Not Found means 'resource not found (potentially temporary)'. 410 Gone means 'resource has been permanently deleted' and signals to crawlers that the resource should be deindexed. For SEO, using 410 for deleted pages is recommended.
301 Moved Permanently indicates a permanent move, and SEO value transfers to the new URL. 302 Found indicates a temporary move, and SEO value stays with the original URL. Use 301 for site migrations or URL structure changes, and 302 for temporary redirects like maintenance.
401 Unauthorized means 'authentication required' - you might be able to access after logging in. 403 Forbidden means 'authenticated but not authorized to access this resource' - you need different credentials or permissions.
500 Internal Server Error indicates an unexpected server-side error. There's limited action users can take, but developers should check server logs and investigate potential causes like code bugs, database connection issues, or memory problems.