What are HTTP status codes?
HTTP status codes are three-digit numbers a server returns with every response to tell the client what happened to its request. A code of 200 means the request succeeded, 404 means the page was not found, and 500 means the server hit an error. This reference lists every standard status code defined by the Internet Engineering Task Force, grouped by class, with a plain-English explanation of what each one means and a link to the specification that defines it. You can search by number, by name, or by a word from the description.
Status codes fall into five classes identified by their first digit. The 1xx class is informational and signals that the request was received and processing continues. The 2xx class means success, so the request was received, understood, and accepted. The 3xx class is redirection, telling the client the resource lives somewhere else or has not changed. The 4xx class is a client error, meaning the request was malformed or not allowed. The 5xx class is a server error, where the request was valid but the server failed to fulfil it. Knowing the class alone tells you whether to fix your request or look at the server.
Developers reach for a status code reference constantly. Front-end engineers debug why an API call returns 401 instead of 200, back-end developers decide whether to send 400 or 422 for a validation failure, and SEO specialists check that a moved page returns 301 rather than 302 so search engines transfer its ranking. This tool runs entirely in your browser, so searches are instant and nothing is sent to a server. It works offline once loaded and is free with no account required, making it a fast tab to keep open while building or debugging any web service.
How to use the HTTP Status Codes reference?
Search by code or name
Type a number like 404, a phrase like "not found", or a keyword like "redirect" into the search box to filter the list instantly.
Filter by class
Narrow the list to one category (1xx, 2xx, 3xx, 4xx, or 5xx) to browse only informational, success, redirect, client-error, or server-error codes.
Read the meaning
Each row shows the reason phrase, a clear description of when the code is used, and the RFC that defines it.
Copy the code or phrase
Copy a status code and its reason phrase with one click to paste into documentation, tests, or API responses.
Key Features
Complete IANA registry
Covers every standard code from 100 to 511, including WebDAV and rate-limiting codes, grouped by their class.
Instant search
Match by number, reason phrase, or description, so 404, "not found", and "missing page" all find the right entry.
Class filters
Jump straight to 1xx, 2xx, 3xx, 4xx, or 5xx codes to focus on redirects, client errors, or server errors.
Spec citations
Every code names the RFC that defines it, so you can confirm behaviour against the primary source.
Frequently Asked Questions
Related Tools
Basic Auth Generator
Turn a username and password into an HTTP Basic Authentication header, base64 token, curl commands and URL form, and decode existing Basic auth tokens back.
Domain Search
Check one name across dozens of TLDs at once. RDAP first, WHOIS fallback, and a verdict of available, taken or unknown, never a guess
WHOIS Checker
Look up the registry record for any domain: registrar, registration and expiry dates, status codes, nameservers, DNSSEC and the raw WHOIS record.
JSON Validator
Validate JSON against RFC 8259 and get the exact line, column, and character of the first syntax error, plus duplicate-key detection and structure stats. Client-side, no signup.
Comments
0 comments
No comments yet. Be the first to share your thoughts!