HTTP Status Code Lookup
Search every HTTP status code with practical guidance on when to use it.
No status code matches that
Try just the number, or a word from the situation you are in — “timeout”, “redirect”, “rate limit”.
Runs entirely in your browser. Your data isn't uploaded — this page makes no network request with anything you type, which you can verify in your browser's network tab. How this works.
What is the HTTP Status Code Lookup?
HTTP status codes are a small, stable vocabulary that carries a lot of meaning, and most arguments about them are really about the handful of distinctions that matter: 401 versus 403, 400 versus 422, 301 versus 308, 502 versus 504.
This reference lists every standard code with its specification definition and, more usefully, practical guidance on when to return it, whether the response may carry a body, and whether it is cacheable by default.
How to use it
- Type a code, or a word from its name, into the search box.
- Filter by class — 1xx informational through 5xx server error.
- Open a code to see the specification wording, practical guidance and related codes it is often confused with.
Example
Looking up 409.
409
409 Conflict The request conflicts with the current state of the target resource. Return it when: an optimistic-concurrency check failed, or a uniqueness constraint was violated. Include enough detail for the client to resolve it. Body allowed: yes. Cacheable: no.
Features
- Every IANA-registered status code, plus widely used unofficial ones
- Search by number, name or symptom
- Practical "return this when" guidance, not just the specification text
- Cacheability and body-allowed notes
- Side-by-side comparison of commonly confused pairs