HTTP Status Code Explorer
API & BackendSearch every HTTP status code with meaning, cause and how to respond.
Runs entirely in your browser — nothing is uploaded
Features
- Every registered status code from 1xx to 5xx.
- Search by number, name or symptom.
- Each entry explains the typical cause and the right client response.
- Filter by class to browse a whole family.
How to use the HTTP Status Code Explorer
- 1Search for a code, or filter by class.
- 2Open an entry to read its meaning and common causes.
- 3Follow the guidance on whether the request is safe to retry.
Frequently asked questions
401 or 403?
401 means you are not authenticated — credentials are missing or invalid. 403 means you are authenticated but not allowed to do this.
When should a client retry?
On 429 and 503, honouring Retry-After. On 500 and 502 a bounded retry with backoff is reasonable. Never retry a 4xx that reflects a client mistake.
What is the difference between 301 and 302?
301 says the move is permanent, so clients cache it and search engines pass the page's accumulated signals to the new address. 302 says it is temporary and neither happens. Using 302 for a permanent move is a common mistake that quietly costs a page its ranking.
When should I use 410 rather than 404?
404 means the resource is not here, leaving open that it might return. 410 says it is gone deliberately and is not coming back, which tells crawlers to stop asking sooner. If you are unsure, 404 is the safe choice.