Loading your tools...
Loading your tools...
Complete list of HTTP, SMTP, and FTP status codes with search. 1xx informational, 2xx success, 3xx redirection, 4xx client error, 5xx server error.
62 status codes found
HTTP stands for Hypertext Transfer Protocol. Common methods:
| Method | Description | Safe | Idempotent |
|---|---|---|---|
| GET | Retrieve a resource | Yes | Yes |
| POST | Create a resource or submit data | No | No |
| PUT | Replace a resource | No | Yes |
| PATCH | Partially update a resource | No | No |
| DELETE | Delete a resource | No | Yes |
| HEAD | Same as GET but headers only | Yes | Yes |
| OPTIONS | Describe communication options | Yes | Yes |
| CONNECT | Establish tunnel (e.g. SSL) | No | No |
| TRACE | Message loop-back test | Yes | Yes |
Search by code (e.g. 404, 200), name, or description.
Filter by protocol: HTTP, SMTP, or FTP. Filter by category: 1xx, 2xx, 3xx, 4xx, 5xx.
Click a row to expand and see when/where/why you get each status code.
http status codes 200: Verify success responses in APIs
http status codes 404: Debug broken links, missing resources
http status codes 400: Understand validation errors
http status codes 500: Troubleshoot server errors
http status codes table: Quick reference for REST APIs
http-status-codes npm: Alternative to Node.js package
node http status codes: Use in Express res.status(200)
http status codes github: Reference for API design
HTTP status codes are three-digit responses from a server indicating request outcome. 1xx: Informational (request received, continuing). 2xx: Success (request succeeded). 3xx: Redirection (further action needed). 4xx: Client Error (bad request, unauthorized, not found). 5xx: Server Error (server failed). http stands for Hypertext Transfer Protocol. This tool provides a complete http status codes table with http status codes 200, 201, 400, 404, 500 with examples. Also includes SMTP (email) and FTP status codes. http-status-codes npm and node http status codes alternative.
Common codes: 200 OK (success), 201 Created (POST created resource), 204 No Content (success, no body), 301/302 (redirects), 304 Not Modified (use cache), 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 429 Too Many Requests, 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable.
Use 204 for successful DELETE. Use 201 with Location header for POST. Use 429 with Retry-After for rate limiting. http status codes 418 I'm a teapot is from RFC 2324 (April Fools).
1xx: 100 Continue, 101 Switching Protocols, 102 Processing, 103 Early Hints. 2xx: 200 OK, 201 Created, 202 Accepted, 204 No Content, 206 Partial Content. 3xx: 301 Moved Permanently, 302 Found, 304 Not Modified, 307 Temporary Redirect, 308 Permanent Redirect. 4xx: 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 429 Too Many Requests. 5xx: 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable, 504 Gateway Timeout.
http methods: GET (retrieve), POST (create), PUT (replace), PATCH (update), DELETE (remove), HEAD (headers only), OPTIONS (capabilities). Use 200/204 for GET/DELETE success, 201 for POST success, 400 for bad input, 404 for not found, 500 for server error.