Skip to content
100% local

HTTP status code lookup

Find HTTP status codes in text or a log and see the name, class and meaning of each.

Input
Output

HTTP status code lookup

Paste anything containing an HTTP status code - a single code like 404, an access log line, a curl -i response, or a chunk of server output - and this tool identifies every recognized code and shows its official name, its class (1xx through 5xx) and a short, plain-language note on when it shows up. It covers the full range from informational 1xx codes through success, redirection, client-error and server-error codes, so a stray 429 or 507 doesn't send you searching a spec.

"Single code" mode reads the first recognized code out of whatever you paste - the quickest path when you just want to know what one code means. "Search in log" mode scans the whole input instead and counts every occurrence, which suits a real access log full of mixed traffic. Turn on "Sort by occurrences" to put the most frequent codes first and spot which error dominates a noisy log. "Errors only" narrows the result to 4xx and 5xx codes, filtering out the 200s and 304s that make up the bulk of normal traffic.

Choose the output format to match what you are doing with the result: "List" prints one readable block per code with its name, class and explanation, good for reading through on screen. "Table" lines the same information up in columns - code, name, class, and in log mode a count - ready to paste into a bug report or a spreadsheet. A three-digit number that isn't a registered status code, like a byte count sitting next to a real one in a log line, is left out of the result rather than shown as an empty entry.

Everything runs locally in your browser. The log lines or responses you paste can contain internal hostnames, request paths or other details you'd rather not send anywhere, and none of it leaves your device - the lookup runs against a small built-in table of status codes. Copy the result, download it as a .txt file, or send it straight into another tool to keep working.

FAQ

What is the difference between "Single code" and "Search in log" mode?
"Single code" reads only the first recognized status code in the input - useful for a quick lookup of one code. "Search in log" scans the whole input and reports every occurrence, with a count for each, which suits a real log file with many requests.
How does it avoid matching random three-digit numbers?
Only numbers that are registered HTTP status codes (100-599, drawn from the official IANA registry) are shown. A byte count or a port number that happens to be three digits, or is embedded inside a longer number, is not treated as a status code.
Can I see only the error codes in a log?
Yes. Turn on "Errors only" to keep just the 4xx and 5xx entries and drop everything in the 1xx-3xx range.
Does "Sort by occurrences" work in single-code mode?
It has no effect there, since single-code mode always returns exactly one entry. It matters in "Search in log" mode, where it reorders the result by how often each code appears.
Is my log or response data uploaded anywhere?
No. The lookup runs entirely in your browser against a small built-in table of status codes - nothing you paste is ever sent to a server.