HTTP Status Codes
Searchable reference of all HTTP status codes with explanations.
1xx Informational
100
Continue
The initial part of a request was received, please continue.
101
Switching Protocols
The server is switching protocols as requested by the client.
2xx Success
200
OK
The request has succeeded.
201
Created
The request has been fulfilled and a new resource was created.
202
Accepted
The request has been accepted for processing.
204
No Content
The request was successful but there is no content to return.
206
Partial Content
Partial content delivered as requested by a Range header.
3xx Redirection
301
Moved Permanently
The resource has been moved to a new URL permanently.
302
Found
The resource is temporarily located at a different URL.
304
Not Modified
Cached version is still valid; no body returned.
307
Temporary Redirect
Same as 302 but the method must not change.
308
Permanent Redirect
Same as 301 but the method must not change.
4xx Client Error
400
Bad Request
The server cannot process the request due to a client error.
401
Unauthorized
Authentication is required and has failed or not been provided.
403
Forbidden
The server understood the request but refuses to authorize it.
404
Not Found
The requested resource could not be found.
405
Method Not Allowed
The request method is not supported for this resource.
408
Request Timeout
The server timed out waiting for the request.
409
Conflict
The request conflicts with the current state of the resource.
410
Gone
The resource is no longer available and will not be available again.
413
Payload Too Large
The request body is larger than the server is willing to process.
415
Unsupported Media Type
The media type is not supported by the server.
422
Unprocessable Entity
The request was well-formed but contained semantic errors.
429
Too Many Requests
The user has sent too many requests in a given time (rate limited).
5xx Server Error
500
Internal Server Error
A generic server error.
501
Not Implemented
The server does not support the functionality required.
502
Bad Gateway
Invalid response from an upstream server.
503
Service Unavailable
The server is overloaded or down for maintenance.
504
Gateway Timeout
Upstream server failed to respond in time.
Private & SecureRuns in your browser — nothing is uploaded
Easy to UseJust paste or type — instant results
Free ForeverUnlimited use, no sign-up
Fast & ReliableAdvanced tech, fast and stable
When an API or a page returns a bare number like 404 or 502, it is telling you exactly what went wrong, if you know the code. This is a full, searchable reference to every HTTP status code, grouped by class, so you can look one up and know whether the problem is your request, the server, or just a redirect.
How to use: HTTP Status Codes
- 1Enter inputType a status code number or keyword (e.g. 404 or Not Found) in the search box.
- 2Set optionsFind the matching HTTP status code in the filtered list.
- 3ProcessRead its category (1xx-5xx) and clear explanation.
- 4Get resultCopy the code or description for documentation or API troubleshooting.
Common use cases
Debug an API callLook up the code your request came back with to see whether to fix the call or the server.
Pick the right responseReturn the correct status from your own endpoint instead of defaulting to 200 or 500.
Read server logsMake sense of the status numbers filling an access log at a glance.
Settle 401 vs 403Check the precise meaning when two close codes are easy to confuse.
Good to know
The first digit is the class1xx is informational, 2xx success, 3xx redirect, 4xx your request, 5xx the server. That alone tells you which side to look at.
401 is not 403A 401 means you are not authenticated; a 403 means you are, but not allowed. They call for different fixes.
Some codes are rare or unofficialYou will occasionally meet codes like 418, jokes or vendor-specific ones; do not build logic around the obscure ones.
A code is a hint, not the whole storyThe number narrows it down, but the real error detail is often in the response body, so read both.