ToolbitHTTP Status Code Reference
Look up what a 409 means, when a 422 is more appropriate than a 400, or why your proxy returned a 502 — with the practical explanation, not just the RFC sentence.
What the HTTP Status Code Reference does
- Every status code from 1xx through 5xx, searchable by number or name.
- Practical guidance on when each code is the right choice.
- Common causes for the errors you actually hit in production.
- Available offline once the app is installed.
How to use it
- Type the status code or part of its name.
- Read the meaning and typical causes.
- Pick the right code for your own API response.
Why it runs locally
Toolbit has no backend. The HTTP Status Code Reference is implemented with standard browser APIs, so your input is processed in the tab and never uploaded, logged, or retained. That is what makes it safe to paste real data into — and it is also why the tool keeps working with the network disconnected, once you have installed Toolbit as an app.
Frequently asked questions
- When should I use 422 instead of 400?
- Use 400 when the request is malformed and cannot be parsed; use 422 when it parses fine but fails validation rules.
- What causes a 502 versus a 504?
- A 502 means an upstream server returned an invalid response; a 504 means it did not respond in time. Both point at the layer behind your proxy.
- Does the reference work offline?
- Yes. Toolbit installs as a PWA and ships as a desktop app for macOS, Windows, and Linux, so the whole toolbox keeps working on a plane, behind a corporate firewall, or on an air-gapped machine.