online

HTTP Status Codesonline

Reference guide for all HTTP status codes.

100

Continue

Server received request headers, client should proceed to send the body.

101

Switching Protocols

Server agrees to switch protocols per the client's Upgrade header.

200

OK

Request succeeded. The response body contains the result.

201

Created

Request succeeded and a new resource was created.

204

No Content

Request succeeded but no response body.

206

Partial Content

Partial resource returned (range requests).

301

Moved Permanently

Resource permanently moved to a new URL.

302

Found

Resource temporarily at a different URL.

304

Not Modified

Cached resource is still valid. Client should use cache.

307

Temporary Redirect

Redirect with same HTTP method.

308

Permanent Redirect

Permanent redirect preserving the HTTP method.

400

Bad Request

Server cannot process the request due to client error.

401

Unauthorized

Authentication required. Client must authenticate first.

403

Forbidden

Server understood request but refuses to authorize it.

404

Not Found

Resource not found at the given URL.

405

Method Not Allowed

HTTP method is not allowed for this resource.

408

Request Timeout

Server timed out waiting for request from client.

409

Conflict

Request conflicts with current state of the resource.

410

Gone

Resource permanently deleted and will not be available again.

413

Payload Too Large

Request body exceeds server's size limits.

414

URI Too Long

Request URI is too long for the server to process.

415

Unsupported Media Type

Request media type is not supported by the server.

422

Unprocessable Entity

Request is well-formed but contains semantic errors.

429

Too Many Requests

Client has sent too many requests (rate limiting).

500

Internal Server Error

Server encountered an unexpected condition.

501

Not Implemented

Server does not support the requested functionality.

502

Bad Gateway

Upstream server returned an invalid response.

503

Service Unavailable

Server temporarily unavailable (overloaded or down).

504

Gateway Timeout

Upstream server failed to respond in time.

How to use HTTP Status Codes

1

Enter or search a status code

Click the search bar at the top of the tool and type the HTTP status code number (e.g., 404, 500, 200). Alternatively, scroll through the categorized list organized by code ranges in the left sidebar.

2

Review the detailed status information

View the status code, official name, HTTP category, and plain-English meaning in the main results panel. Each entry displays the official RFC definition and common use cases.

3

Check related codes and solutions

Expand the 'Related Codes' section below to see similar status codes. Read the 'What It Means' and 'Common Causes' tabs to understand why this status code appears.

4

Copy or bookmark results

Click the 'Copy' button next to any code definition to copy to clipboard. Use the bookmark icon in the top-right corner to save frequently referenced codes to your browser.

Frequently Asked Questions

Related Tools