HTTP Status Codes
HTTP Status Codes
Quick reference table for common HTTP response codes with descriptions.
Live
Live update on input changes.
Result
29results
Filter status codes by class and search query.
100
Continue
Request received, continue sending body.
101
Switching Protocols
Server agrees to protocol switch.
200
OK
Request completed successfully.
201
Created
A new resource was created.
202
Accepted
Request accepted for processing.
204
No Content
Success with no response body.
301
Moved Permanently
Resource has a new permanent URL.
302
Found
Resource is temporarily at another URL.
304
Not Modified
Use cached version, resource unchanged.
307
Temporary Redirect
Repeat request at another URI.
308
Permanent Redirect
Permanent redirect preserving method.
400
Bad Request
Server cannot process malformed request.
401
Unauthorized
Authentication is required.
403
Forbidden
Request understood but rejected.
404
Not Found
Requested resource was not found.
405
Method Not Allowed
HTTP method is not allowed for this route.
408
Request Timeout
Server timed out waiting for the request.
409
Conflict
Request conflicts with current resource state.
410
Gone
Resource is permanently unavailable.
413
Payload Too Large
Request body exceeds server limits.
415
Unsupported Media Type
Server does not support this content type.
418
I am a teapot
RFC Easter egg status code.
422
Unprocessable Content
Request syntax valid but semantically invalid.
429
Too Many Requests
Rate limit exceeded.
500
Internal Server Error
Unexpected server-side failure.
501
Not Implemented
Server does not support requested capability.
502
Bad Gateway
Invalid upstream server response.
503
Service Unavailable
Server temporarily unavailable.
504
Gateway Timeout
Upstream server timed out.
| Code | Class | Phrase | Description |
|---|---|---|---|
| 100 | Informational | Continue | Request received, continue sending body. |
| 101 | Informational | Switching Protocols | Server agrees to protocol switch. |
| 200 | Success | OK | Request completed successfully. |
| 201 | Success | Created | A new resource was created. |
| 202 | Success | Accepted | Request accepted for processing. |
| 204 | Success | No Content | Success with no response body. |
| 301 | Redirection | Moved Permanently | Resource has a new permanent URL. |
| 302 | Redirection | Found | Resource is temporarily at another URL. |
| 304 | Redirection | Not Modified | Use cached version, resource unchanged. |
| 307 | Redirection | Temporary Redirect | Repeat request at another URI. |
| 308 | Redirection | Permanent Redirect | Permanent redirect preserving method. |
| 400 | Client Error | Bad Request | Server cannot process malformed request. |
| 401 | Client Error | Unauthorized | Authentication is required. |
| 403 | Client Error | Forbidden | Request understood but rejected. |
| 404 | Client Error | Not Found | Requested resource was not found. |
| 405 | Client Error | Method Not Allowed | HTTP method is not allowed for this route. |
| 408 | Client Error | Request Timeout | Server timed out waiting for the request. |
| 409 | Client Error | Conflict | Request conflicts with current resource state. |
| 410 | Client Error | Gone | Resource is permanently unavailable. |
| 413 | Client Error | Payload Too Large | Request body exceeds server limits. |
| 415 | Client Error | Unsupported Media Type | Server does not support this content type. |
| 418 | Client Error | I am a teapot | RFC Easter egg status code. |
| 422 | Client Error | Unprocessable Content | Request syntax valid but semantically invalid. |
| 429 | Client Error | Too Many Requests | Rate limit exceeded. |
| 500 | Server Error | Internal Server Error | Unexpected server-side failure. |
| 501 | Server Error | Not Implemented | Server does not support requested capability. |
| 502 | Server Error | Bad Gateway | Invalid upstream server response. |
| 503 | Server Error | Service Unavailable | Server temporarily unavailable. |
| 504 | Server Error | Gateway Timeout | Upstream server timed out. |
Reference includes 29 commonly used codes for debugging and API docs.
Your input is processed locally in your browser whenever possible. We do not store your data.
Flow
- Load built-in table of commonly used HTTP statuses.
- Apply class filter and text query matching.
- Render filtered result rows in lookup table.
Example
Worked example: 429 lookup
- 1 Enter query 429 in search field.
- 2 Table filters to matching status code row.
- 3 Description confirms rate limit behavior.
Status meaning is identified instantly.
How
- Type code or phrase in search field.
- Optionally filter by status class.
- Review matched rows with descriptions.
Cases
- Quickly explain API failures to non-backend teammates.
- Document expected response outcomes in endpoint guides.
- Check uncommon status meanings during incident triage.
Avoid
- Confusing 401 Unauthorized with 403 Forbidden semantics.
- Treating 500 errors as client-side issues.
- Ignoring retry behavior for 429 and 503 responses.
FAQ
Does this include every RFC status code?
It includes commonly used codes for practical debugging and documentation.
Can I filter to only client errors?
Yes, select Client Error class to narrow to 4xx responses.
Is this a live API checker?
No, this is a local reference and lookup utility.
Switch
Switch12
No match.