CIDR Toolbelt
Merge, overlap-check, and diff IPv4 CIDR lists for security groups.
OpenFilter the most common HTTP status codes by number or name in one short list.
Enter a code or a word from its name.
Matching codes stay; the rest are hidden.
Each code shows its standard reason phrase.
Empty the box to see all eighteen codes again.
A monitoring alert says 502, a client complains about 409s, and someone asks whether 401 or 403 is the right response for an expired session. Most of the time you need a quick reminder of the name, not the full specification. This reference keeps the everyday codes in one searchable list.
The list covers eighteen codes: 200, 201 and 204 for success; 301, 302 and 304 for redirects and caching; 400, 401, 403, 404, 405, 409, 418 and 429 for client errors; and 500, 502, 503 and 504 for server errors. Each shows its standard reason phrase. Type in the filter box to narrow by number or by words in the name, so typing 'gateway' finds 502 and 504 and typing '40' shows every code that starts with 40.
A few pairs cause most of the confusion. 401 Unauthorized means the request has no valid credentials, while 403 Forbidden means the server knows who you are and still refuses. 502 Bad Gateway means a proxy got an invalid answer from the upstream service, whereas 504 Gateway Timeout means it got no answer in time. 301 tells clients and search engines a move is permanent, while 302 is temporary.
To see the status and headers a real URL returns, try the HTTP headers tool, or send a full request with the API Tester. Other network references are on the network tools hub. The list is filtered in your browser.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
The list is intentionally short and covers eighteen common codes. Less frequent ones such as 206 Partial Content, 307 Temporary Redirect, 422 Unprocessable Content or 451 Unavailable For Legal Reasons are not included, so check the HTTP specification for those.
409 Conflict fits when the request is valid but clashes with the current state, such as creating a user with an email that already exists. 400 Bad Request is better for malformed input that would never succeed.
It began as an April Fools joke about coffee pots and is reserved rather than meant for production use. A few services return it as an easter egg or for blocked bots, so you may still see it in logs.