HTTP Status Codes
HTTP Status Codes — runs in your browser. Inputs are not stored.
HTTP status codes
A static list of common HTTP status codes built into the browser. It does not call a remote API.
How to use
- In Search (code / text), type a number or an English/Korean description. Examples: 404, Not Found, redirect.
- The table filters and the shown number above counts remaining rows.
- On a row, check the meaning and the 1xx–5xx class.
- To clear search, press Reset search.
- The list is not fetched remotely. It is a static table built into the page.
Key concepts
The HTTP status code table is a static list of common codes built into the browser. It does not fetch the full IANA registry live. Search matches code numbers and English/Korean descriptions. There is no network round-trip, so you can use the table in near-offline environments.
1xx is often informational, 2xx success, 3xx redirect, 4xx client, 5xx server error. Real APIs can use the same number with a different body reason, so read the service docs too. Rare experimental codes may be missing from the table.
Example
Type 404 in search and the Not Found row remains. Search “redirect” in Korean and 3xx rows filter in. If shown is 0, change the spelling or reset. Compare 401 and 403 from the table descriptions, then match them to your API responses. Search works on Korean descriptions as well as numbers, so you can narrow by a class word like redirect. The list focuses on common codes, so obscure experimental ones may be absent. Meanings in the table are a reference; real API docs differ by service. When retrying, reset first so old output is not mixed in. On a shared computer, clear the field when you finish. Closing the tab discards what you typed; no server delete is needed. Labels match the tool at the top of the page. If the result is empty, check required fields and hidden errors. This article is a how-to; it does not mean input is stored off-site. On mobile, Copy may ask for clipboard permission—allow it, then press again.
Related: User-Agent info
Frequently asked questions
Does the HTTP status code table fetch the full IANA registry?
No. It is a static list of common codes built into the script.
Can I search in Korean?
Yes. Entries with Korean descriptions can be narrowed by a word such as redirect.
Does it call a remote API?
No. It only filters the table built into the page.
Are 401 and 403 explained in the table?
They are common codes, so description rows exist. Read service docs together for auth vs. permission.
What is the shown number?
The number of rows left in the table after search.
Are newer codes like 103 included?
The list is common-code focused, so newest or experimental codes may be missing.
Last reviewed: 2026-09-04