HTTP Status Code Reference Tool
Search or browse a full reference of HTTP response status codes, grouped by category with a plain-English explanation for each. Type a code number or a keyword to filter instantly.
How to Use This Tool
- Start typing a status code number (like "404") or a keyword (like "redirect" or "not found") in the search box.
- The list filters live to show only matching codes, grouped by category (Informational, Success, Redirection, Client Error, Server Error).
- Clear the search box to browse the full reference of all supported codes.
- Use it as a quick lookup while debugging APIs, reading server logs, or writing documentation.
Why Use This Tool?
Is this list accurate and complete?
This reference covers over 60 real, standardized HTTP status codes defined across RFC 7231, RFC 6585, RFC 4918 (WebDAV) and related specifications — spanning all five official categories from 1xx Informational through 5xx Server Error. It includes the codes developers encounter daily (200, 301, 404, 429, 500, 503) as well as less common but still standard codes used in specialized contexts like WebDAV and content negotiation.
Is my search query sent anywhere?
No. The entire status code list is bundled directly into this page's JavaScript and filtered locally in your browser as you type. Nothing is sent to a server, logged, or tracked — this works identically offline once the page has loaded.
Why do status codes matter for developers?
HTTP status codes are the primary signal a server uses to tell a client (browser, mobile app, or another server) what happened with a request. Correctly returning 404 instead of 200 for a missing resource, or 429 instead of 500 when rate-limiting, directly affects how clients, caches, monitoring tools and search engine crawlers behave. Misusing status codes is a common source of subtle bugs in APIs and SEO issues on websites.
What's the difference between the five categories?
1xx codes are informational and rarely seen directly by end users. 2xx codes mean success. 3xx codes indicate the client must take further action, usually following a redirect. 4xx codes mean the client made a mistake in the request (like requesting a page that doesn't exist). 5xx codes mean the server itself failed to fulfill an otherwise valid request. Recognizing the category from the first digit alone is often enough to quickly triage an issue.