Skip to content
Toolden

TOOLDENDEVELOPERON-DEVICE

HTTP Status Codes: Reference Guide

Complete reference of HTTP status codes with descriptions and categories.

Matches code, phrase and description. Results filter live on the right.

62 shown
most looked up
Search or pick a category on the left, matching codes appear on the right with a copy button each.
100

Continue

The server has received the request headers and the client should proceed to send the request body.

101

Switching Protocols

The requester has asked the server to switch protocols and the server has agreed to do so.

102

Processing

The server has received and is processing the request, but no response is available yet.

103

Early Hints

Used to return some response headers before final HTTP message.

200

OK

Standard response for successful HTTP requests.

201

Created

The request has been fulfilled, resulting in the creation of a new resource.

202

Accepted

The request has been accepted for processing, but the processing has not been completed.

203

Non-Authoritative Information

The request was successful but the enclosed payload has been modified from that of the origin server.

204

No Content

The request was successful but there is no content to return.

205

Reset Content

The request was successful and the user agent should reset the document view.

206

Partial Content

The server is delivering only part of the resource due to a range header sent by the client.

207

Multi-Status

The message body that follows is an XML message and can contain a number of separate response codes.

208

Already Reported

The members of a DAV binding have already been enumerated in a preceding part of the multistatus response.

226

IM Used

The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

300

Multiple Choices

Indicates multiple options for the resource from which the client may choose.

301

Moved Permanently

This and all future requests should be directed to the given URI.

302

Found

The resource was found but at a different URI.

303

See Other

The response to the request can be found under another URI using a GET method.

304

Not Modified

Indicates that the resource has not been modified since the version specified by the request headers.

305

Use Proxy

The requested resource is available only through a proxy.

307

Temporary Redirect

The request should be repeated with another URI; however, future requests should still use the original URI.

308

Permanent Redirect

The request and all future requests should be repeated using another URI.

400

Bad Request

The server cannot or will not process the request due to an apparent client error.

401

Unauthorized

Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.

402

Payment Required

Reserved for future use.

403

Forbidden

The request was valid, but the server is refusing to respond to it.

404

Not Found

The requested resource could not be found but may be available in the future.

405

Method Not Allowed

A request method is not supported for the requested resource.

406

Not Acceptable

The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.

407

Proxy Authentication Required

The client must first authenticate itself with the proxy.

408

Request Timeout

The server timed out waiting for the request.

409

Conflict

Indicates that the request could not be processed because of conflict in the current state of the resource.

410

Gone

Indicates that the resource requested is no longer available and will not be available again.

411

Length Required

The request did not specify the length of its content, which is required by the requested resource.

412

Precondition Failed

The server does not meet one of the preconditions that the requester put on the request.

413

Payload Too Large

The request is larger than the server is willing or able to process.

414

URI Too Long

The URI provided was too long for the server to process.

415

Unsupported Media Type

The request entity has a media type which the server or resource does not support.

416

Range Not Satisfiable

The client has asked for a portion of the file that lies beyond the end of the file.

417

Expectation Failed

The server cannot meet the requirements of the Expect request-header field.

418

I'm a teapot

This code was defined in 1998 as one of the traditional IETF April Fools jokes.

421

Misdirected Request

The request was directed at a server that is not able to produce a response.

422

Unprocessable Entity

The request was well-formed but was unable to be followed due to semantic errors.

423

Locked

The resource that is being accessed is locked.

424

Failed Dependency

The request failed due to failure of a previous request.

425

Too Early

Indicates that the server is unwilling to risk processing a request that might be replayed.

426

Upgrade Required

The client should switch to a different protocol.

428

Precondition Required

The origin server requires the request to be conditional.

429

Too Many Requests

The user has sent too many requests in a given amount of time.

431

Request Header Fields Too Large

The server is unwilling to process the request because its header fields are too large.

451

Unavailable For Legal Reasons

A server operator has received a legal demand to deny access to a resource.

500

Internal Server Error

A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

501

Not Implemented

The server either does not recognize the request method, or it lacks the ability to fulfill the request.

502

Bad Gateway

The server was acting as a gateway or proxy and received an invalid response from the upstream server.

503

Service Unavailable

The server is currently unavailable (because it is overloaded or down for maintenance).

504

Gateway Timeout

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

505

HTTP Version Not Supported

The server does not support the HTTP protocol version used in the request.

506

Variant Also Negotiates

Transparent content negotiation for the resource results in a circular reference.

507

Insufficient Storage

The server is unable to store the representation needed to complete the request.

508

Loop Detected

The server detected an infinite loop while processing the request.

510

Not Extended

Further extensions to the request are required for the server to fulfill it.

511

Network Authentication Required

The client needs to authenticate to gain network access.

Showing 62 of 62 codes. Each row has its own copy button.

HOW TO USE

  1. 1Type a code, phrase or keyword in the search box on the left.
  2. 2Pick one of the five categories on the left to narrow the list.
  3. 3Tap a common code chip on the left for instant lookup.
  4. 4Read the matches on the right and copy any code with its button.

EXAMPLE

INPUT

404

OUTPUT

404 Not Found, the server could not find the requested resource.

FAQ

What are the five HTTP status code categories?
1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error and 5xx Server Error.
What is the difference between 401 and 403?
401 Unauthorized means you are not authenticated; 403 Forbidden means you are authenticated but lack permission.
What is the difference between 4xx and 5xx?
4xx errors mean the client sent an invalid request (bad URL, missing auth). 5xx errors mean the server failed to fulfill a valid request.
How should I handle 429 errors?
429 means Too Many Requests — implement exponential backoff and respect the Retry-After header if present.

RELATED TOOLS

Regex Tester↗JSON Formatter↗CIDR Calculator↗