HTTP Status Code Lookup
Searchable reference table of all HTTP status codes with descriptions, categorised by 1xx through 5xx.
How to use this tool
- 1Type a code number, name, or keyword into the search box to filter the list.
- 2Click a category button (1xx, 2xx, 3xx, 4xx, 5xx) to show only that group.
- 3Click All to clear the category filter.
About HTTP Status Code Lookup
This HTTP status code lookup is a searchable reference of 1xx–5xx codes with short descriptions — filter by category or keyword.
Debugging APIs means remembering whether 422 or 409 fits. A quick table beats scrolling MDN mid-incident.
Type a code number, name, or keyword into the search box to filter the list. Click a category button (1xx, 2xx, 3xx, 4xx, 5xx) to show only that group. Click All to clear the category filter. Processing stays in your browser.
Use it while writing clients and reading gateway logs. Vendor-specific codes exist beyond the RFC set.
Memorizing codes does not replace reading error bodies. Vendors add non-standard codes. Search by number or phrase.
Close the tab when you finish so sensitive input is not left in page memory.
Code examples
JavaScript (fetch)
const res = await fetch("/api/data");
if (res.status === 200) { /* OK */ }
if (res.status === 401) { /* Unauthorized — redirect to login */ }
if (res.status === 429) { /* Too Many Requests — back off */ }
if (res.status >= 500) { /* Server error — retry */ }Python (requests)
import requests
r = requests.get("https://api.example.com/data")
r.raise_for_status() # raises HTTPError for 4xx/5xx
print(r.status_code, r.json())Frequently asked questions
Different tools use different definitions and parsers, so small gaps are common. HTTP Status Code Lookup applies an in-page reference table with instant filtering with one consistent browser-side rule set. Hidden characters, stricter syntax, or a different tokenizer usually explain the mismatch. Reduce the input to a minimal sample, then add pieces back until the difference appears. Match the rule your destination actually enforces.
Treat the error as a signal that this environment is stricter or configured differently. Browser APIs reject malformed structures early instead of guessing. Convert to a boring intermediate when it helps—plain UTF-8 text, PNG, WAV, or an unlocked PDF—then retry. If the intermediate works, the original encoding was the problem. Keep that minimal sample for the next regression check.
Runtimes disagree even when feature names match. Locales, parser strictness, codec builds, and library versions differ between your browser and CI. Export the exact bytes from HTTP Status Code Lookup, hash them, and compare in the pipeline. Align normalization steps so both systems see the same input. Use the browser result as a reference artifact, then make CI match it.
Desktop apps win on deep feature sets, batch farms, and specialized hardware paths. HTTP Status Code Lookup wins on zero install, private local processing, and speed for the everyday job on this page. Choose desktop software for multi-hour editorial work or exotic edge formats. Choose this tool when you need a correct result quickly without uploading. Many people do a quick pass here first, then open the heavy suite only if an edge case demands it.
Prefer HTTP Status Code Lookup whenever the input is personal, unpublished, customer-owned, or under NDA, because the core transform stays in your browser via an in-page reference table with instant filtering. Cloud services can still help for formats your browser truly cannot decode, but you must trust their retention policy. Strip secrets before any upload. Privacy is usually the reason to stay local—not a longer marketing checklist.
Start from the best original input you still have. Change only what the destination requires. Prefer lossless intermediates when you must convert twice. Because the tool is local, iterate in small steps: tweak one setting, re-run, compare. Spot-check a short sample before batching anything important.
No account is required for normal use. The core http status codes transform runs in your browser on your device using an in-page reference table with instant filtering. You get on-screen output, a copy action, or a download without a mandatory ToolBrigade upload for that step. Keep your browser updated. A few lookup utilities may call public reference APIs for live fields only—they still do not need your private documents.
Lighter text, code, calculator, and many image jobs work on modern phones. Large video encodes and huge PDFs are happier on a plugged-in laptop with more RAM. Fully client-side flows can continue offline once scripts are cached; live lookups still need network. If a run seems stuck, try a smaller sample, free memory by closing tabs, and confirm the input is not truncated. Prove the path on a short fixture before blaming the algorithm.