Look up what 200/301/404/500 and other codes mean
The client should continue its request; the server has received the request headers and has not rejected it
The server is switching protocols as requested by the client
The request has succeeded; the meaning of the response depends on the request method
The request succeeded and the server created a new resource
The server successfully processed the request but is returning no content
The server successfully processed a range request and is returning only part of the resource
The requested resource has been permanently moved to a new location
The requested resource temporarily resides at a different URI
The resource has not changed and the cached version can be used; typically used with conditional caching
The resource temporarily resides at another URI, and the request method must not change when redirecting
The resource has been permanently moved to another URI, and the request method must not change when redirecting
The server could not understand the request due to malformed syntax
Authentication is required and either wasn't provided or the credentials given are invalid
The server understood the request but refuses to authorize it, usually due to insufficient permissions
The server could not find the requested resource — one of the most common error codes
The method specified in the request is not allowed for this resource
The server timed out waiting for the client to send the request
The request conflicts with the current state of the resource, such as an edit conflict
The requested resource has been permanently deleted and no forwarding address is available
A joke status code from the April Fools' RFC 2324: the server refuses to brew coffee because it is a teapot
The server understands the content type, but the data in the request is semantically invalid and cannot be processed
The user sent too many requests in a given time period and has been rate-limited
The server encountered a situation it doesn't know how to handle
The server, acting as a gateway or proxy, received an invalid response from the upstream server
The server is currently unable to handle the request, usually due to overload or maintenance
The server, acting as a gateway or proxy, did not get a timely response from the upstream server
The HTTP Status Code Reference is a searchable cheat sheet covering the 26 most commonly used status codes across the five classes: 1xx informational, 2xx success, 3xx redirection, 4xx client error and 5xx server error. Each entry has the standard name and a one-sentence explanation. It is static reference material, not a diagnostic tool. It does not request any URL, cannot tell you why a particular site returned a 404, and does not include every standard status code.
Say you see a 502 while testing an API. Type 502 and you get "Bad Gateway": a server acting as a gateway or proxy received an invalid response from the upstream server. Type 504 and you get "Gateway Timeout": the gateway did not get a timely response from upstream. Comparing the two helps you tell whether upstream answered badly or did not answer in time. Searching 30 matches 301, 302, 304, 307 and 308, so you can see that 301 is a permanent move, 302 is temporary, and 304 tells the browser to use its cached copy.
401 means authentication is required and you either did not provide credentials or they were invalid. 403 means the server understood the request, you may even be logged in, but it still refuses, usually because of insufficient permissions. In short, 401 is not logged in or invalid login, and 403 is logged in but not allowed.
A 301 says the resource has moved permanently, and search engines generally transfer the old address's standing to the new one over time. A 302 says the move is temporary, and the old address is usually kept. The exact effect depends on how each search engine treats them. This page only lists the standard meaning of the two codes.
500 means the server itself hit a situation it could not handle. 502 means a gateway or proxy got an invalid response from upstream. 503 means the server is temporarily unable to handle the request, often due to overload or maintenance. 504 means the gateway did not get a response from upstream in time. The last three typically appear in setups with a reverse proxy or load balancer.
Because the page currently includes only 26 common codes, and anything outside them cannot be found. For a complete list, check RFC 9110 or the IANA HTTP status code registry.
The data is built into the page code and the filtering happens in your browser. The keywords you type are not sent to a server or stored.