HTTP Status Code Reference
About this tool
A sudden 403 or 502 is easier to debug when you know which side failed. Browse by class and compare with your response.
Features
- Browse 1xx–5xx
- Short meanings, not the full RFC
- Useful next to gateway and API docs
How to use
- Search by code or class.
- Read the meaning.
- Confirm against gateway and app logs.
When to use it
- A sudden 502: gateway vs app
- 401 vs 403
- Docs need the standard code
Examples
- 404 is missing; 500 is an internal server error.
- 301 and 302 both redirect, with different caching.
FAQ
401 vs 403?
401 is unauthenticated; 403 is forbidden after identity is known.
Is 502 always my code?
Often the upstream or proxy. Check both.
Back to DevOps Tools Hub