Text & Regex

HTTP Status Code Lookup

Look up HTTP status codes with plain-language meanings and RFC references.

61 matches. Searching a number such as 404 shows exact and prefix matches; words match the status phrase, summary, and description.

  • 1001xx Informational

    Continue

    The server received the initial part of the request; the client should continue.

    The client may resume the request after the server signals it is ready for the remaining headers or body.

    Reference: RFC 9110

  • 1011xx Informational

    Switching Protocols

    The server is switching to a protocol the client requested.

    The upgrade handshake is complete and both sides start speaking the new protocol.

    Reference: RFC 9110

  • 1021xx Informational

    Processing

    The server accepted the request but has not finished processing it.

    A WebDAV intermediate response that tells the client the request is still in progress.

    Reference: RFC 4918

  • 1031xx Informational

    Early Hints

    The server sends hints about resources it will link soon.

    Lets a browser preload stylesheets or scripts while the final response is still being prepared.

    Reference: RFC 8297

  • 2002xx Success

    OK

    The request succeeded and the response carries the result.

    The meaning of success depends on the method: GET returns the body, POST returns the created or updated resource.

    Reference: RFC 9110

  • 2012xx Success

    Created

    The request succeeded and a new resource was created.

    The response usually includes a Location header pointing at the resource that was created.

    Reference: RFC 9110

  • 2022xx Success

    Accepted

    The request was accepted for processing but is not complete yet.

    Useful for asynchronous work: the server promises to act on the request later.

    Reference: RFC 9110

  • 2032xx Success

    Non-Authoritative Information

    The response metadata comes from a copy rather than the origin.

    A proxy may return modified headers while still indicating the body is derived from the origin.

    Reference: RFC 9110

  • 2042xx Success

    No Content

    The request succeeded but there is no body to return.

    Common after updates or deletes; the browser keeps the current document in view.

    Reference: RFC 9110

  • 2052xx Success

    Reset Content

    The request succeeded and the client should reset its form view.

    Tells the browser to clear the form the user just submitted.

    Reference: RFC 9110

  • 2062xx Success

    Partial Content

    The server is returning only a requested range of the resource.

    Used with range requests so a client can resume a download or fetch one chunk at a time.

    Reference: RFC 9110

  • 2072xx Success

    Multi-Status

    The response carries separate status entries for sub-operations.

    WebDAV uses this to report the outcome of several batched requests in one message.

    Reference: RFC 4918

  • 2082xx Success

    Already Reported

    The members of a WebDAV collection were already listed earlier.

    Avoids repeating resources that an earlier 207 response already reported.

    Reference: RFC 5842

  • 2262xx Success

    IM Used

    The server applied instance manipulations to the representation.

    Returned when delta encoding was used to transform the response body.

    Reference: RFC 3229

  • 3003xx Redirection

    Multiple Choices

    More than one representation is available for the resource.

    The response may include a list of alternatives so a client or user can pick one.

    Reference: RFC 9110

  • 3013xx Redirection

    Moved Permanently

    The resource has a new permanent location.

    Search engines update their stored URL, and future requests should use the new address.

    Reference: RFC 9110

  • 3023xx Redirection

    Found

    The resource temporarily lives at a different location.

    The client should keep using its original method for the follow-up request.

    Reference: RFC 9110

  • 3033xx Redirection

    See Other

    Fetch the result of the request at another location with GET.

    Lets a server redirect a completed POST to a results page the browser can load directly.

    Reference: RFC 9110

  • 3043xx Redirection

    Not Modified

    The cached copy the client sent is still valid.

    The server skips the body entirely, saving bandwidth on conditional requests.

    Reference: RFC 9110

  • 3073xx Redirection

    Temporary Redirect

    The resource is temporarily at a new location with the same method.

    Unlike a 302, a 307 guarantees the method and body are not changed during the redirect.

    Reference: RFC 9110

  • 3083xx Redirection

    Permanent Redirect

    The resource has permanently moved and the method stays the same.

    The permanent counterpart of 307 that also preserves the original request method.

    Reference: RFC 7538

  • 4004xx Client Error

    Bad Request

    The server could not understand the request.

    The request was malformed: bad syntax, missing headers, or invalid parameters.

    Reference: RFC 9110

  • 4014xx Client Error

    Unauthorized

    Authentication is required and has not succeeded.

    The response includes a WWW-Authenticate header describing how to authenticate.

    Reference: RFC 9110

  • 4024xx Client Error

    Payment Required

    Reserved for future use around payment requirements.

    Originally defined for digital cash schemes; rarely returned in practice.

    Reference: RFC 9110

  • 4034xx Client Error

    Forbidden

    The server understood the request but refuses to authorize it.

    Authentication will not help: the client is not allowed to perform this action.

    Reference: RFC 9110

  • 4044xx Client Error

    Not Found

    The requested resource does not exist on this server.

    The server is unwilling to say whether the resource exists or is simply hidden.

    Reference: RFC 9110

  • 4054xx Client Error

    Method Not Allowed

    The method is known but not supported for this resource.

    The response lists the allowed methods in an Allow header.

    Reference: RFC 9110

  • 4064xx Client Error

    Not Acceptable

    No representation matches the client's Accept headers.

    The server cannot produce a body that matches the requested content types.

    Reference: RFC 9110

  • 4074xx Client Error

    Proxy Authentication Required

    The proxy needs credentials before forwarding the request.

    Mirrors 401 but is issued by an intermediary proxy rather than the origin server.

    Reference: RFC 9110

  • 4084xx Client Error

    Request Timeout

    The server timed out waiting for the client to finish sending.

    The client may retry with the request completed before the deadline elapsed.

    Reference: RFC 9110

  • 4094xx Client Error

    Conflict

    The request conflicts with the current server state.

    Common in concurrent edits where the resource changed since the client read it.

    Reference: RFC 9110

  • 4104xx Client Error

    Gone

    The resource is gone permanently and will not return.

    Stronger than 404: it tells clients they should drop their stored reference.

    Reference: RFC 9110

  • 4114xx Client Error

    Length Required

    The server requires a declared Content-Length.

    Rejects requests that do not state their body size up front.

    Reference: RFC 9110

  • 4124xx Client Error

    Precondition Failed

    An If-Match or If-None-Match precondition failed.

    The resource state does not satisfy the condition the client attached to the request.

    Reference: RFC 9110

  • 4134xx Client Error

    Content Too Large

    The request body exceeds the server's size limit.

    The server refuses to process an oversized payload and may offer a Retry-After hint.

    Reference: RFC 9110

  • 4144xx Client Error

    URI Too Long

    The request URI is longer than the server accepts.

    Often caused by oversized query strings; switch long parameters to a request body.

    Reference: RFC 9110

  • 4154xx Client Error

    Unsupported Media Type

    The request body format is not supported for this resource.

    The Content-Type header does not match what the endpoint expects.

    Reference: RFC 9110

  • 4164xx Client Error

    Range Not Satisfiable

    The requested byte range lies outside the resource.

    The response should describe the current size of the resource.

    Reference: RFC 9110

  • 4174xx Client Error

    Expectation Failed

    The server cannot satisfy the Expect header value.

    The client asked for an expectation such as 100-continue that the server will not meet.

    Reference: RFC 9110

  • 4184xx Client Error

    I'm a teapot

    The server refuses to brew coffee because it is a teapot.

    A classic April Fools' response from HTCPCP that also documents playful API behavior.

    Reference: RFC 2324

  • 4214xx Client Error

    Misdirected Request

    The request was directed at a server that cannot answer it.

    Common with HTTP/2 when the connection does not match the requested authority.

    Reference: RFC 9110

  • 4224xx Client Error

    Unprocessable Content

    The syntax is valid but the request is semantically wrong.

    The body parses fine yet violates business rules such as missing required fields.

    Reference: RFC 9110

  • 4234xx Client Error

    Locked

    The resource is locked by another operation.

    WebDAV uses this to signal a resource held by a lock that the client has not acquired.

    Reference: RFC 4918

  • 4244xx Client Error

    Failed Dependency

    The request failed because a prior request failed.

    Used by batched WebDAV operations where one step's failure blocks the rest.

    Reference: RFC 4918

  • 4254xx Client Error

    Too Early

    The server is unwilling to risk processing a replayed request.

    Protects against replaying requests that were sent before a connection was verified.

    Reference: RFC 8470

  • 4264xx Client Error

    Upgrade Required

    The server refuses the protocol and requires an upgrade.

    The response carries an Upgrade header, such as switching to a newer HTTP version.

    Reference: RFC 9110

  • 4284xx Client Error

    Precondition Required

    The server requires conditional headers on this request.

    Stops clients from making blind changes without first checking the resource state.

    Reference: RFC 6585

  • 4294xx Client Error

    Too Many Requests

    The client sent more requests than the rate limit allows.

    A Retry-After header tells the client how long to wait before trying again.

    Reference: RFC 6585

  • 4314xx Client Error

    Request Header Fields Too Large

    The request headers are bigger than the server accepts.

    Often caused by oversized cookies; moving data into the body usually fixes it.

    Reference: RFC 6585

  • 4514xx Client Error

    Unavailable For Legal Reasons

    The resource is blocked for legal reasons.

    Signals censorship or court orders while still naming the legal basis for removal.

    Reference: RFC 7725

  • 5005xx Server Error

    Internal Server Error

    The server hit an unexpected condition it cannot handle.

    A generic failure meaning the server itself failed rather than the client's input.

    Reference: RFC 9110

  • 5015xx Server Error

    Not Implemented

    The server does not support the method used.

    Unlike 405, the server has no capability to perform this request at all.

    Reference: RFC 9110

  • 5025xx Server Error

    Bad Gateway

    An upstream server returned an invalid response.

    Issued by a proxy that received a broken or unacceptable reply from the origin.

    Reference: RFC 9110

  • 5035xx Server Error

    Service Unavailable

    The server is temporarily unable to handle the request.

    Usually overload or maintenance; a Retry-After header may suggest when to retry.

    Reference: RFC 9110

  • 5045xx Server Error

    Gateway Timeout

    An upstream server did not respond in time.

    The gateway gave up waiting for the origin and reports a timeout to the client.

    Reference: RFC 9110

  • 5055xx Server Error

    HTTP Version Not Supported

    The server does not support the HTTP version requested.

    The client should downgrade to a protocol version the server understands.

    Reference: RFC 9110

  • 5065xx Server Error

    Variant Also Negotiates

    Content negotiation was misconfigured and produced a loop.

    The chosen variant points back to the same negotiating resource, breaking the cycle.

    Reference: RFC 2295

  • 5075xx Server Error

    Insufficient Storage

    The server lacks the storage needed to complete the operation.

    A WebDAV error meaning the request cannot be stored right now.

    Reference: RFC 4918

  • 5085xx Server Error

    Loop Detected

    The server stopped an infinite loop in a WebDAV operation.

    An endless chain of references was detected while processing the request.

    Reference: RFC 5842

  • 5105xx Server Error

    Not Extended

    A required HTTP extension was not applied.

    The client asked for an extension the server will not use for this request.

    Reference: RFC 2774

  • 5115xx Server Error

    Network Authentication Required

    The client must authenticate to the network itself.

    Captive portals use this to force login before internet access is granted.

    Reference: RFC 6585

Lookups run locally in your browser against the built-in status reference. The query text is not uploaded, saved to browser storage, or included in analytics events.

Your data stays private

This tool runs directly in your browser. The content you enter is processed locally and is not sent to TechFixGen servers. No account or signup is required.

HTTP status code guide

What HTTP status codes are

Every HTTP response starts with a three-digit status code that summarizes the outcome of the request, grouped by class: 1xx informational, 2xx success, 3xx redirection, 4xx a problem with the request, and 5xx a problem on the server. Reading the code is the fastest way to understand why an endpoint behaved the way it did.

Search by number or by word

Type a number such as 404, 42, or 3 to see exact and prefix matches across the series. Or type a plain-language word such as redirect, timeout, teapot, or locked and the lookup matches the status phrase, summary, and description. Words are matched inside the text, so a partial term still surfaces related statuses.

Filter by category

The category chips narrow results to one class of status: informational, success, redirection, client error, or server error. Combining a category with a search term helps you find, for example, a timeout problem that belongs to the server rather than the client.

Meanings versus guarantees

Status codes describe intent. A 200 OK does not prove the payload is correct, and a 301 signal about a permanent move does not automatically update a client and its bookmarks. The reference explains what each code means and, for common cases, the header you should look for next, based on the RFC listed on each card.

Privacy

The reference ships inside this page and lookup runs entirely in your browser. The query text is not uploaded, saved to the URL, localStorage, or sessionStorage, and is not included in analytics events. Analytics events record only that a lookup or a category filter was used, never what you searched for.

Frequently asked questions

Which status codes are included?

The reference covers 60 widely used codes across all five classes, including informational codes such as 102 Processing and 103 Early Hints, features such as 418 I'm a teapot, and the full 4xx and 5xx series. Each entry includes the standard reason phrase, a short summary, a longer description, and the RFC that defines it.

Is a 200 OK proof that my request worked?

No. 200 means the request succeeded at the HTTP layer and the response carries a result, but many APIs return 200 with an error shape inside the body. Check the response body and your API's own error contract in addition to the status code.

Why does searching number 42 match 421 through 429?

The lookup treats numbers as prefixes: 42 returns every status whose code starts with those digits so you can scan a whole series. Type a complete code such as 422 to narrow to the single status.

How accurate are the meanings?

Phrases and descriptions follow the listed RFCs rather than folklore. Statuses such as 301 and 307, or 401 and 403, are easy to confuse; the descriptions call out the difference and the header the server should return. RFC text changes over time, so verify against the reference for the version you use.

Is my query uploaded or saved?

No. The lookup runs locally in your browser against a built-in reference. The query text is not sent to a service or to analytics, and is not saved in the URL, localStorage, or sessionStorage. Analytics events record that a lookup or filter happened, not what you searched for.

Can I look up codes outside this list?

The reference intentionally covers codes in active use and the classic ones developers meet daily. Registry-defined codes outside this list will not match; the word search still falls back to whatever text is in this page's built-in reference.