HTTP status code reference
1xx informational, 2xx success, 3xx redirection, 4xx client error, 5xx server error.
Code
100
Continue
The initial part of the request has been received; the client should continue.
Code
101
Switching Protocols
The server agrees to switch protocols, e.g. to WebSocket.
Code
200
OK
The request succeeded.
Code
201
Created
The request succeeded and a new resource was created.
Code
202
Accepted
The request was accepted for processing, but isn't complete yet.
Code
204
No Content
The request succeeded but there is no content to return.
Code
206
Partial Content
Returning part of a resource, as requested via a Range header.
Code
301
Moved Permanently
The resource has permanently moved; search engines transfer link equity.
Code
302
Found
A temporary redirect; the original URL stays indexed.
Code
303
See Other
Redirects to a different resource, typically after a POST.
Code
304
Not Modified
The cached version is still valid; no body is returned.
Code
307
Temporary Redirect
Like 302, but guarantees the method and body are repeated.
Code
308
Permanent Redirect
Like 301, but guarantees the method and body are repeated.
Code
400
Bad Request
The server can't process the request due to a client error.
Code
401
Unauthorized
Authentication is required and has not been provided.
Code
403
Forbidden
The server understood the request but refuses to authorize it.
Code
404
Not Found
The requested resource doesn't exist.
Code
405
Method Not Allowed
The HTTP method isn't supported for this resource.
Code
408
Request Timeout
The server timed out waiting for the request.
Code
409
Conflict
The request conflicts with the current state of the resource.
Code
410
Gone
The resource existed once but is permanently gone.
Code
413
Payload Too Large
The request body is larger than the server will accept.
Code
414
URI Too Long
The request URI is longer than the server will process.
Code
415
Unsupported Media Type
The request body's format isn't supported.
Code
418
I'm a Teapot
An April Fools' joke from RFC 2324 — never seriously implemented.
Code
422
Unprocessable Entity
The request is well-formed but semantically invalid.
Code
425
Too Early
The server is unwilling to risk processing a request that might be replayed.
Code
429
Too Many Requests
The client has sent too many requests in a given time (rate limiting).
Code
431
Request Header Fields Too Large
The request's headers are too large.
Code
451
Unavailable For Legal Reasons
The resource is withheld for legal reasons (e.g. censorship).
Code
500
Internal Server Error
A generic server-side error occurred.
Code
501
Not Implemented
The server doesn't support the functionality required.
Code
502
Bad Gateway
A server acting as a gateway got an invalid response upstream.
Code
503
Service Unavailable
The server is temporarily unable to handle the request.
Code
504
Gateway Timeout
A gateway server didn't get a response in time from upstream.
Code
505
HTTP Version Not Supported
The server doesn't support the HTTP version used.
What is HTTP status code reference?
Every HTTP response carries a 3-digit status code that tells the client what happened — 2xx for success, 3xx for redirects, 4xx for client errors, 5xx for server errors — and the exact code often matters for debugging.
How to use it
Search by code number or a keyword from its meaning to find the right one instantly.
Example
Searching "redirect" surfaces 301 Moved Permanently, 302 Found, 307 and 308.