HTTP Status Code Reference

Searchable reference of all HTTP status codes with descriptions and use cases.

HTTP Status Code Reference

Showing 62 of 62 results

Code	Name	Description
100	Continue	Server has received request headers; client should proceed to send the body.
101	Switching Protocols	Server is switching protocols as requested by the client (e.g., HTTP → WebSocket).
102	Processing	(WebDAV) Server has received and is processing the request, but no response is available yet.
103	Early Hints	Used with the Link header to allow preloading resources while the server prepares a final response.
200	OK	Standard success response for GET, POST, PUT, DELETE, etc.
201	Created	Request succeeded and a new resource was created. Response includes a Location header.
202	Accepted	Request accepted for processing, but processing is not yet complete (async operations).
203	Non-Authoritative Information	Returned metadata is from a transforming proxy, not necessarily the origin server.
204	No Content	Request succeeded; response has no body. Common for DELETE and PUT that return no data.
205	Reset Content	Request succeeded; client should reset the document/form that caused the request.
206	Partial Content	Partial GET fulfilled (Range request). Used for resumable downloads and video streaming.
207	Multi-Status	(WebDAV) Response body contains XML with status for multiple sub-requests.
208	Already Reported	(WebDAV) Members of a DAV binding have already been enumerated in a previous reply.
226	IM Used	Server fulfilled a GET request and the response is a result of instance-manipulations.
300	Multiple Choices	Multiple possible responses; user or user agent should choose one.
301	Moved Permanently	Resource has permanently moved to a new URL. Browsers and search engines update their references.
302	Found	Resource temporarily at a different URL. Browser follows the redirect but keeps the original URL.
303	See Other	Response to a POST/PUT/DELETE; client should GET the resource at the given URL.
304	Not Modified	Conditional GET: resource unchanged since last request. Client should use its cached copy.
305	Use Proxy	(Deprecated) Requested resource must be accessed through a proxy.
307	Temporary Redirect	Temporary redirect that preserves the HTTP method (unlike 302, which may change POST → GET).
308	Permanent Redirect	Permanent redirect that preserves the HTTP method (like 301, but method must not change).
400	Bad Request	Malformed request syntax, invalid framing, or deceptive request routing.
401	Unauthorized	Authentication required. Client must authenticate itself to get the requested resource.
402	Payment Required	Reserved for future use. Occasionally used by APIs for paywall errors.
403	Forbidden	Server understands the request but refuses it. Authenticated but lacking permission.
404	Not Found	Resource not found. Most common HTTP error; URL may be wrong or resource deleted.
405	Method Not Allowed	HTTP method not supported for this resource (e.g., POST to a read-only endpoint).
406	Not Acceptable	Server cannot produce a response matching the Accept headers sent by the client.
407	Proxy Authentication Required	Client must authenticate with a proxy before this request can be served.
408	Request Timeout	Server timed out waiting for the client to send a complete request.
409	Conflict	Request conflicts with the current state of the resource (e.g., edit conflict, duplicate entry).
410	Gone	Resource permanently deleted and will not be restored. Unlike 404, indicates intentional removal.
411	Length Required	Server requires a Content-Length header but it was not provided.
412	Precondition Failed	Conditional request precondition (If-Match, If-None-Match, etc.) evaluated to false.
413	Content Too Large	Request body exceeds the server's size limit (previously "Request Entity Too Large").
414	URI Too Long	URI provided was too long for the server to process.
415	Unsupported Media Type	Media type of the request body is not supported (check Content-Type header).
416	Range Not Satisfiable	Range specified in Range header cannot be fulfilled (e.g., beyond end of file).
417	Expectation Failed	Server cannot meet the requirements of the Expect header in the request.
418	I'm a Teapot	April Fools joke (RFC 2324). Server refuses to brew coffee because it is a teapot.
421	Misdirected Request	Request was directed at a server unable to produce a response for this host/scheme combination.
422	Unprocessable Content	(WebDAV / REST APIs) Request is well-formed but has semantic errors (invalid field values, etc.).
423	Locked	(WebDAV) Resource is locked.
424	Failed Dependency	(WebDAV) Request failed because a previous request it depended on failed.
425	Too Early	Server unwilling to risk processing a request that might be replayed (TLS early data).
426	Upgrade Required	Client should switch to the protocol specified in the Upgrade header.
428	Precondition Required	Origin server requires the request to be conditional (to prevent lost-update problems).
429	Too Many Requests	Client has sent too many requests in a given time (rate limiting). Check Retry-After header.
431	Request Header Fields Too Large	Server unwilling to process the request because header fields are too large.
451	Unavailable For Legal Reasons	Resource has been blocked for legal reasons (e.g., government censorship, DMCA takedown).
500	Internal Server Error	Generic server-side error. Something went wrong on the server. Check server logs.
501	Not Implemented	Server does not recognise or support the request method.
502	Bad Gateway	Server acting as a gateway received an invalid response from an upstream server.
503	Service Unavailable	Server temporarily unable to handle requests (overloaded, in maintenance). Check Retry-After.
504	Gateway Timeout	Server acting as gateway timed out waiting for a response from an upstream server.
505	HTTP Version Not Supported	Server does not support the HTTP version used in the request.
506	Variant Also Negotiates	Transparent content negotiation results in a circular reference (server misconfiguration).
507	Insufficient Storage	(WebDAV) Server cannot store the representation needed to complete the request.
508	Loop Detected	(WebDAV) Server detected an infinite loop while processing the request.
510	Not Extended	Further extensions to the request are required before the server can fulfil it.
511	Network Authentication Required	Client needs to authenticate to gain network access (e.g., captive portal).

Code100

NameContinue

DescriptionServer has received request headers; client should proceed to send the body.

Code101

NameSwitching Protocols

DescriptionServer is switching protocols as requested by the client (e.g., HTTP → WebSocket).

Code102

NameProcessing

Description(WebDAV) Server has received and is processing the request, but no response is available yet.

Code103

NameEarly Hints

DescriptionUsed with the Link header to allow preloading resources while the server prepares a final response.

Code200

NameOK

DescriptionStandard success response for GET, POST, PUT, DELETE, etc.

Code201

NameCreated

DescriptionRequest succeeded and a new resource was created. Response includes a Location header.

Code202

NameAccepted

DescriptionRequest accepted for processing, but processing is not yet complete (async operations).

Code203

NameNon-Authoritative Information

DescriptionReturned metadata is from a transforming proxy, not necessarily the origin server.

Code204

NameNo Content

DescriptionRequest succeeded; response has no body. Common for DELETE and PUT that return no data.

Code205

NameReset Content

DescriptionRequest succeeded; client should reset the document/form that caused the request.

Code206

NamePartial Content

DescriptionPartial GET fulfilled (Range request). Used for resumable downloads and video streaming.

Code207

NameMulti-Status

Description(WebDAV) Response body contains XML with status for multiple sub-requests.

Code208

NameAlready Reported

Description(WebDAV) Members of a DAV binding have already been enumerated in a previous reply.

Code226

NameIM Used

DescriptionServer fulfilled a GET request and the response is a result of instance-manipulations.

Code300

NameMultiple Choices

DescriptionMultiple possible responses; user or user agent should choose one.

Code301

NameMoved Permanently

DescriptionResource has permanently moved to a new URL. Browsers and search engines update their references.

Code302

NameFound

DescriptionResource temporarily at a different URL. Browser follows the redirect but keeps the original URL.

Code303

NameSee Other

DescriptionResponse to a POST/PUT/DELETE; client should GET the resource at the given URL.

Code304

NameNot Modified

DescriptionConditional GET: resource unchanged since last request. Client should use its cached copy.

Code305

NameUse Proxy

Description(Deprecated) Requested resource must be accessed through a proxy.

Code307

NameTemporary Redirect

DescriptionTemporary redirect that preserves the HTTP method (unlike 302, which may change POST → GET).

Code308

NamePermanent Redirect

DescriptionPermanent redirect that preserves the HTTP method (like 301, but method must not change).

Code400

NameBad Request

DescriptionMalformed request syntax, invalid framing, or deceptive request routing.

Code401

NameUnauthorized

DescriptionAuthentication required. Client must authenticate itself to get the requested resource.

Code402

NamePayment Required

DescriptionReserved for future use. Occasionally used by APIs for paywall errors.

Code403

NameForbidden

DescriptionServer understands the request but refuses it. Authenticated but lacking permission.

Code404

NameNot Found

DescriptionResource not found. Most common HTTP error; URL may be wrong or resource deleted.

Code405

NameMethod Not Allowed

DescriptionHTTP method not supported for this resource (e.g., POST to a read-only endpoint).

Code406

NameNot Acceptable

DescriptionServer cannot produce a response matching the Accept headers sent by the client.

Code407

NameProxy Authentication Required

DescriptionClient must authenticate with a proxy before this request can be served.

Code408

NameRequest Timeout

DescriptionServer timed out waiting for the client to send a complete request.

Code409

NameConflict

DescriptionRequest conflicts with the current state of the resource (e.g., edit conflict, duplicate entry).

Code410

NameGone

DescriptionResource permanently deleted and will not be restored. Unlike 404, indicates intentional removal.

Code411

NameLength Required

DescriptionServer requires a Content-Length header but it was not provided.

Code412

NamePrecondition Failed

DescriptionConditional request precondition (If-Match, If-None-Match, etc.) evaluated to false.

Code413

NameContent Too Large

DescriptionRequest body exceeds the server's size limit (previously "Request Entity Too Large").

Code414

NameURI Too Long

DescriptionURI provided was too long for the server to process.

Code415

NameUnsupported Media Type

DescriptionMedia type of the request body is not supported (check Content-Type header).

Code416

NameRange Not Satisfiable

DescriptionRange specified in Range header cannot be fulfilled (e.g., beyond end of file).

Code417

NameExpectation Failed

DescriptionServer cannot meet the requirements of the Expect header in the request.

Code418

NameI'm a Teapot

DescriptionApril Fools joke (RFC 2324). Server refuses to brew coffee because it is a teapot.

Code421

NameMisdirected Request

DescriptionRequest was directed at a server unable to produce a response for this host/scheme combination.

Code422

NameUnprocessable Content

Description(WebDAV / REST APIs) Request is well-formed but has semantic errors (invalid field values, etc.).

Code423

NameLocked

Description(WebDAV) Resource is locked.

Code424

NameFailed Dependency

Description(WebDAV) Request failed because a previous request it depended on failed.

Code425

NameToo Early

DescriptionServer unwilling to risk processing a request that might be replayed (TLS early data).

Code426

NameUpgrade Required

DescriptionClient should switch to the protocol specified in the Upgrade header.

Code428

NamePrecondition Required

DescriptionOrigin server requires the request to be conditional (to prevent lost-update problems).

Code429

NameToo Many Requests

DescriptionClient has sent too many requests in a given time (rate limiting). Check Retry-After header.

Code431

NameRequest Header Fields Too Large

DescriptionServer unwilling to process the request because header fields are too large.

Code451

NameUnavailable For Legal Reasons

DescriptionResource has been blocked for legal reasons (e.g., government censorship, DMCA takedown).

Code500

NameInternal Server Error

DescriptionGeneric server-side error. Something went wrong on the server. Check server logs.

Code501

NameNot Implemented

DescriptionServer does not recognise or support the request method.

Code502

NameBad Gateway

DescriptionServer acting as a gateway received an invalid response from an upstream server.

Code503

NameService Unavailable

DescriptionServer temporarily unable to handle requests (overloaded, in maintenance). Check Retry-After.

Code504

NameGateway Timeout

DescriptionServer acting as gateway timed out waiting for a response from an upstream server.

Code505

NameHTTP Version Not Supported

DescriptionServer does not support the HTTP version used in the request.

Code506

NameVariant Also Negotiates

DescriptionTransparent content negotiation results in a circular reference (server misconfiguration).

Code507

NameInsufficient Storage

Description(WebDAV) Server cannot store the representation needed to complete the request.

Code508

NameLoop Detected

Description(WebDAV) Server detected an infinite loop while processing the request.

Code510

NameNot Extended

DescriptionFurther extensions to the request are required before the server can fulfil it.

Code511

NameNetwork Authentication Required

DescriptionClient needs to authenticate to gain network access (e.g., captive portal).

HTTP status codes communicate the outcome of every web request — success, failure, redirect, or server error. A solid understanding of status codes is essential for building robust APIs, configuring reverse proxies, debugging client-server interactions, and writing meaningful test assertions. Both the exact code and its semantics matter: a 401 and a 403 both block access but require fundamentally different client responses.

This reference covers every standardised code across the 1xx–5xx classes, including recently standardised additions like 103 Early Hints and 425 Too Early, with descriptions, common causes, appropriate server usage, and recommended client behaviour for each.

So verwenden Sie die HTTP-Statuscode-Referenz

1
Nach Statuscode oder Kategorie suchen
Geben Sie einen HTTP-Statuscode (z.B. 404, 503) oder ein Kategorie-Schlüsselwort (z.B. 'Weiterleitung', 'Serverfehler') in das Suchfeld ein.
2
Das Tool zeigt übereinstimmende Codes an
Die Referenz zeigt sofort alle übereinstimmenden HTTP-Statuscodes mit ihren numerischen Codes, offiziellen Namen und detaillierten Beschreibungen an.
3
Fehlerbehebungsanleitung lesen
Jeder Statuscode enthält Informationen darüber, wann er auftritt, was ihn verursacht und häufige Fehlerbehebungsschritte.

How HTTP Status Codes Are Standardised

HTTP status codes are defined primarily in RFC 9110 (the 2022 update to RFC 7231), with additional codes specified in protocol extensions. The IANA HTTP Status Code Registry is the authoritative list, maintained as a living document. New codes require an RFC or similar specification and must fit into the class structure defined by the first digit.

The extensibility model means that new codes can be added without breaking existing clients, because a client that does not recognise a specific code can fall back to the class-level default (e.g., treating 451 as 400). Some codes like 418 (I'm a Teapot, from RFC 2324) are technically not in the IANA registry as reserved but are widely known and protected from assignment to serious uses.

Warum FileCrank HTTP-Statuscode-Referenz verwenden

✓ Vollständige Referenz aller HTTP/1.1 und HTTP/2 Statuscodes (1xx–5xx)
✓ Suche nach Statuscodenummer oder Schlüsselwort (z.B. 'nicht gefunden', 'zu viele Anfragen')
✓ Gruppiert nach Kategorie: informativ (1xx), Erfolg (2xx), Weiterleitung (3xx), Client-Fehler (4xx), Server-Fehler (5xx)
✓ Läuft vollständig in Ihrem Browser mit lokal gebündelten Referenzdaten
✓ Unverzichtbar für API-Entwicklung, Web-Debugging und Fehlerbehebung

Funktionen & Spezifikationen

Max. Dateigröße: Bis zu 100 MB
Datenschutz: DSGVO-konform: Dateien werden nach etwa einer Stunde gelöscht
Preis: Kostenlos, keine Registrierung
Verarbeitung: Serverseitig
Verarbeitung: 100% clientseitig
Datenbankquelle: RFC 7231, RFC 6585, IANA HTTP-Statuscode-Register
Abdeckung: Statuscodes 1xx, 2xx, 3xx, 4xx, 5xx
Kosten: Kostenlos — keine Limits

Läuft vollständig in Ihrem Browser — keine Daten werden an Server gesendet.Keine Registrierung erforderlich.Kostenlos — keine versteckten Gebühren.

Häufig gestellte Fragen

Wie verwende ich die HTTP-Statuscode-Referenz?

Geben Sie einen HTTP-Statuscode (z.B. 404) oder ein Beschreibungs-Schlüsselwort (z.B. 'nicht gefunden') ein und das Tool zeigt sofort übereinstimmende Codes mit Erklärungen an.

Was ist ein HTTP-Statuscode?

Ein HTTP-Statuscode ist eine 3-stellige numerische Antwort von einem Webserver, die das Ergebnis einer Anfrage angibt. Codes 2xx zeigen Erfolg an, 3xx Weiterleitung, 4xx Client-Fehler und 5xx Server-Fehler.

Was bedeutet ein 404-Fehler?

404 bedeutet 'Nicht Gefunden'. Der Server erhielt die Anfrage, konnte aber die angeforderte Ressource nicht finden.

Was ist der Unterschied zwischen einer 301- und 302-Weiterleitung?

301 (Dauerhaft Verschoben) zeigt an, dass die Ressource dauerhaft verschoben wurde und Browser Lesezeichen aktualisieren sollten. 302 (Gefunden) zeigt eine temporäre Weiterleitung an.

Was verursacht einen 500 Internal Server Error?

Ein 500-Fehler zeigt einen serverseitigen Anwendungsabsturz oder eine unbehandelte Ausnahme an. Überprüfen Sie Server-Protokolle und Anwendungscode.

Was bedeutet 429 Too Many Requests?

429 bedeutet, dass der Client zu viele Anfragen in kurzer Zeit gesendet hat. Der Server begrenzt die Rate, um Missbrauch zu verhindern.