M
Momo Toolbox
Online Tools

HTTP Status Code Lookup - Momo Toolbox

HTTP Status Code Lookup

Lookup 60+ HTTP status codes

HTTP Status Code Lookup How to use

Type a code, name, or description keyword to filter results in real time. Click category chips to filter 1xx-5xx. Click any card to copy the code.

View full tutorial →
61 results
100

Continue

Server received request headers; client should send request body.

101

Switching Protocols

Server agrees to switch protocols, commonly used for WebSocket upgrade.

102

Processing

Server received the request but has not yet completed it (WebDAV).

103

Early Hints

Server hints the client to preload resources before the final response.

200

OK

Request succeeded. The most common status code for successful GET/POST.

201

Created

Request succeeded and a new resource was created, typical for POST/PUT.

202

Accepted

Request accepted but not yet processed, typical for async tasks.

203

Non-Authoritative Information

Returned information comes from a third party, not the origin server.

204

No Content

Request succeeded with no content returned, typical for DELETE/PUT.

205

Reset Content

Asks the client to reset the view (e.g., clear forms).

206

Partial Content

Server returns partial content, typical for Range requests (resume/video streaming).

207

Multi-Status

WebDAV extension; response body contains multiple independent statuses.

226

IM Used

Server fulfilled a GET request and applied instance manipulations.

300

Multiple Choices

Resource has multiple representations; client can pick one.

301

Moved Permanently

Resource moved permanently to a new URI; SEO juice transferred.

302

Found

Resource temporarily at another URI; future requests use the original URI.

303

See Other

Asks to GET another URI, typical for post-POST redirects.

304

Not Modified

Resource not modified; client can use cached version (conditional request).

305

Use Proxy

Deprecated; originally required access via a proxy.

307

Temporary Redirect

Like 302 but preserves the original method (POST stays POST).

308

Permanent Redirect

Like 301 but preserves the original request method.

400

Bad Request

Malformed request syntax; server cannot understand. Common for parameter errors.

401

Unauthorized

Authentication required. Response should include WWW-Authenticate header.

402

Payment Required

Reserved for future use; commonly repurposed for paywalls.

403

Forbidden

Server refused the request. Differs from 401: identity verified but no permission.

404

Not Found

Server cannot find the requested resource. The most common error code.

405

Method Not Allowed

Request method not allowed (e.g., POST on a read-only resource).

406

Not Acceptable

Resource cannot generate a format matching the Accept header.

407

Proxy Authentication Required

Client must authenticate with a proxy first.

408

Request Timeout

Client did not send a request within the server timeout.

409

Conflict

Request conflicts with current server state, common for concurrent updates.

410

Gone

Resource permanently removed; unlike 404 it indicates intentional deletion.

411

Length Required

Request must include a Content-Length header.

412

Precondition Failed

If-Match/If-Unmodified-Since precondition failed.

413

Payload Too Large

Request body exceeds the server size limit.

414

URI Too Long

Request URI exceeds the server length limit.

415

Unsupported Media Type

Request Content-Type is not supported by the server.

416

Range Not Satisfiable

Range request exceeds the resource size.

417

Expectation Failed

Expect header field could not be met.

418

I'm a Teapot

April Fools joke; server refuses to brew tea because it is a teapot.

421

Misdirected Request

Request sent to a server that cannot respond (HTTP/2).

422

Unprocessable Entity

Syntactically correct but semantically wrong, common for validation errors (WebDAV).

423

Locked

Resource is locked (WebDAV).

424

Failed Dependency

Prior request failed causing this one to fail (WebDAV).

425

Too Early

Server refuses to process within the TLS replay window.

426

Upgrade Required

Client must switch to a higher protocol like TLS/1.1.

428

Precondition Required

Server requires If-Match etc. to prevent lost updates.

429

Too Many Requests

Rate limit exceeded. Response should include Retry-After.

431

Request Header Fields Too Large

Header total size or a single field exceeds the limit.

451

Unavailable For Legal Reasons

Refused for legal reasons (e.g., copyright, government censorship).

500

Internal Server Error

Server encountered an unexpected error. The most common server error code.

501

Not Implemented

Server does not support the request method.

502

Bad Gateway

Gateway/proxy received an invalid response from upstream.

503

Service Unavailable

Server temporarily unavailable (overloaded or maintenance). Should include Retry-After.

504

Gateway Timeout

Gateway/proxy timed out waiting for upstream response.

505

HTTP Version Not Supported

Server does not support the HTTP version used in the request.

506

Variant Also Negotiates

Transparent content negotiation misconfiguration.

507

Insufficient Storage

Server lacks storage to complete the request (WebDAV).

508

Loop Detected

Infinite loop detected while processing the request (WebDAV).

510

Not Extended

Further extensions are required to fulfill the request.

511

Network Authentication Required

Network login required first (e.g., public WiFi captive portal).

HTTP Status Code Lookup - Use Cases

The HTTP Status Code Lookup is useful for frontend/backend development, API debugging, ops troubleshooting, and HTTP learning. When you see an unfamiliar status code in DevTools or curl output, this tool gives you bilingual explanations instantly.

Features

FAQ

Why are some codes unfamiliar to me?

This tool includes standard RFC 9110 codes plus WebDAV, HTTP/2, etc. extensions (e.g., 207, 421, 425), which are rare in real projects but included for completeness.

What is 418 I'm a Teapot?

An April Fools status code defined in RFC 2324 (HTCPCP), never actually used but a programmer culture meme.

How to memorize 1xx-5xx categories?

1 Informational, 2 Success, 3 Redirection, 4 Client Error, 5 Server Error.

Want more details? See the full HTTP Status Code Lookup Tutorial