HTTP Status Code Lookup
Search and look up the meaning of any of the 60+ standard HTTP status codes.
A static reference — nothing is sent anywhere.
- Search by number or by phrase, with a plain-English explanation of when each is used.
- Covers all 60+ standard codes across the 1xx–5xx ranges, including less common ones like 402, 418, 425, 428 and 451 — not just the everyday handful.
- A static reference — instant, offline-capable, nothing sent anywhere.
Why this is private
- A static reference — nothing is sent anywhere.
- Open your browser's DevTools → Network tab while using this tool — you won't see a request carrying your input, because it never leaves your device.
- Nothing you enter is uploaded to a server or shared with us — the processing happens entirely on your device.
Overview
A searchable reference covering the full standard IANA-registered set of HTTP status codes — what each one means and when a server would return it.
How to use it
- 1Search by code (e.g. 404) or keyword (e.g. "not found").
Frequently asked questions
What people use it for
Understand a response you're gettingLook up why an API returned 409 or 422 and what the client should do.
Pick the right code for an endpointDecide between 400, 404 and 422, or 301 vs 302 vs 307, when designing an API.
Look up an unusual or rarely-seen codeFind out what 418, 425, 428 or 451 actually mean the moment you encounter one.
Explain an error to a teammateShare the precise meaning rather than guessing.
Read a server or CDN logScan status codes and know which ones need attention.
Related guides
- How to read JSON with a tree viewerA tree viewer turns a wall of brackets into a structure you can expand, search and copy paths from. Here's how to use one effectively.
- JSON parse errors explained: 'Unexpected token', 'Expected comma or brace', and the restWhat each common JSON error message actually means, the usual cause, and how to find the spot fast using line and column.
- How to format JSON (and actually understand the errors)JSON looks like a JavaScript object but follows stricter rules. Here's what those rules are and how to read the errors when they're broken.
Related tools
All developer toolsHTTP Headers AnalyzerParse and explain raw HTTP response headers.URL EncoderPercent-encode text for safe use in URLs, with a component vs. full-URL mode.JSON Viewer & FormatterView, format, validate, edit and beautify JSON with an interactive tree view, plus a shareable link.JSON ValidatorValidate JSON syntax and pinpoint errors instantly.
Ready to use HTTP Status Code Lookup?
HTTP Status Code Lookup