HTTP status codes

Client

Search and browse standard HTTP response codes from 1xx through 5xx—each entry includes a short developer-oriented meaning you can copy with one click.

Reference

?

Reason phrases are conventional; APIs may use custom text with the same numeric code. Copy uses the usual "CODE Phrase" form.

62 codes

Try examples

1xx — Informational

  • 100Continue

    Client may continue with the request body.

  • 101Switching Protocols

    Server agrees to change protocol (e.g. WebSocket upgrade).

  • 102Processing

    Request accepted; processing not finished (WebDAV).

  • 103Early Hints

    Hints to preload resources while the response is prepared.

2xx — Success

  • 200OK

    Request succeeded; response includes a representation.

  • 201Created

    Resource created; often returns Location and body.

  • 202Accepted

    Accepted for processing; completion may be asynchronous.

  • 203Non-Authoritative Information

    Payload from a transforming proxy, not origin.

  • 204No Content

    Success with no body (e.g. DELETE or empty update).

  • 205Reset Content

    Success; client should reset the document view.

  • 206Partial Content

    Range request satisfied; body is a sub-range.

  • 207Multi-Status

    Mixed success/failure across WebDAV sub-requests.

  • 208Already Reported

    DAV members already enumerated in a previous part.

  • 226IM Used

    Instance manipulations applied to the result (WebDAV).

3xx — Redirection

  • 300Multiple Choices

    Several representations; client or user should choose.

  • 301Moved Permanently

    URI changed permanently; update bookmarks and links.

  • 302Found

    Temporary redirect; method may change to GET in practice.

  • 303See Other

    GET the URI in Location to retrieve the result.

  • 304Not Modified

    Conditional GET: use cached copy.

  • 305Use Proxy

    Deprecated; must use proxy given by Location.

  • 307Temporary Redirect

    Temporary redirect; method and body preserved.

  • 308Permanent Redirect

    Permanent redirect; method and body preserved.

4xx — Client error

  • 400Bad Request

    Malformed syntax or invalid framing; fix the client.

  • 401Unauthorized

    Authentication required (WWW-Authenticate).

  • 402Payment Required

    Reserved for future payment flows.

  • 403Forbidden

    Authenticated but not allowed to access this resource.

  • 404Not Found

    No matching resource for the request URI.

  • 405Method Not Allowed

    HTTP method not supported; Allow header lists options.

  • 406Not Acceptable

    Cannot produce a representation matching Accept-*.

  • 407Proxy Authentication Required

    Authenticate with the proxy first.

  • 408Request Timeout

    Server gave up waiting for the full request.

  • 409Conflict

    State conflict with current resource (e.g. versioning).

  • 410Gone

    Resource was here but is permanently removed.

  • 411Length Required

    Content-Length or Transfer-Encoding required.

  • 412Precondition Failed

    If-* precondition evaluated to false.

  • 413Payload Too Large

    Request body exceeds server limits.

  • 414URI Too Long

    Request target exceeds server limits.

  • 415Unsupported Media Type

    Body format not supported for this method.

  • 416Range Not Satisfiable

    Requested range invalid or outside representation.

  • 417Expectation Failed

    Expect header could not be met.

  • 418I'm a teapot

    Easter egg from HTCPCP; sometimes used in tests.

  • 421Misdirected Request

    Request not intended for this origin (HTTP/2).

  • 422Unprocessable Content

    Semantics invalid though syntax may be OK (e.g. validation).

  • 423Locked

    Resource locked (WebDAV).

  • 424Failed Dependency

    Action failed because a dependency failed (WebDAV).

  • 425Too Early

    Replay risk; retry after TLS early-data is safe.

  • 426Upgrade Required

    Switch protocol (e.g. TLS); Upgrade header hints how.

  • 428Precondition Required

    Server requires conditional requests to avoid conflicts.

  • 429Too Many Requests

    Rate limited; Retry-After may apply.

  • 431Request Header Fields Too Large

    Headers exceed server limits.

  • 451Unavailable For Legal Reasons

    Withheld for legal or censorship reasons.

5xx — Server error

  • 500Internal Server Error

    Unexpected server failure; no more specific code fits.

  • 501Not Implemented

    Server does not support the request feature.

  • 502Bad Gateway

    Upstream server returned an invalid response.

  • 503Service Unavailable

    Temporarily overloaded or down; Retry-After may apply.

  • 504Gateway Timeout

    Upstream did not respond in time.

  • 505HTTP Version Not Supported

    Server refuses the HTTP version.

  • 506Variant Also Negotiates

    Negotiation misconfiguration on the server.

  • 507Insufficient Storage

    Cannot store the representation (WebDAV).

  • 508Loop Detected

    Depth loop detected in WebDAV processing.

  • 510Not Extended

    Further extensions required to fulfill the request.

  • 511Network Authentication Required

    Client must authenticate to gain network access.

Common use cases

  • Look up what 301 vs 308 means before changing redirect behavior in production.
  • Decode 4xx vs 5xx from API or CDN logs when pairing with User-Agent or Open Graph checks.
  • Paste a code from documentation into the filter to jump straight to its phrase and description.

Common mistakes to avoid

  • Treating the reason phrase as authoritative

    HTTP allows servers to vary wording; clients should rely on the numeric code and documented semantics.

  • Assuming 401 and 403 are interchangeable

    401 means authenticate; 403 means you are authenticated but still not allowed.

  • Ignoring Retry-After and rate limits

    429 and 503 often include Retry-After—back off instead of hammering the endpoint.

FAQ

Is this list sent to Toolcore?

No. Filtering and display run entirely in your browser.

Why might my API return text that does not match the phrase here?

Reason phrases are conventional; frameworks may customize the status line while keeping the same code.

Does this cover every registered HTTP code?

It covers the codes most developers hit in HTTP APIs and proxies; niche or obsolete codes may be omitted.

More tools

Related utilities you can open in another tab—mostly client-side.