ST

HTTP Status Codes

Reference for all common HTTP status codes with descriptions

61 codes
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

A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request.

103

Early Hints

Used to return some response headers before final HTTP message. Allows the browser to start preloading resources.

200

OK

Standard response for successful HTTP requests. The actual response will depend on the request method used.

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 server is a transforming proxy that received a 200 OK from its origin but is returning a modified version of the origin's response.

204

No Content

The server successfully processed the request, and is not returning any content.

205

Reset Content

The server successfully processed the request, asks that the requester reset its document view, and is not returning any content.

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 by default 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 multi-status 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

The target resource has more than one representation; the user agent or user can choose one (e.g. different formats or languages).

301

Moved Permanently

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

302

Found

Tells the client to look at (browse to) another URL. The request should be repeated with another URI, but future requests may still use the original URI.

303

See Other

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

304

Not Modified

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

307

Temporary Redirect

In this case, the request should be repeated with another URI, but future requests can 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 such as malformed request syntax.

401

Unauthorized

Authentication is required and has failed or has not yet been provided.

402

Payment Required

Reserved for future use. Originally intended for digital payment systems.

403

Forbidden

The request contained valid data and was understood by the server, but the server is refusing action.

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 was previously in use but 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 header fields.

413

Content 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, but the server cannot supply that portion.

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 Content

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 because it depended on another request and that request failed.

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 such as TLS/1.3.

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 ("rate limiting").

431

Request Header Fields Too Large

The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.

451

Unavailable For Legal Reasons

A server operator has received a legal demand to deny access to a resource or a set of resources.

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 fulfil 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 cannot handle the request (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 version used in the request.

506

Variant Also Negotiates

Transparent content negotiation for the request 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 fulfil it.

511

Network Authentication Required

The client needs to authenticate to gain network access.

Opens your print window: choose "Save as PDF". The file is named "HTTP Status Codes - MondayTool".
About this tool

Last updated:

Look up any common HTTP status code

This HTTP status codes reference lists 59 response codes, each with its official name and a short description. Search by number, name or keyword, or filter by class to see only the codes you need.

How to use it

  1. Type in the search box. You can search a number like 404, a name like Gateway, or a word from the description like redirect.
  2. Click a tab to filter: All, 1xx, 2xx, 3xx, 4xx or 5xx.
  3. Search and tabs work together. The counter shows how many codes match.

How it works

Every HTTP response starts with a three-digit status code. The first digit tells you the class of the response. The list is built into the page and filtered in your browser as you type. It is case-insensitive and matches part of a code, name or description.

The five classes

ClassMeaningExamples in the list
1xxInformational100 Continue, 101 Switching Protocols, 103 Early Hints
2xxSuccess200 OK, 201 Created, 204 No Content
3xxRedirection301 Moved Permanently, 302 Found, 304 Not Modified, 308 Permanent Redirect
4xxClient error400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 429 Too Many Requests
5xxServer error500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable, 504 Gateway Timeout

Tips

  • Use 301 or 308 for a permanent move. Use 302 or 307 for a temporary one. 307 and 308 keep the request method, such as POST.
  • 401 means the client is not authenticated. 403 means it is known but not allowed.
  • 410 Gone tells clients and search engines a page was removed on purpose. 404 only says it was not found.
  • A 502 or 504 often points to a proxy or upstream server, not the app itself.

Frequently asked questions

What is the difference between 4xx and 5xx codes?

4xx codes mean the problem is with the request, such as a wrong URL or missing login. 5xx codes mean the server failed to handle a valid request.

Does this tool check the status of a live URL?

No. It is a reference list only. It does not send requests to any website.

Does the list include every status code?

It covers 59 standard and widely used codes. A few rare or joke codes, such as 418, are not included.

More to explore

Related Network & API

Browse all tools from the same category.

Showing 1-2 of 7