Ontoom

HTTP status codes

Simple list of standard HTTP statuses — 1xx to 5xx. Search by code or name.

61 codes

  • 100

    Continue

    1xx

    Server received the headers and is ready for the request body.

  • 101

    Switching Protocols

    1xx

    Server agreed to switch protocols (e.g. WebSocket).

  • 102

    Processing

    1xx

    Server is still processing — prevents timeouts on long operations.

  • 103

    Early Hints

    1xx

    Hints the browser to preload resources while the full response is prepared.

  • 200

    OK

    2xx

    Request succeeded. The code you want to see.

  • 201

    Created

    2xx

    Resource created (common after POST/PUT).

  • 202

    Accepted

    2xx

    Accepted but not yet processed (async).

  • 203

    Non-Authoritative Information

    2xx

    Success, but a proxy modified the response.

  • 204

    No Content

    2xx

    Success with no response body (e.g. delete).

  • 205

    Reset Content

    2xx

    Success — client should reset the document view/form.

  • 206

    Partial Content

    2xx

    Partial content (Range) — downloads and streaming.

  • 207

    Multi-Status

    2xx

    Multiple statuses in one response (WebDAV).

  • 208

    Already Reported

    2xx

    Already reported in Multi-Status (avoids DAV duplicates).

  • 226

    IM Used

    2xx

    GET with instance manipulations applied.

  • 300

    Multiple Choices

    3xx

    Multiple options — client needs to choose one.

  • 301

    Moved Permanently

    3xx

    URL permanently moved (good for SEO).

  • 302

    Found

    3xx

    Temporary redirect. Keep using the original URL later.

  • 303

    See Other

    3xx

    See another resource via GET (e.g. after POST).

  • 304

    Not Modified

    3xx

    Not modified — use the cache. Saves bandwidth.

  • 307

    Temporary Redirect

    3xx

    Temporary redirect keeping the same HTTP method.

  • 308

    Permanent Redirect

    3xx

    Permanent redirect keeping the same HTTP method.

  • 400

    Bad Request

    4xx

    Invalid request (syntax, parameters, etc.).

  • 401

    Unauthorized

    4xx

    Missing or invalid authentication. Sign in.

  • 402

    Payment Required

    4xx

    Reserved for payment systems — rarely used.

  • 403

    Forbidden

    4xx

    No permission. Re-auth usually will not help.

  • 404

    Not Found

    4xx

    Resource not found. Broken link or wrong URL.

  • 405

    Method Not Allowed

    4xx

    HTTP method not allowed for this resource.

  • 406

    Not Acceptable

    4xx

    No content matches the Accept headers.

  • 407

    Proxy Authentication Required

    4xx

    Authenticate with the proxy (not the origin).

  • 408

    Request Timeout

    4xx

    Server did not receive the full request in time.

  • 409

    Conflict

    4xx

    Conflict with the current resource state.

  • 410

    Gone

    4xx

    Resource permanently removed.

  • 411

    Length Required

    4xx

    Content-Length header is required.

  • 412

    Precondition Failed

    4xx

    Request preconditions were not met.

  • 413

    Payload Too Large

    4xx

    Request payload is too large.

  • 414

    URI Too Long

    4xx

    URI is longer than the server accepts.

  • 415

    Unsupported Media Type

    4xx

    Unsupported media type.

  • 416

    Range Not Satisfiable

    4xx

    Requested range is invalid or outside the resource.

  • 417

    Expectation Failed

    4xx

    Expect header could not be satisfied.

  • 418

    I'm a Teapot

    4xx

    Easter egg (April Fools). Server is a teapot.

  • 421

    Misdirected Request

    4xx

    Request was sent to the wrong server.

  • 422

    Unprocessable Entity

    4xx

    Syntax OK, but semantic/validation errors.

  • 423

    Locked

    4xx

    Resource is locked (WebDAV).

  • 424

    Failed Dependency

    4xx

    Failed because a previous dependency failed.

  • 425

    Too Early

    4xx

    Server refuses to process (replay risk).

  • 426

    Upgrade Required

    4xx

    Client must switch protocols (Upgrade).

  • 428

    Precondition Required

    4xx

    Server requires a conditional request.

  • 429

    Too Many Requests

    4xx

    Rate limited — too many requests in a short time.

  • 431

    Request Header Fields Too Large

    4xx

    Request headers are too large.

  • 451

    Unavailable For Legal Reasons

    4xx

    Unavailable for legal reasons.

  • 500

    Internal Server Error

    5xx

    Generic server error. Hosting-side problem.

  • 501

    Not Implemented

    5xx

    Functionality not implemented by the server.

  • 502

    Bad Gateway

    5xx

    Gateway/proxy got an invalid upstream response.

  • 503

    Service Unavailable

    5xx

    Service unavailable (maintenance or overload).

  • 504

    Gateway Timeout

    5xx

    Gateway/proxy timed out waiting for upstream.

  • 505

    HTTP Version Not Supported

    5xx

    HTTP version used in the request is not supported.

  • 506

    Variant Also Negotiates

    5xx

    Content negotiation configuration error.

  • 507

    Insufficient Storage

    5xx

    Not enough storage on the server.

  • 508

    Loop Detected

    5xx

    Infinite loop detected — operation stopped.

  • 510

    Not Extended

    5xx

    Further extensions are required.

  • 511

    Network Authentication Required

    5xx

    Network authentication required (e.g. captive portal).

Important: Quick reference for debugging and SEO. Not a replacement for IANA/RFC docs.

What this tool does

This page is a reference for the HTTP status codes it lists, from the 1xx range through 5xx. You search by number or by name and filter by class. It is not a server: it does not return those statuses for a request of yours, and it does not replace the IANA registry or RFC 9110.

Each row shows the code, the English name, and a short line about what it means in API and page work. To see the status your call actually received, use the cURL runner or your service log. A JSON body from that response belongs in the JSON formatter.

How to use it

  1. Type the number or part of the name, for example 404 or Not Found.
  2. Or pick a range: 1xx, 2xx, 3xx, 4xx, or 5xx.
  3. Read the sentence next to the code. It describes the common case, not every use the specification allows.
  4. Go back to your HTTP client with the right code: permanent or temporary, authentication or permission, rate limit or server error.

What each range usually means

  • 1xx is informational. 100 Continue means the server accepted the headers and expects the body. 101 Switching Protocols shows up when moving to WebSocket.
  • 2xx is success. 200 OK is the ordinary response. 201 Created means a resource was created.
  • 3xx is redirection. 301 Moved Permanently changes the URL for good. 302 Found is temporary. 304 Not Modified tells the client to use the cache. 307 and 308 repeat temporary and permanent while keeping the HTTP method.
  • 4xx is a problem in the request. 400 Bad Request is invalid syntax or parameters. 401 Unauthorized asks for authentication. 403 Forbidden is missing permission, and signing in again usually does not help. 404 Not Found means the resource is absent. 429 Too Many Requests is a rate limit.
  • 5xx is a problem on the server. 500 Internal Server Error is generic. 502 Bad Gateway is an invalid upstream response. 503 Service Unavailable is maintenance or overload.

Example

Search for 404. The row says the resource was not found: a broken link or a wrong URL. That is different from 401, where authentication is missing, and from 403, where the identity may be correct and permission is still denied.

Search for 301 and compare it with 302. 301 is a permanent URL change, the case where a client and an index may store the new target. 302 asks you to keep using the original URL later. If the method must be preserved, the list separates 307 (temporary) and 308 (permanent). None of these codes is produced by this page: it only explains the number you already saw in cURL or in the browser.

Frequently asked questions

Does the page respond with the status I search for?
No. It only lists and describes the codes. To observe the status of a URL, call that URL with the HTTP client you already use.
Are 401 and 403 the same?
No. 401 is missing or invalid authentication. 403 is missing permission: signing in again usually does not unlock the resource.
When do I use 301 instead of 302?
Use 301 when the URL has moved for good and the new target may be remembered. Use 302 when the detour is temporary and the original URL still stands.
Is 429 a server error?
No. 429 is a 4xx: the client exceeded the request limit. 500, 502, and 503 are the codes that mean failure or unavailability on the server side.
Is this list complete against IANA?
No. It is a short reference of codes that show up in debugging. A code missing here can still exist in the specification; do not invent its meaning from the neighboring number.

Written by Orlando Alves · reviewed on · Editorial policy

See also