HTTP Status Codes

Complete reference for all HTTP status codes with descriptions, use cases, and MDN links.

Runs in your browser — your data never leaves your device

100Continue

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

101Switching Protocols

The server is switching protocols as requested by the client via the Upgrade header.

102Processing

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

103Early Hints

Used to preload resources while the server prepares a response by sending Link headers early.

200OK

The request has succeeded. The meaning depends on the HTTP method used.

201Created

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

202Accepted

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

203Non-Authoritative Information

The response is a transformed proxy copy from a local or third-party copy.

204No Content

The server successfully processed the request, but there is no content to send back.

205Reset Content

The server has fulfilled the request and the user agent should reset the document view.

206Partial Content

The server is delivering only part of the resource due to a Range header in the request.

207Multi-Status

The message body contains an XML status with multiple status codes for sub-operations.

208Already Reported

The members of a DAV binding have already been enumerated in a preceding reply.

226IM Used

The server has fulfilled a GET request for the resource using Instance Manipulations.

300Multiple Choices

The request has more than one possible response. The user or agent should choose one.

301Moved Permanently

The resource has been permanently moved to a new URL. Clients should update bookmarks.

302Found

The resource temporarily resides under a different URL. The original URL should still be used.

303See Other

The response can be found under a different URL using a GET request.

304Not Modified

The resource has not been modified since the last request (caching mechanism).

305Use Proxy

The requested resource must be accessed through the given proxy.

307Temporary Redirect

The resource temporarily resides under a different URL. The method must not change.

308Permanent Redirect

The resource has been permanently moved to a new URL. The method must not change.

400Bad Request

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

401Unauthorized

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

402Payment Required

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

403Forbidden

The server understood the request but refuses to authorize it.

404Not Found

The server cannot find the requested resource. The most common error on the web.

405Method Not Allowed

The request HTTP method is not allowed for the target resource.

406Not Acceptable

The resource cannot generate content matching the Accept headers sent by the client.

407Proxy Authentication Required

The client must first authenticate itself with the proxy.

408Request Timeout

The server timed out waiting for the request from the client.

409Conflict

The request conflicts with the current state of the target resource.

410Gone

The resource has been permanently removed and will not be available again.

411Length Required

The server requires a Content-Length header in the request.

412Precondition Failed

One or more conditions in the request header fields evaluated to false.

413Content Too Large

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

414URI Too Long

The request URI is longer than the server is willing to interpret.

415Unsupported Media Type

The request payload format is not supported by the server for the target resource.

416Range Not Satisfiable

The byte range requested cannot be fulfilled.

417Expectation Failed

The Expect header in the request cannot be met by the server.

418I'm a Teapot

The server refuses to brew coffee because it is, permanently, a teapot. (RFC 2324)

421Misdirected Request

The request was directed at a server that cannot produce a response.

422Unprocessable Content

The request was well-formed but semantically erroneous (WebDAV / RFC 4918).

423Locked

The resource that is being accessed is locked (WebDAV).

424Failed Dependency

The request failed because it depended on another request that failed (WebDAV).

425Too Early

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

426Upgrade Required

The client should switch to a different protocol (e.g., TLS 1.3).

428Precondition Required

The origin server requires the request to be conditional (RFC 6585).

429Too Many Requests

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

431Request Header Fields Too Large

The server is unwilling to process the request because individual header fields are too large.

451Unavailable For Legal Reasons

The resource is blocked due to legal demands (censorship).

500Internal Server Error

The server encountered an unexpected condition that prevented it from fulfilling the request.

501Not Implemented

The server does not support the functionality required to fulfill the request.

502Bad Gateway

The server acting as a gateway received an invalid response from an upstream server.

503Service Unavailable

The server is currently unable to handle the request due to temporary overloading or maintenance.

504Gateway Timeout

The server acting as a gateway did not receive a timely response from the upstream server.

505HTTP Version Not Supported

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

506Variant Also Negotiates

The server has an internal configuration error in transparent content negotiation.

507Insufficient Storage

The server does not have enough storage to store the representation needed to complete the request (WebDAV).

508Loop Detected

The server detected an infinite loop while processing the request (WebDAV).

510Not Extended

The server requires further extensions to the request for it to be fulfilled.

511Network Authentication Required

The client needs to authenticate to gain network access (captive portal).

HTTP status code reference →

A dedicated page for every status code with its meaning, typical use and code examples.

Frequently Asked Questions

What are HTTP status codes?

HTTP status codes are three-digit numbers returned by a server in response to a client's HTTP request. They indicate whether the request was successful, needs redirection, or encountered an error.

What do the different categories mean?

1xx are informational responses, 2xx indicate success, 3xx are redirection responses, 4xx represent client errors, and 5xx indicate server errors.

How do I use this reference?

Search by code number, name, description, or use case. Use the category filter buttons to narrow down to a specific range (1xx-5xx). Click any code to expand and see full details with MDN links.

Can I link directly to a specific status code?

Yes, use the search to find the code and click on it. Each entry includes a link to the official MDN documentation for authoritative details.

Is this reference free?

Yes, ToolDock's HTTP status codes reference is completely free, requires no signup, and runs entirely in your browser.

Security Headers Checker

Analyze HTTP response headers for security.

TLS/SSL Certificate Checker

Check a domain's SSL/TLS certificate details.

DNS Lookup

Query DNS records for any domain using Google or Cloudflare.