HTTP Status Codes Reference

Web & HTTP

Complete reference for HTTP 1xx–5xx status codes with descriptions and RFCs.

61 status codes

100

Continue

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

1xx Informational

101

Switching Protocols

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

1xx Informational

102

Processing

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

1xx Informational

103

Early Hints

Used to return some response headers before final HTTP message.

1xx Informational

200

Standard response for successful HTTP requests.

2xx Success

201

Created

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

2xx Success

202

Accepted

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

2xx Success

203

Non-Authoritative Information

The server is a transforming proxy that received a 200 OK but is returning a modified version.

2xx Success

204

No Content

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

2xx Success

205

Reset Content

The server successfully processed the request, asks that the requester reset its document view.

2xx Success

206

Partial Content

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

2xx Success

207

Multi-Status

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

2xx Success

208

Already Reported

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

2xx Success

226

IM Used

The server has fulfilled a request for the resource, and the response is a representation of the result.

2xx Success

300

Multiple Choices

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

3xx Redirection

301

Moved Permanently

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

3xx Redirection

302

Found

Tells the client to look at another URL. 302 has been superseded by 303 and 307.

3xx Redirection

303

See Other

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

3xx Redirection

304

Not Modified

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

3xx Redirection

307

Temporary Redirect

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

3xx Redirection

308

Permanent Redirect

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

3xx Redirection

400

Bad Request

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

4xx Client Error

401

Unauthorized

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

4xx Client Error

402

Payment Required

Reserved for future use.

4xx Client Error

403

Forbidden

The request was valid, but the server is refusing action.

4xx Client Error

404

Not Found

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

4xx Client Error

405

Method Not Allowed

A request method is not supported for the requested resource.

4xx Client Error

406

Not Acceptable

The requested resource is capable of generating only content not acceptable by the Accept headers.

4xx Client Error

407

Proxy Authentication Required

The client must first authenticate itself with the proxy.

4xx Client Error

408

Request Timeout

The server timed out waiting for the request.

4xx Client Error

409

Conflict

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

4xx Client Error

410

Gone

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

4xx Client Error

411

Length Required

The request did not specify the length of its content.

4xx Client Error

412

Precondition Failed

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

4xx Client Error

413

Payload Too Large

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

4xx Client Error

414

URI Too Long

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

4xx Client Error

415

Unsupported Media Type

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

4xx Client Error

416

Range Not Satisfiable

The client has asked for a portion of the file, but the server cannot supply that portion.

4xx Client Error

417

Expectation Failed

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

4xx Client Error

418

I'm a teapot

Any attempt to brew coffee with a teapot should result in the error code 418 (RFC 2324).

4xx Client Error

421

Misdirected Request

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

4xx Client Error

422

Unprocessable Content

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

4xx Client Error

423

Locked

The resource that is being accessed is locked.

4xx Client Error

424

Failed Dependency

The request failed because it depended on another request and that request failed.

4xx Client Error

425

Too Early

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

4xx Client Error

426

Upgrade Required

The client should switch to a different protocol.

4xx Client Error

428

Precondition Required

The origin server requires the request to be conditional.

4xx Client Error

429

Too Many Requests

The user has sent too many requests in a given amount of time (rate limiting).

4xx Client Error

431

Request Header Fields Too Large

The server is unwilling to process the request because either an individual header field is too large.

4xx Client Error

451

Unavailable For Legal Reasons

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

4xx Client Error

500

Internal Server Error

A generic error message, given when an unexpected condition was encountered.

5xx Server Error

501

Not Implemented

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

5xx Server Error

502

Bad Gateway

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

5xx Server Error

503

Service Unavailable

The server cannot handle the request (because it is overloaded or down for maintenance).

5xx Server Error

504

Gateway Timeout

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

5xx Server Error

505

HTTP Version Not Supported

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

5xx Server Error

506

Variant Also Negotiates

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

5xx Server Error

507

Insufficient Storage

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

5xx Server Error

508

Loop Detected

The server detected an infinite loop while processing the request.

5xx Server Error

510

Not Extended

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

5xx Server Error

511

Network Authentication Required

The client needs to authenticate to gain network access.

5xx Server Error

#http status#http codes#status code reference#rest api codes

About HTTP Status Codes Reference

Complete reference for HTTP 1xx–5xx status codes with descriptions and RFCs. HTTP Status Codes Reference runs entirely in your browser — no installation, no uploads, and no data ever leaves your device.

Common use cases: look up unfamiliar status codes during api development; reference correct codes when designing api responses; teach http semantics to junior developers. Whether you are debugging, prototyping, or building production code, having a fast and private tool for this task saves time compared to writing one-off scripts or using an online tool that logs your data.

Like every tool in Catalyst, this one is free forever, requires no login, and is safe to use with confidential data. All processing happens client-side via native browser APIs.

How to use HTTP Status Codes Reference

1
Open the tool
Open HTTP Status Codes Reference directly — no signup or installation required. The interactive interface loads instantly.
2
Paste or enter your input
Drop your data into the input area. The tool validates and processes your input live as you type or paste.
3
Review the result
The output updates instantly. If the tool has configuration options, adjust them and watch the result update.
4
Copy or download
Use the copy button to send the result to your clipboard. Nothing is saved between page loads, so closing the tab discards everything.

Frequently asked questions

Is any data sent to a server?

No. The tool runs entirely in your browser using native JavaScript and Web APIs. Nothing you paste or upload is transmitted, logged, or stored. You can verify this by disconnecting your network and seeing the tool continue to work.

Is this tool free to use?

Yes. It's completely free with no login, signup, API key, or usage limits. Catalyst is funded by ads and will remain free forever.

Does it work offline?

Once the page has loaded, yes. All processing happens locally in your browser, so you can use the tool on airplanes, trains, or in air-gapped environments.