HTTP Status Code Reference
Searchable reference of every HTTP status code (1xx-5xx) with descriptions and when to use each.
Searchable reference of every HTTP status code (1xx-5xx) with descriptions and when to use each.
This free HTTP Status Code Reference from KX Toolkit is part of our all-in-one online toolkit. It runs entirely in your browser, so your data never leaves your device for client-side operations. 100% free, forever - no paywall, no credit card, no trial.
How to use the HTTP Status Code Reference
- Paste your input - JSON, regex pattern, JWT, URL etc.
- Pick any flags or options the tool supports.
- Click the action button (Format, Test, Decode).
- Copy the result or download it as a file.
What you can do with the HTTP Status Code Reference
- Format and validate API responses while debugging.
- Test regex patterns against real input before deploying.
- Decode JWTs to inspect claims and expiry.
- Generate UUIDs for migrations, tests and seeders.
Why use KX Toolkit's HTTP Status Code Reference
- Browser-based: Works on Windows, macOS, Linux, iOS and Android - no install, no extension.
- Privacy-first: Client-side tools never upload your data; server-side tools delete files right after processing.
- Mobile-friendly: Full feature parity on phones and tablets - not a stripped-down view.
- Fast: Optimised for instant feedback. No artificial waiting screens, no email-gated downloads.
- One hub for everything: 300+ tools across SEO, text, image, PDF, code, color, calculators and more - skip switching between sites.
Tips for the best results
Bookmark the most-used tools - your browser bookmark bar is faster than retyping the URL every time.
Related Developer Tools
If you find this tool useful, explore the full Developer Tools collection or browse our complete tool directory. KX Toolkit is built for marketers, developers, designers, students and anyone who needs a quick utility without signing up for yet another SaaS.
What do the five status code classes mean?
The first digit defines the class. 1xx is informational (rarely seen by users). 2xx means success - the request was understood and processed. 3xx means redirection - the resource has moved or further action is needed. 4xx is a client error - the request was malformed or unauthorized. 5xx is a server error - the server failed to fulfill a valid request.
When should I use 401 versus 403?
401 Unauthorized means the request lacks valid credentials - the client should authenticate and retry. 403 Forbidden means the server understood and authenticated the request but refuses to perform it - the user has the wrong role or permission. The distinction matters because clients reauthenticate on 401 but not on 403, and confusing them leads to retry loops or stuck UIs.
Is 200 always the right success code?
Not always. Use 201 Created when a POST creates a new resource and ideally include a Location header pointing to it. Use 202 Accepted for asynchronous work that has been queued. Use 204 No Content when there is no body to return - common for DELETE responses. Reserving 200 for plain GET responses keeps the API's intent clearer to consumers.
What is the difference between 301 and 302 redirects?
301 Moved Permanently signals the resource has a new permanent home; clients and search engines update their references. 302 Found is a temporary redirect; bookmarks and SEO stay with the original URL. 307 and 308 are stricter modern equivalents that preserve the HTTP method on redirect, where 301 and 302 historically did not. Use 308 for permanent and 307 for temporary in new APIs.
When should an API return 422 instead of 400?
400 Bad Request means the request itself is malformed - invalid JSON, missing required fields, or the wrong content type. 422 Unprocessable Entity means the syntax is valid but the data fails business validation, like an email already in use. Many APIs use 400 for both, but separating them helps clients distinguish between developer bugs and user-visible validation errors.
What are the most useful 5xx codes to know?
500 Internal Server Error is the catch-all for unhandled exceptions. 502 Bad Gateway means a proxy or load balancer got an invalid response from upstream. 503 Service Unavailable signals overload or maintenance and pairs well with a Retry-After header. 504 Gateway Timeout means the upstream did not respond in time. Pick the most specific one to give clients better retry strategies.
No reviews yet
Be the first to share your experience with the HTTP Status Code Reference.