HTTP Status Codes Reference

Complete HTTP status code reference with explanations, examples, and when to use each code. Search by code or name. Free developer reference tool.

Showing 62 of 62 status codes

100

Continue

Server received request headers, client should proceed.

▼

101

Switching Protocols

Server is switching protocols as requested.

▼

102

Processing

Server is processing the request (WebDAV).

▼

103

Early Hints

Used to return some response headers before final response.

▼

200

Request succeeded.

▼

201

Created

Request succeeded and a new resource was created.

▼

202

Accepted

Request accepted but not yet processed.

▼

203

Non-Authoritative Information

Metadata is not from the origin server.

▼

204

No Content

Request succeeded but no content to return.

▼

205

Reset Content

Server asks client to reset the document view.

▼

206

Partial Content

Server is delivering part of the resource.

▼

207

Multi-Status

Multiple status codes for multiple operations (WebDAV).

▼

208

Already Reported

Members already enumerated (WebDAV).

▼

226

IM Used

Server has fulfilled a GET request with instance-manipulations.

▼

300

Multiple Choices

Request has more than one possible response.

▼

301

Moved Permanently

Resource has been permanently moved to a new URL.

▼

302

Found

Resource temporarily resides at a different URL.

▼

303

See Other

Response can be found at a different URL using GET.

▼

304

Not Modified

Resource has not been modified since last request.

▼

305

Use Proxy

Requested resource must be accessed through a proxy.

▼

307

Temporary Redirect

Resource temporarily at a different URL; method preserved.

▼

308

Permanent Redirect

Resource permanently at a different URL; method preserved.

▼

400

Bad Request

Server cannot process the request due to client error.

▼

401

Unauthorized

Authentication is required.

▼

402

Payment Required

Reserved for future use (digital payment systems).

▼

403

Forbidden

Client does not have access rights.

▼

404

Not Found

Server cannot find the requested resource.

▼

405

Method Not Allowed

Request method is not supported for the resource.

▼

406

Not Acceptable

No content matching the Accept headers.

▼

407

Proxy Authentication Required

Authentication with the proxy is required.

▼

408

Request Timeout

Server timed out waiting for the request.

▼

409

Conflict

Request conflicts with the current state of the server.

▼

410

Gone

Resource has been permanently deleted.

▼

411

Length Required

Content-Length header is required.

▼

412

Precondition Failed

Precondition in headers was not met.

▼

413

Payload Too Large

Request entity is too large.

▼

414

URI Too Long

Requested URI is too long.

▼

415

Unsupported Media Type

Media format of the request is not supported.

▼

416

Range Not Satisfiable

Range specified in headers cannot be fulfilled.

▼

417

Expectation Failed

Expect header cannot be met by the server.

▼

418

I'm a Teapot

Server refuses to brew coffee with a teapot.

▼

421

Misdirected Request

Request was directed to a wrong server.

▼

422

Unprocessable Entity

Request is well-formed but has semantic errors.

▼

423

Locked

Resource is locked (WebDAV).

▼

424

Failed Dependency

Request failed due to failure of a previous request (WebDAV).

▼

425

Too Early

Server is unwilling to process a request that might be replayed.

▼

426

Upgrade Required

Client should switch to a different protocol.

▼

428

Precondition Required

Origin server requires the request to be conditional.

▼

429

Too Many Requests

User has sent too many requests (rate limiting).

▼

431

Request Header Fields Too Large

Header fields are too large.

▼

451

Unavailable For Legal Reasons

Resource is unavailable due to legal demands.

▼

500

Internal Server Error

Server encountered an unexpected condition.

▼

501

Not Implemented

Server does not support the request method.

▼

502

Bad Gateway

Server got an invalid response from an upstream server.

▼

503

Service Unavailable

Server is not ready to handle the request.

▼

504

Gateway Timeout

Server acting as gateway did not get a timely response.

▼

505

HTTP Version Not Supported

HTTP version used in the request is not supported.

▼

506

Variant Also Negotiates

Server has an internal configuration error.

▼

507

Insufficient Storage

Server cannot store the representation (WebDAV).

▼

508

Loop Detected

Server detected an infinite loop (WebDAV).

▼

510

Not Extended

Further extensions to the request are required.

▼

511

Network Authentication Required

Client needs to authenticate to gain network access.

▼

Help Us Improve

Be the first to rate!

Quickly look up any HTTP status code to understand what it means and when to use it. This reference covers all 60+ codes from 1xx through 5xx with clear explanations and practical examples, perfect for developers debugging APIs or building web applications.

How it works

1Search by status code number or name in the search box
2View plain-English explanation and when to use each code
3Copy the code and description for quick reference
4Browse all codes organized by category (1xx–5xx)

Who uses this tool

✓Backend developers debugging API responses and error codes
✓Frontend developers understanding server responses in requests
✓DevOps engineers troubleshooting web server issues
✓QA testers verifying correct status codes in test scenarios
✓Students learning HTTP protocols and web communication

Frequently Asked Questions

How do I use HTTP Status Codes Reference?

Search by code number (e.g. 404) or name (e.g. 'not found'). Each entry explains what the code means and when to use it in your API.

Is HTTP Status Codes Reference free?

Yes, this reference tool on ToolPix is 100% free with no signup required.

What is the difference between 401 and 403?

401 Unauthorized means the client is not authenticated (no or invalid credentials). 403 Forbidden means the client is authenticated but lacks permission for the resource.

When should I use 422 vs 400?

400 Bad Request is for malformed syntax. 422 Unprocessable Entity is for well-formed requests that fail validation (e.g. missing required fields in JSON).

What HTTP codes should a REST API return?

200 OK, 201 Created, 204 No Content for success. 400, 401, 403, 404, 422 for client errors. 500, 503 for server errors.

Related Tools

CSS Minifier

Minify and compress CSS code. Remove comments, whitespa…

JWT Decoder

Decode and inspect JWT tokens. View header, payload, an…

Regex Tester

Test and debug regular expressions with real-time match…

Diff Checker

Compare two texts side by side. Highlight additions, de…

Cron Expression Generator

Build cron expressions visually with a point-and-click …