HTTP Status Codes Reference

Search and browse all HTTP status codes with descriptions, use cases, and common troubleshooting tips.

Loading...
1. Type a status code number (such as 404 or 502) or keyword (such as "redirect" or "unauthorized") into the search bar. 2. Browse results filtered by category - 1xx, 2xx, 3xx, 4xx, or 5xx - using the category tabs. 3. Click on any status code card to expand its full description, common causes, and troubleshooting tips. 4. Review the real-world examples to understand when and why each code occurs in practice. 5. Use the copy button to copy the status code name and description for your documentation or bug reports.

About This Tool

The HTTP Status Codes Reference is a comprehensive, searchable guide to every HTTP response status code. Browse by category (1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error, 5xx Server Error) or search for any specific code to see its official name, detailed description, common causes, and troubleshooting steps.

Understanding HTTP status codes is essential for web developers, API designers, and system administrators. Whether you are debugging a mysterious 502 Bad Gateway, implementing proper 301 redirects for SEO, or designing RESTful API responses, this reference provides clear, practical explanations for every code.

Each status code entry includes real-world examples of when it occurs, the correct way to handle it programmatically, and common mistakes to avoid. The tool also highlights deprecated or non-standard codes and notes which codes are cacheable by default.

Frequently Asked Questions

1xx codes are informational, 2xx indicate success (200 OK is the most common), 3xx are redirections, 4xx indicate client errors (like 404 Not Found), and 5xx indicate server errors (like 500 Internal Server Error).
A 301 is a permanent redirect - search engines transfer ranking signals to the new URL. A 302 is a temporary redirect - search engines keep the original URL indexed. Use 301 for permanent URL changes and 302 for temporary situations.
A 403 error means the server understood the request but refuses to authorize it. Common causes include insufficient file permissions, IP-based access restrictions, missing authentication, or web application firewall rules blocking the request.
A 401 Unauthorized means the client needs to authenticate (provide credentials). A 403 Forbidden means the client is authenticated but does not have permission to access the resource. In practice, some servers use 404 instead of 403 to hide the existence of resources.

Related Tools

URL Parser

Break down URLs into protocol, host, port, path, query parameters, and hash components.

Developer Tools

Meta Tag Generator

Generate HTML meta tags for SEO, Open Graph, and Twitter Cards with a live preview of search and social results.

Web and SEO Tools

MIME Types Lookup

Search MIME types by file extension or content type with descriptions, categories, and common uses.

Web and SEO Tools

JSON Formatter and Validator

Format, validate, and beautify JSON data with syntax highlighting, tree view, and error detection.

Developer Tools

JWT Decoder

Decode JSON Web Tokens to inspect header, payload, and signature without needing the secret key.

Developer Tools

2xx Success (10)

3xx Redirection (8)

4xx Client Error (29)

5xx Server Error (11)