By ToolzHive · Updated
The first digit indicates a family: 1xx progress, 2xx success, 3xx redirection, 4xx a request problem and 5xx a server problem. This table focuses on common website and API responses.
Reference table
| Code | Meaning | Practical interpretation |
|---|---|---|
| 100 | Continue | The client may continue sending the body. |
| 103 | Early Hints | Preliminary resource hints. |
| 200 | OK | Success; interpret the body according to the method. |
| 201 | Created | A resource was created. |
| 202 | Accepted | Processing accepted, not necessarily complete. |
| 204 | No Content | Success without a body. |
| 206 | Partial Content | A requested range of the representation. |
| 301 | Moved Permanently | Permanent redirect; POST may become GET. |
| 302 | Found | Temporary redirect; POST may become GET. |
| 303 | See Other | Retrieve another resource, usually with GET. |
| 304 | Not Modified | Use the cached representation. |
| 307 | Temporary Redirect | Preserves method and body. |
| 308 | Permanent Redirect | Preserves method and body. |
| 400 | Bad Request | Cannot process the request as sent. |
| 401 | Unauthorized | Inspect WWW-Authenticate. |
| 403 | Forbidden | The server refuses the request. |
| 404 | Not Found | No representation found, or existence concealed. |
| 405 | Method Not Allowed | Inspect Allow. |
| 409 | Conflict | Conflicts with current state. |
| 410 | Gone | Intentionally unavailable, likely permanently. |
| 413 | Content Too Large | Request body exceeds the accepted limit. |
| 415 | Unsupported Media Type | Check the body format and Content-Type. |
| 422 | Unprocessable Content | Content understood; instructions cannot be processed. |
| 429 | Too Many Requests | Respect Retry-After when present. |
| 500 | Internal Server Error | Unexpected server failure. |
| 502 | Bad Gateway | Invalid upstream response. |
| 503 | Service Unavailable | Temporarily unable to serve requests. |
| 504 | Gateway Timeout | Upstream response did not arrive in time. |
Redirect example
Use a method-preserving redirect such as 308 when a permanent API relocation must retain the request body. A form submission followed by a confirmation page commonly uses 303.
Nonstandard codes
419 and 520 are not ordinary registered HTTP codes. Check the framework or proxy that produced them.
Try the related tools
- HTTP Headers Checker — View the HTTP response headers and status code of any URL, with a security header review.
- Redirect Checker — Trace every redirect hop of a URL with status codes (301, 302, 307, 308) and the final destination.