HTTP Status Code Reference
Searchable, dated snapshot of the IANA status registry with RFC references.
- 100ContinueRFC 9110 §15.2.1
Interim ack; the client may finish sending the request body.
- 101Switching ProtocolsRFC 9110 §15.2.2
The server agreed to switch protocols (e.g. to WebSocket).
- 103Early HintsRFC 8297
Preload hints sent before the final response.
- 200OKRFC 9110 §15.3.1
The request succeeded; the meaning of the body depends on the method.
- 201CreatedRFC 9110 §15.3.2
A new resource was created; Location says where.
- 202AcceptedRFC 9110 §15.3.3
Queued for processing, but completion is not guaranteed yet.
- 204No ContentRFC 9110 §15.3.5
Success with no body (common for DELETE and PUT).
- 206Partial ContentRFC 9110 §15.3.7
A Range request was satisfied; Content-Range describes the slice.
- 300Multiple ChoicesRFC 9110 §15.4.1
More than one representation exists; the client picks.
- 301Moved PermanentlyRFC 9110 §15.4.2
Permanent new location, so caches and links should update.
- 302FoundRFC 9110 §15.4.3
Temporary redirect; the method may change in practice (see 307/308).
- 303See OtherRFC 9110 §15.4.4
Fetch the target with GET; this is the post-POST redirect.
- 304Not ModifiedRFC 9110 §15.4.5
Conditional GET hit; the cached copy is still fresh.
- 307Temporary RedirectRFC 9110 §15.4.8
Temporary redirect that preserves the request method.
- 308Permanent RedirectRFC 9110 §15.4.9
Permanent redirect that preserves the request method.
- 400Bad RequestRFC 9110 §15.5.1
Malformed syntax the server refuses to process.
- 401UnauthorizedRFC 9110 §15.5.2
Authentication missing or failed (the name means unauthenticated).
- 402Payment RequiredRFC 9110 §15.5.3
Reserved, with no standard use.
- 403ForbiddenRFC 9110 §15.5.4
Authenticated but not allowed; do not retry with the same rights.
- 404Not FoundRFC 9110 §15.5.5
No resource at this URI; the catch-all client error.
- 405Method Not AllowedRFC 9110 §15.5.6
The method is not supported; Allow lists what is.
- 406Not AcceptableRFC 9110 §15.5.7
No representation matches the Accept headers.
- 408Request TimeoutRFC 9110 §15.5.9
The client took too long to finish sending.
- 409ConflictRFC 9110 §15.5.10
State conflict: concurrent edit, name clash, stale resource.
- 410GoneRFC 9110 §15.5.11
Deliberately removed: a permanent 404 with intent.
- 411Length RequiredRFC 9110 §15.5.12
Content-Length is required and missing.
- 412Precondition FailedRFC 9110 §15.5.13
An If-Match/If-Unmodified-Since guard rejected the request.
- 413Content Too LargeRFC 9110 §15.5.14
The body exceeds what the server accepts.
- 414URI Too LongRFC 9110 §15.5.15
The request-target exceeds the server's limits.
- 415Unsupported Media TypeRFC 9110 §15.5.16
The body's format is not supported.
- 416Range Not SatisfiableRFC 9110 §15.5.17
The requested Range lies outside the representation.
- 417Expectation FailedRFC 9110 §15.5.18
The Expect header cannot be met.
- 418I'm a teapotRFC 2324 §2.3.2
The 1998 April-fools teapot; real servers should not send it.
- 422Unprocessable ContentRFC 9110 §15.5.21
Well-formed but semantically invalid (the classic API validation error).
- 425Too EarlyRFC 8470
Replay-risk window; the server refuses early retries.
- 428Precondition RequiredRFC 6585 §3
The server demands conditional requests to avoid lost updates.
- 429Too Many RequestsRFC 6585 §4
Rate limited; Retry-After says when to come back.
- 431Request Header Fields Too LargeRFC 6585 §5
Header block exceeds limits (cookie bloat's favorite error).
- 451Unavailable For Legal ReasonsRFC 7725
Blocked for legal reasons; the response explains which.
- 500Internal Server ErrorRFC 9110 §15.6.1
The server broke; this is the catch-all server error.
- 501Not ImplementedRFC 9110 §15.6.2
The server does not support the functionality at all.
- 502Bad GatewayRFC 9110 §15.6.3
An upstream dependency returned something invalid.
- 503Service UnavailableRFC 9110 §15.6.4
Temporarily down or overloaded; Retry-After may say when.
- 504Gateway TimeoutRFC 9110 §15.6.5
An upstream did not answer in time.
- 505HTTP Version Not SupportedRFC 9110 §15.6.6
The requested HTTP version is refused.
- 507Insufficient StorageRFC 4918 §11.5
The server cannot store the representation (WebDAV).
- 508Loop DetectedRFC 5842 §7.2
Infinite bind-loop detected (WebDAV).
- 511Network Authentication RequiredRFC 6585 §6
Captive portal: authenticate to the network first.
Finished here in the tab. Nothing was uploaded.