Tous les outils
TarifsNouveautés

Codes de statut HTTP

Outil SEONouveau

Consultez la signification de n'importe quel code de statut HTTP.

Cet outil s'exécute entièrement dans votre navigateur. Vos fichiers ne quittent jamais votre appareil — rien n'est envoyé.

Search status codes

Match by code, name or description. Everything runs privately in your browser.

All 48 codes

1xx Informational

100 · ContinueThe server received the request headers and the client should proceed to send the request body.
101 · Switching ProtocolsThe server is switching protocols as requested by the client via the Upgrade header.
102 · ProcessingThe server has received and is processing the request, but no response is available yet.
103 · Early HintsUsed to return preliminary headers, often to let the browser preload resources, before the final response.

2xx Success

200 · OKThe request succeeded. The meaning of success depends on the HTTP method used.
201 · CreatedThe request succeeded and a new resource was created as a result, usually after a POST or PUT.
202 · AcceptedThe request was accepted for processing, but the processing has not been completed yet.
203 · Non-Authoritative InformationThe returned metadata is from a local or third-party copy rather than the origin server.
204 · No ContentThe request succeeded but there is no content to send in the response body.
205 · Reset ContentThe request succeeded and the client should reset the document view that sent the request.
206 · Partial ContentThe server is delivering only part of the resource in response to a Range header, used for resumable downloads.

3xx Redirection

300 · Multiple ChoicesThe request has more than one possible response and the client may choose one of them.
301 · Moved PermanentlyThe resource has permanently moved to a new URL, which is given in the Location header.
302 · FoundThe resource temporarily resides at a different URL. Future requests should still use the original URL.
303 · See OtherThe client should fetch the resource at another URL using a GET request, often used after a form POST.
304 · Not ModifiedThe cached version of the resource is still valid, so the client can reuse it without a fresh download.
307 · Temporary RedirectThe resource is temporarily at a different URL and the same HTTP method must be reused for the redirect.
308 · Permanent RedirectThe resource has permanently moved and the same HTTP method must be reused for all future requests.

4xx Client Error

400 · Bad RequestThe server cannot process the request due to a client error such as malformed syntax or invalid parameters.
401 · UnauthorizedAuthentication is required and has either failed or not been provided for the requested resource.
402 · Payment RequiredReserved for future use, sometimes used by APIs to signal that payment or a higher plan is required.
403 · ForbiddenThe server understood the request but refuses to authorize it. Authenticating will not help.
404 · Not FoundThe server cannot find the requested resource. The URL may be broken or the resource may no longer exist.
405 · Method Not AllowedThe HTTP method used is known by the server but is not supported for the target resource.
406 · Not AcceptableThe server cannot produce a response matching the content types listed in the request's Accept headers.
408 · Request TimeoutThe server timed out waiting for the request because the client did not produce one in time.
409 · ConflictThe request conflicts with the current state of the resource, such as an edit conflict or duplicate entry.
410 · GoneThe requested resource is permanently gone and no forwarding address is known. Remove any links to it.
411 · Length RequiredThe server requires a Content-Length header, which was missing from the request.
413 · Payload Too LargeThe request body is larger than the server is willing or able to process.
414 · URI Too LongThe request URL is longer than the server is willing to interpret, often from too many query parameters.
415 · Unsupported Media TypeThe request body is in a media format that the server or resource does not support.
418 · I'm a TeapotAn April Fools' joke from RFC 2324: the server refuses to brew coffee because it is a teapot.
422 · Unprocessable EntityThe request was well formed but contains semantic errors that prevent the server from processing it.
425 · Too EarlyThe server is unwilling to process a request that might be replayed, used to mitigate replay attacks.
426 · Upgrade RequiredThe client should switch to a different protocol, given in the Upgrade header, to complete the request.
428 · Precondition RequiredThe server requires the request to be conditional to prevent lost updates from conflicting writes.
429 · Too Many RequestsThe client has sent too many requests in a given time and is being rate limited. Check the Retry-After header.
431 · Request Header Fields Too LargeThe server refuses the request because its header fields are too large, individually or in total.
451 · Unavailable For Legal ReasonsThe resource is unavailable due to legal demands, such as censorship or a takedown request.

5xx Server Error

500 · Internal Server ErrorThe server hit an unexpected condition that prevented it from fulfilling the request.
501 · Not ImplementedThe server does not support the functionality required to fulfil the request, such as an unknown method.
502 · Bad GatewayActing as a gateway or proxy, the server received an invalid response from the upstream server.
503 · Service UnavailableThe server is temporarily unable to handle the request, usually due to overload or maintenance.
504 · Gateway TimeoutActing as a gateway or proxy, the server did not get a timely response from the upstream server.
505 · HTTP Version Not SupportedThe server does not support the HTTP protocol version that was used in the request.
507 · Insufficient StorageThe server cannot store the representation needed to complete the request, often a WebDAV scenario.
511 · Network Authentication RequiredThe client must authenticate to gain network access, commonly seen on captive portal Wi-Fi networks.

Questions fréquentes

Comment rechercher un code de statut HTTP ?
Saisissez un numéro comme 404 ou 500 dans la recherche et le code correspondant apparaît instantanément, coloré selon sa classe. Vous pouvez aussi rechercher par nom (« not found ») ou par mots de la description (« rate limited », « redirect »). Cliquez sur une carte pour copier le code et son nom.
Ce que je recherche est-il transmis à un serveur ?
Non. C'est une référence statique qui fonctionne entièrement dans votre navigateur — vos recherches ne quittent jamais votre appareil et rien n'est envoyé ni enregistré. La liste complète des codes est incluse avec la page, elle fonctionne donc même hors ligne une fois chargée.
Que signifient les différentes classes de codes de statut ?
Le premier chiffre regroupe chaque réponse : 1xx est informatif, 2xx est un succès, 3xx est une redirection, 4xx est une erreur du client (quelque chose ne va pas dans la requête) et 5xx est une erreur du serveur. Les cartes sont regroupées et colorées par classe pour que vous puissiez parcourir la bonne plage d'un coup d'œil.