Search and filter all HTTP status codes. Click any card to see full details, use cases, and context.
Showing 60 of 60 status codes
Frequently Asked Questions
What are HTTP status codes?
HTTP status codes are three-digit numbers returned by a server in response to a client's request. They indicate whether the request was successful, redirected, resulted in a client error, or caused a server error. They are grouped into five classes: 1xx (informational), 2xx (success), 3xx (redirection), 4xx (client errors), and 5xx (server errors).
What is the difference between 401 and 403?
401 Unauthorized means the client has not authenticated at all — it needs to provide credentials (e.g., a login token). 403 Forbidden means the client is authenticated but does not have permission to access the requested resource. Think of it this way: 401 is 'Who are you?', while 403 is 'I know who you are, but you can't come in.'
What are the most common HTTP status codes?
The most commonly encountered status codes are: 200 OK (successful request), 201 Created (new resource created), 204 No Content (success with no body), 301/302 (redirects), 400 Bad Request (malformed request), 401 Unauthorized (missing authentication), 403 Forbidden (insufficient permissions), 404 Not Found (resource doesn't exist), 429 Too Many Requests (rate limited), 500 Internal Server Error (server crash), and 503 Service Unavailable (server overloaded).
What is HTTP status code 418?
418 I'm a Teapot is a joke status code defined in RFC 2324 (Hyper Text Coffee Pot Control Protocol) published on April 1, 1998. It means any attempt to brew coffee with a teapot should result in this error. Despite being an April Fools' joke, the code is permanently reserved by the IETF and some developers use it as an Easter egg in their APIs.