A little help goes a long way. Find a tool/

Developer

HTTP Status Code Lookup

Free HTTP status code lookup: search 60+ status codes by number or keyword and get the official name, the class it belongs to, and a plain-English explanation of when it happens.

YOUR WORKSPACEFree to use. No sign-up.
—
Enter a three-digit code or a search term like “not found”.

Deep dive guides

A LITTLE CONTEXT · 4 MIN READHTTP Status Codes Explained: What 200, 301, 404 and 500 Really Mean

How http status code lookup works

Every HTTP response starts with a three-digit status code that tells the client how the request went. The first digit groups codes into five classes: 1xx informational, 2xx success, 3xx redirection, 4xx client error, and 5xx server error. This tool covers all of the IANA-registered codes you will actually meet — plus a few widely used non-standard ones like nginx's 499 — each with its official name and a plain-English explanation of when it appears.

You can work three ways. Enter a full three-digit code like 404 for a detailed answer: the name, the class with its range, and a description of the usual cause. Enter a single class digit like 4 to list every client-error code. Or type a keyword like "redirect", "timeout", or "teapot" and the tool ranks matching codes — exact name matches first, then name mentions, then descriptions.

Codes that are not part of the official IANA registry are flagged as non-standard, so you never mistake a server-specific convention like 499 (Client Closed Request) for something a browser or HTTP library is guaranteed to understand. A reference table of the five classes stays at the bottom of the page for quick orientation.

Frequently asked questions

What is the difference between 401 and 403?
401 Unauthorized means you are not authenticated — log in or send valid credentials and the request may succeed. 403 Forbidden means the server knows who you are and still refuses: re-authenticating will not help. A good rule of thumb: 401 is "who are you?", 403 is "I know who you are, and no".
Which redirect should I use — 301, 302, 307 or 308?
301 is the permanent redirect and 302 the temporary one, but both may be turned into GET requests by clients. 307 and 308 are the modern versions that preserve the method and body: use 308 for a permanent move that must stay a POST, and 307 for a temporary one.
Does a 4xx or 5xx error mean the request failed?
4xx means the client side caused the problem — bad syntax (400), missing authentication (401), or a missing resource (404) — so fixing the request helps. 5xx means the server failed even though the request was valid (500, 502, 503, 504), so retrying or fixing the server is the answer.
Are all the codes in the tool official?
Almost. 499 (Client Closed Request) and 599 (Network Connect Timeout) are widely used but server-specific rather than IANA-registered, and the tool flags them as non-standard. Everything else, including the WebDAV codes and the 418 teapot, comes from an IETF RFC.
Why do I see 304 instead of a full response?
304 Not Modified is a success for caching: your browser asked "has this changed since my copy?" and the server answered no, so the cached copy is reused and no body is downloaded. It is how conditional GET requests with If-Modified-Since or ETag headers save bandwidth.