1001Tools

HTTP Status Codes

Look up any HTTP status code. Search by number or name and filter by class, from 1xx Informational to 5xx Server Error.

Search

62 status codes

  • 100

    Continue

    The server received the request headers; the client should send the request body.

  • 101

    Switching Protocols

    The server agrees to switch protocols as requested via the Upgrade header (e.g. to WebSocket).

  • 102

    Processing

    WebDAV: the server has accepted the request but has not completed it yet.

  • 103

    Early Hints

    Lets the client start preloading resources (Link headers) while the server prepares the final response.

  • 200

    OK

    The request succeeded. The meaning depends on the method.

  • 201

    Created

    The request succeeded and a new resource was created, typically after POST or PUT.

  • 202

    Accepted

    The request was accepted for processing, but processing has not finished.

  • 203

    Non-Authoritative Information

    The returned metadata comes from a transforming proxy, not the origin server.

  • 204

    No Content

    The request succeeded and there is no content to return.

  • 205

    Reset Content

    The request succeeded; the client should reset the document view (e.g. clear a form).

  • 206

    Partial Content

    Only part of the resource is returned, in response to a Range header.

  • 207

    Multi-Status

    WebDAV: the body contains multiple status codes for multiple sub-requests.

  • 208

    Already Reported

    WebDAV: members of a binding were already listed earlier in the response.

  • 226

    IM Used

    The server fulfilled a GET request with instance manipulations applied (delta encoding).

  • 300

    Multiple Choices

    The request has more than one possible response; the client should choose one.

  • 301

    Moved Permanently

    The resource has a new permanent URL, given in the Location header.

  • 302

    Found

    The resource is temporarily at a different URL. Clients often switch to GET.

  • 303

    See Other

    The client should fetch the result at another URL using GET, often after a POST.

  • 304

    Not Modified

    The cached version is still valid; used with conditional requests.

  • 305

    Use Proxy

    Deprecated. The resource must be accessed through a proxy.

  • 307

    Temporary Redirect

    The resource is temporarily at another URL; the method and body must not change.

  • 308

    Permanent Redirect

    The resource is permanently at another URL; the method and body must not change.

  • 400

    Bad Request

    The server cannot process the request because of malformed syntax or invalid data.

  • 401

    Unauthorized

    Authentication is required and has failed or not been provided.

  • 402

    Payment Required

    Reserved for future use; sometimes used for paywalls.

  • 403

    Forbidden

    The client is authenticated but does not have permission to access the resource.

  • 404

    Not Found

    The server cannot find the requested resource.

  • 405

    Method Not Allowed

    The HTTP method is not supported for this resource. See the Allow header.

  • 406

    Not Acceptable

    No representation matches the Accept headers sent by the client.

  • 407

    Proxy Authentication Required

    The client must authenticate with the proxy first.

  • 408

    Request Timeout

    The server timed out waiting for the request.

  • 409

    Conflict

    The request conflicts with the current state of the resource (e.g. an edit conflict).

  • 410

    Gone

    The resource has been permanently removed and will not come back.

  • 411

    Length Required

    The request must include a Content-Length header.

  • 412

    Precondition Failed

    A precondition in the request headers (e.g. If-Match) evaluated to false.

  • 413

    Content Too Large

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

  • 414

    URI Too Long

    The request URL is longer than the server will interpret.

  • 415

    Unsupported Media Type

    The request body format (Content-Type) is not supported by the server.

  • 416

    Range Not Satisfiable

    The requested Range cannot be served for this resource.

  • 417

    Expectation Failed

    The server cannot meet the Expect request header.

  • 418

    I'm a teapot

    April Fools joke from RFC 2324: the server refuses to brew coffee because it is a teapot.

  • 421

    Misdirected Request

    The request was sent to a server that cannot produce a response for it.

  • 422

    Unprocessable Content

    The request is well-formed but contains semantic errors, such as failed validation.

  • 423

    Locked

    WebDAV: the resource being accessed is locked.

  • 424

    Failed Dependency

    WebDAV: the request failed because a request it depended on failed.

  • 425

    Too Early

    The server is unwilling to process a request that might be replayed (TLS early data).

  • 426

    Upgrade Required

    The client must switch to a different protocol, given in the Upgrade header.

  • 428

    Precondition Required

    The server requires the request to be conditional to prevent lost updates.

  • 429

    Too Many Requests

    The client sent too many requests in a given time (rate limiting). See Retry-After.

  • 431

    Request Header Fields Too Large

    The request headers are too large for the server to process.

  • 451

    Unavailable For Legal Reasons

    The resource cannot be served for legal reasons, such as government censorship.

  • 500

    Internal Server Error

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

  • 501

    Not Implemented

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

  • 502

    Bad Gateway

    A gateway or proxy received an invalid response from the upstream server.

  • 503

    Service Unavailable

    The server is temporarily unable to handle the request (overload or maintenance).

  • 504

    Gateway Timeout

    A gateway or proxy did not get a timely response from the upstream server.

  • 505

    HTTP Version Not Supported

    The HTTP version used in the request is not supported.

  • 506

    Variant Also Negotiates

    Server configuration error in transparent content negotiation.

  • 507

    Insufficient Storage

    WebDAV: the server cannot store the representation needed to complete the request.

  • 508

    Loop Detected

    WebDAV: the server detected an infinite loop.

  • 510

    Not Extended

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

  • 511

    Network Authentication Required

    The client must authenticate to gain network access (e.g. captive portals).

Related tools

  • IP Subnet Calculator

    Calculate IPv4 subnet details from CIDR or netmask: network and broadcast address, host range, usable hosts, wildcard mask and binary view.

  • JSON Formatter / Minifier

    Format, validate, and minify JSON instantly. Beautify JSON with configurable indentation or compress it to a single line.

  • JSON to CSV Converter

    Convert JSON arrays or objects to CSV instantly. Supports custom delimiters and optional header rows.

  • JSON to TypeScript

    Convert JSON into TypeScript interfaces or type aliases with nested types, optional fields, and union types