HTTP Status Code Reference

Searchable HTTP status code reference (1xx → 5xx) with short descriptions and typical use cases. Filter by class, copy a code, link to the IETF spec.

61 / 61

100

ContinueInformational

Initial part of request received; continue with the rest.

101

Switching ProtocolsInformational

Server is switching protocols per Upgrade header (e.g., HTTP → WebSocket).

102

ProcessingInformational

WebDAV: request being processed; no response yet.

103

Early HintsInformational

Hint at resources the client can start fetching while final response is prepared.

200

OKSuccess

Request succeeded; semantics depend on the method.

201

CreatedSuccess

New resource created — typically returned by POST.

202

AcceptedSuccess

Request accepted but not yet processed (async work).

203

Non-Authoritative InformationSuccess

Response was modified by a transforming proxy.

204

No ContentSuccess

Success, but no body — used for DELETE and idempotent updates.

205

Reset ContentSuccess

Tell the client to reset the document view (e.g., clear a form).

206

Partial ContentSuccess

Partial response per Range header — used for resumable downloads and streaming.

207

Multi-StatusSuccess

WebDAV: multiple status codes inside the body (XML).

208

Already ReportedSuccess

WebDAV: members already enumerated in a previous reply.

226

IM UsedSuccess

Delta encoding: server fulfilled the request using one or more instance-manipulations.

300

Multiple ChoicesRedirection

Resource has multiple representations; client picks one.

301

Moved PermanentlyRedirection

Resource permanently moved to a new URL — update bookmarks and links.

302

FoundRedirection

Temporary redirect — the request method may change in practice.

303

See OtherRedirection

Tells client to GET the resource at a different URL — POST/Redirect/GET pattern.

304

Not ModifiedRedirection

Cached response is still valid; no body sent.

307

Temporary RedirectRedirection

Like 302 but preserves the request method.

308

Permanent RedirectRedirection

Like 301 but preserves the request method.

400

Bad RequestClient Error

Malformed syntax, invalid framing, or a request the server cannot understand.

401

UnauthorizedClient Error

Authentication required or failed — see the WWW-Authenticate header.

402

Payment RequiredClient Error

Reserved for paid resources; rarely used in practice.

403

ForbiddenClient Error

Authenticated, but access is denied for this resource.

404

Not FoundClient Error

No resource at that URL — by far the most common error.

405

Method Not AllowedClient Error

Method not supported for this resource — see the Allow header.

406

Not AcceptableClient Error

Server cannot produce a response matching the Accept-* headers.

407

Proxy Authentication RequiredClient Error

Like 401 but for the proxy in front of the server.

408

Request TimeoutClient Error

Server closed the connection because the request was too slow.

409

ConflictClient Error

Request conflicts with current resource state (e.g., concurrent edit).

410

GoneClient Error

Resource permanently removed — no forwarding URL.

411

Length RequiredClient Error

Content-Length header is required for this request.

412

Precondition FailedClient Error

If-Match / If-Unmodified-Since condition not satisfied.

413

Content Too LargeClient Error

Request body exceeds server limits (previously Payload Too Large).

414

URI Too LongClient Error

URL longer than the server accepts.

415

Unsupported Media TypeClient Error

Content-Type not supported for this endpoint.

416

Range Not SatisfiableClient Error

Requested Range cannot be returned (e.g., past the end of file).

417

Expectation FailedClient Error

Server cannot meet the Expect header requirement.

418

I'm a teapotClient Error

April Fools joke (RFC 2324). Returned by some sites for impossible requests.

421

Misdirected RequestClient Error

Request sent to a server that cannot answer for this hostname/authority.

422

Unprocessable ContentClient Error

Request is syntactically OK but semantically invalid — common for form validation.

423

LockedClient Error

WebDAV: resource is locked.

424

Failed DependencyClient Error

WebDAV: a prior request in a multi-request chain failed.

425

Too EarlyClient Error

Server is unwilling to process a request that may be replayed.

426

Upgrade RequiredClient Error

Client must switch protocols (see the Upgrade header).

428

Precondition RequiredClient Error

Server requires the request to be conditional — protects against lost-update.

429

Too Many RequestsClient Error

Rate-limited — see the Retry-After header.

431

Request Header Fields Too LargeClient Error

Total request headers exceed server limits.

451

Unavailable For Legal ReasonsClient Error

Blocked due to legal demand — name is a Fahrenheit 451 reference.

500

Internal Server ErrorServer Error

Generic server-side failure — typically a bug or unhandled exception.

501

Not ImplementedServer Error

Server does not support the request method.

502

Bad GatewayServer Error

Upstream server returned an invalid response to a proxy.

503

Service UnavailableServer Error

Server is overloaded or down for maintenance — try later.

504

Gateway TimeoutServer Error

Upstream server timed out before responding to a proxy.

505

HTTP Version Not SupportedServer Error

HTTP version in the request is unsupported.

506

Variant Also NegotiatesServer Error

Content negotiation loop detected on the server.

507

Insufficient StorageServer Error

WebDAV: server out of storage for the request.

508

Loop DetectedServer Error

WebDAV: infinite loop detected while processing.

510

Not ExtendedServer Error

Server requires further extensions to fulfill the request.

511

Network Authentication RequiredServer Error

Client must authenticate to gain network access (captive portals).

Loading…

All processing runs in your browser — no files or inputs are uploaded to a server.

Related tools

cURL → Code Converter

Developer

Paste a curl command and get the equivalent fetch, axios, Go net/http, and Python requests snippet. Handles -X, -H, -d / --data, -u, --form, and multiline backslash continuation.

JSON Formatter

Developer

Format and validate JSON. Indented or minified output, with clear error messages.

Base64 Encoder / Decoder

Developer

Encode text to Base64 or decode Base64 back to text. UTF-8 safe.

URL Encoder / Decoder

Developer

Percent-encode or decode URL components.