Handytool
DesenvolvedorGrátisRoda localmente

Búsqueda de código de estado HTTP

Busca cualquier código de estado HTTP — 1xx a 5xx — con una descripción en inglés simple.

Classe
  • 100Continue

    Server received the request headers; client should send the body.

  • 101Switching Protocols

    The server is switching protocols as requested by the client.

  • 102Processing

    Request received but not yet processed (WebDAV).

  • 103Early Hints

    Used to return some response headers before final HTTP message.

  • 200OK

    Standard success response.

  • 201Created

    Request succeeded and a new resource was created.

  • 202Accepted

    Request accepted for processing but not completed.

  • 203Non-Authoritative Information

    Returned metadata is from a third-party copy.

  • 204No Content

    Request succeeded but no content is returned.

  • 205Reset Content

    Request succeeded; client should reset the document view.

  • 206Partial Content

    Range request succeeded; partial content returned.

  • 207Multi-Status

    Body contains multiple statuses (WebDAV).

  • 208Already Reported

    Members of a DAV binding already enumerated.

  • 226IM Used

    Server fulfilled a GET request and the response is the result of one or more instance-manipulations.

  • 300Multiple Choices

    Request has more than one possible response.

  • 301Moved Permanently

    Resource moved to a new permanent URL.

  • 302Found

    Resource is temporarily at a different URL.

  • 303See Other

    Client should follow the response to a new URL with GET.

  • 304Not Modified

    Cached version is still valid; no body returned.

  • 307Temporary Redirect

    Same method should be used at the new URL.

  • 308Permanent Redirect

    Same as 301 but the request method must not change.

  • 400Bad Request

    Server cannot or will not process due to a client error.

  • 401Unauthorized

    Authentication required and has failed or not been provided.

  • 402Payment Required

    Reserved for future use, sometimes used for paywalls.

  • 403Forbidden

    Server understood but refuses to authorize.

  • 404Not Found

    The requested resource could not be found.

  • 405Method Not Allowed

    Request method is known but not supported by the resource.

  • 406Not Acceptable

    Resource cannot produce content matching the Accept headers.

  • 407Proxy Authentication Required

    Client must authenticate with the proxy.

  • 408Request Timeout

    Server timed out waiting for the request.

  • 409Conflict

    Request conflicts with the current state of the resource.

  • 410Gone

    Resource is no longer available and will not be available again.

  • 411Length Required

    Content-Length header is required.

  • 412Precondition Failed

    A precondition in the request headers was not met.

  • 413Payload Too Large

    Request entity is larger than the server is willing to process.

  • 414URI Too Long

    URI is longer than the server is willing to interpret.

  • 415Unsupported Media Type

    Media format of the request is not supported.

  • 416Range Not Satisfiable

    Requested range cannot be served.

  • 417Expectation Failed

    Expectation in Expect header could not be met.

  • 418I'm a teapot

    Server refuses to brew coffee because it is, permanently, a teapot.

  • 421Misdirected Request

    Request was directed to a server unable to produce a response.

  • 422Unprocessable Entity

    Request was well-formed but had semantic errors.

  • 423Locked

    Resource is locked (WebDAV).

  • 424Failed Dependency

    Request failed because of a previous failed request (WebDAV).

  • 425Too Early

    Server unwilling to risk processing a replay-vulnerable request.

  • 426Upgrade Required

    Client must upgrade to a different protocol.

  • 428Precondition Required

    Server requires the request to be conditional.

  • 429Too Many Requests

    Client has sent too many requests in a given amount of time.

  • 431Request Header Fields Too Large

    Headers are too large for the server to process.

  • 451Unavailable For Legal Reasons

    Resource cannot be served for legal reasons.

  • 500Internal Server Error

    Generic server error response.

  • 501Not Implemented

    Server does not support the request method.

  • 502Bad Gateway

    Server received an invalid response from an upstream server.

  • 503Service Unavailable

    Server is overloaded or down for maintenance.

  • 504Gateway Timeout

    Upstream server did not respond in time.

  • 505HTTP Version Not Supported

    HTTP version in the request is not supported.

  • 506Variant Also Negotiates

    Internal configuration error in transparent content negotiation.

  • 507Insufficient Storage

    Server is unable to store the representation (WebDAV).

  • 508Loop Detected

    Server detected an infinite loop while processing (WebDAV).

  • 510Not Extended

    Further extensions to the request are required.

  • 511Network Authentication Required

    Client needs to authenticate to gain network access.

Obtido do RFC 9110 e do registro IANA de status HTTP.

Sobre Búsqueda de código de estado HTTP

La búsqueda de código de estado HTTP de Handytool es una referencia rápida para cada estado HTTP desde 100 Continue hasta 511 Network Authentication Required. Busca por código (404), nombre (Not Found) o fragmento de la descripción; filtra por clase (1xx informativo, 2xx éxito, 3xx redirección, 4xx error de cliente, 5xx error de servidor). Obtenida de RFC 9110 y el registro IANA HTTP, incluyendo WebDAV y otras extensiones que verás en respuestas reales de API.

Recursos de Búsqueda de código de estado HTTP

  • 01

    Busca por código o significado

    Escribe un código, un nombre o una frase de la descripción — la lista se filtra instantáneamente. Útil cuando recuerdas que 422 significa "algo semántico" pero no puedes recordar el nombre exacto.

  • 02

    Filtro de clase

    Estrecha la lista a una única clase — 4xx cuando depuras un error de cliente, 5xx cuando persigues un bug de servidor, 3xx cuando desenredas una cadena de redirección.

  • 03

    Explicaciones en inglés simple

    Cada entrada tiene un resumen de una oración dirigido a desarrolladores — qué código realmente significa en la práctica, no solo la redacción formal de RFC.

Perguntas frequentes sobre Búsqueda de código de estado HTTP

¿Cuál es la diferencia entre 401 y 403?
401 Unauthorized significa que la solicitud carece de autenticación válida — inicia sesión y reintenta. 403 Forbidden significa que estás autenticado pero no se te permite acceder al recurso — las credenciales no ayudarán.
¿Cuándo debo devolver 422 vs 400?
400 Bad Request es para sintaxis mal formada (JSON roto, campo requerido faltante). 422 Unprocessable Entity es para solicitudes sintácticamente válidas que fallan en la validación comercial (correo electrónico ya existe, la edad debe ser ≥ 18).
¿Es 418 I'm a teapot un código de estado real?
Sí — definido como una broma del Día de Inocentes en RFC 2324 (1998) y reafirmado en RFC 7168. No es usado por HTTP en sí pero aparece en el registro IANA, y un puñado de servicios lo devuelven como un huevo de pascua.
¿Qué sucede después de códigos 5xx por encima de 511?
Los códigos por encima de 511 no están asignados en el registro IANA. Puedes ver códigos 5xx personalizados de plataformas específicas (Cloudflare usa 520-527 para problemas ascendentes), pero son extensiones específicas del proveedor, no HTTP estándar.

Ferramentas relacionadas

Desenvolvedor →

Explore outras ferramentas

Todas as ferramentas →