code.liveNewsScore

HTTP Status Explorer

Look up any HTTP status code, what it means, and when it's used. Searchable and grouped by category.

100ContinueInformational

Client should continue with the request.

101Switching ProtocolsInformational

Server is switching protocols per the client's request.

200OKSuccess

Request succeeded.

201CreatedSuccess

Request succeeded and a new resource was created.

202AcceptedSuccess

Request accepted for processing, but not completed yet.

204No ContentSuccess

Request succeeded, no content to return.

206Partial ContentSuccess

Server is delivering part of the resource (range request).

300Multiple ChoicesRedirection

Multiple options for the resource are available.

301Moved PermanentlyRedirection

Resource has permanently moved to a new URL.

302FoundRedirection

Resource temporarily resides at a different URL.

304Not ModifiedRedirection

Cached version is still valid, no need to resend.

307Temporary RedirectRedirection

Resource temporarily at a different URL, method preserved.

308Permanent RedirectRedirection

Resource permanently at a different URL, method preserved.

400Bad RequestClient Error

Server couldn't understand the request due to invalid syntax.

401UnauthorizedClient Error

Authentication is required and has failed or not been provided.

403ForbiddenClient Error

Client does not have access rights to the content.

404Not FoundClient Error

Server can't find the requested resource.

405Method Not AllowedClient Error

Request method is not supported for this resource.

408Request TimeoutClient Error

Server timed out waiting for the request.

409ConflictClient Error

Request conflicts with the current state of the resource.

410GoneClient Error

Resource is permanently gone, no forwarding address.

413Payload Too LargeClient Error

Request body is larger than the server can handle.

415Unsupported Media TypeClient Error

Media format of the request is not supported.

422Unprocessable EntityClient Error

Request is well-formed but semantically incorrect.

429Too Many RequestsClient Error

Client has sent too many requests in a given time.

500Internal Server ErrorServer Error

Server encountered an unexpected condition.

501Not ImplementedServer Error

Server doesn't support the functionality required.

502Bad GatewayServer Error

Server, acting as a gateway, got an invalid response upstream.

503Service UnavailableServer Error

Server is not ready to handle the request (overload/maintenance).

504Gateway TimeoutServer Error

Server, acting as a gateway, didn't get a timely response upstream.

HTTP, DNS & TLS toolkit

Full HTTP, DNS & TLS hub →

Inspect status codes, DNS, SSL certificates, and network connectivity.

Sources

Primary references for claims on this page