2xx — Success: the request was received, understood and accepted.
200 OK
The request succeeded and the response body contains the result.
When you see it: The normal answer to a successful GET, PUT, POST or HEAD.
Look up any HTTP status code with its official name, RFC reference and a plain-English explanation.
No status codes match your search. Try a number like 404, or a word like "redirect".
2xx — Success: the request was received, understood and accepted.
The request succeeded and the response body contains the result.
When you see it: The normal answer to a successful GET, PUT, POST or HEAD.
Type a number like 404 or a word like redirect, timeout
or teapot and the matching HTTP status codes appear instantly. Pick one to see
what it means in plain English, which class it belongs to (1xx informational, 2xx success,
3xx redirection, 4xx client error, 5xx server error), the RFC that defines it and when you
typically run into it while debugging an API or a website. The list covers every registered
IANA status code plus the unofficial ones you actually meet in the wild, such as nginx's 499
and Cloudflare's 520–527. The whole reference is bundled into the page, so lookups work
offline and nothing you search for is sent anywhere.
404 Not Found means the server could not find the requested resource. The URL may be misspelled, the page may have been deleted without a redirect, or the API route may not exist. It is defined in RFC 9110 §15.5.5, and servers also use it to hide resources they do not want to acknowledge exist.
500 is a generic server-side failure: the request looked valid but the server hit an unexpected condition, usually an unhandled exception, a bad deploy or a database error. Nothing the client changes will fix it — the answer is in the server logs. If a proxy sits in front of the app, check 502 and 504 as well.
301 Moved Permanently tells clients and search engines the resource has a new permanent URL, and browsers cache it aggressively. 302 Found is temporary, so the original URL stays authoritative. If the HTTP method and body must be preserved while redirecting, use 308 (permanent) or 307 (temporary) instead.