📡 HTTP Status Codes
Searchable reference of every HTTP status code with plain-language meanings, grouped by class.
📚 A quick everyday reference, not a substitute for the RFC specifications. Descriptions are kept short and practical for debugging.
How to use this tool
Overview
HTTP Status Codes - Complete List & Meanings is a complete, searchable reference of every standard HTTP status code. Codes are grouped by class — 1xx informational, 2xx success, 3xx redirection, 4xx client errors and 5xx server errors — each with a short plain-language meaning written for debugging rather than for the spec. Type any number, name or keyword into the search box and the list filters instantly: try 404, redirect, timeout, auth or cache. Handy for backend debugging, API design reviews, SEO audits and support conversations where "what does 500 mean" needs a fast answer. Everything loads statically and the search runs locally.Frequently asked questions
What is an HTTP status code? +
A three-digit number a server sends with every response to tell the client how the request went. The first digit defines the class: 1xx informational, 2xx success, 3xx redirection, 4xx client error and 5xx server error. The HTTP Status Codes - Complete List & Meanings lists them all with plain-language meanings.
What is the difference between 401 and 403? +
401 Unauthorized means authentication is missing or failed — the client should log in and retry. 403 Forbidden means the server knows who you are but you still do not have permission, so retrying with the same credentials will not help.
Which codes should a REST API return? +
Typical mappings: 200 for reads, 201 for creates with a Location header, 204 for successful deletes, 400 for validation errors, 401 and 403 for auth problems, 404 for unknown resources, 409 for conflicts and 429 for rate limiting.
Is this list searchable? +
Yes — type any code, name or keyword into the search box and the page filters instantly, all locally in your browser.