- Forside
- Gratis værktøjer
- HTTP-statuskoder
Gratis HTTP-statuskoder: Alle HTTP statuskode
Hvad hver statuskode betyder på almindeligt dansk, hvad der typisk forårsager den, hvad du gør ved det, og om et oppetidstjek tæller den som nede.
HTTP-statuskoder efter klasse
Standardkoder linker til den RFC, der definerer dem. Koder, der kun bruges af Cloudflare eller nginx, er markeret som ikke-standard. Mærket på hver række viser, om en Uptimecheck HTTP-monitor tæller koden som oppe eller nede med standardindstillingerne (200–399 er oppe).
Ingen statuskode matcher. Prøv et tal som 404 eller et ord som “timeout”. Vis alle koder
1xx Informational
Interim responses: the request is under way and the real answer follows.
- 100 Continue The server got the request headers and the client may send the body. Monitor: Midlertidig
- 101 Switching Protocols The server agrees to switch the connection to another protocol. Monitor: Nede
- 102 Processing Deprecated A WebDAV server is still working on a long request. Monitor: Midlertidig
- 103 Early Hints The server sends preload hints before the final response is ready. Monitor: Midlertidig
2xx Success
The request was received, understood and accepted.
- 200 OK The request succeeded. Monitor: Oppe
- 201 Created The request created a new resource. Monitor: Oppe
- 202 Accepted The request was accepted but hasn’t been processed yet. Monitor: Oppe
- 203 Non-Authoritative Information The request succeeded, but a proxy changed the content. Monitor: Oppe
- 204 No Content The request succeeded and there is no body to send. Monitor: Oppe
- 205 Reset Content The request succeeded and the client should reset the form that sent it. Monitor: Oppe
- 206 Partial Content The server sends only the part of the file the client asked for. Monitor: Oppe
- 207 Multi-Status One WebDAV response holds a separate status for several resources. Monitor: Oppe
- 208 Already Reported WebDAV members were already listed earlier in the same response. Monitor: Oppe
- 226 IM Used The server answered with changes to a version the client already has. Monitor: Oppe
3xx Redirection
The client has to go somewhere else to complete the request.
- 300 Multiple Choices The resource has several versions and the client may pick one. Monitor: Oppe
- 301 Moved Permanently The page has moved to a new URL for good. Monitor: Oppe
- 302 Found The page is temporarily at another URL. Monitor: Oppe
- 303 See Other The client should get the result from another URL with a GET. Monitor: Oppe
- 304 Not Modified The copy the client already has is still current. Monitor: Oppe
- 305 Use Proxy Deprecated A deprecated code that told the client to use a proxy. Monitor: Oppe
- 306 (Unused) Reserved, not used A reserved code that is no longer used. Monitor: Oppe
- 307 Temporary Redirect The page is temporarily elsewhere and the method must be kept. Monitor: Oppe
- 308 Permanent Redirect The page has moved for good and the method must be kept. Monitor: Oppe
4xx Client error
The server is up, but refuses the request as it was sent.
- 400 Bad Request The server won’t process a request it sees as malformed. Monitor: Nede
- 401 Unauthorized The request needs valid authentication. Monitor: Nede
- 402 Payment Required A code reserved for future use, used by some services for unpaid accounts. Monitor: Nede
- 403 Forbidden The server understood the request but refuses it. Monitor: Nede
- 404 Not Found The server has nothing at this URL. Monitor: Nede
- 405 Method Not Allowed The URL exists but doesn’t accept this request method. Monitor: Nede
- 406 Not Acceptable The server can’t answer in a format the client accepts. Monitor: Nede
- 407 Proxy Authentication Required A proxy between the client and the server needs credentials. Monitor: Nede
- 408 Request Timeout The server gave up waiting for the client to send the request. Monitor: Nede
- 409 Conflict The request conflicts with the resource’s current state. Monitor: Nede
- 410 Gone The page has been removed for good. Monitor: Nede
- 411 Length Required The server requires a Content-Length header. Monitor: Nede
- 412 Precondition Failed A condition in the request headers turned out false. Monitor: Nede
- 413 Content Too Large The request body is larger than the server accepts. Monitor: Nede
- 414 URI Too Long The URL is longer than the server will read. Monitor: Nede
- 415 Unsupported Media Type The server doesn’t accept the format of the request body. Monitor: Nede
- 416 Range Not Satisfiable The requested part of the file doesn’t exist. Monitor: Nede
- 417 Expectation Failed The server can’t meet the request’s Expect header. Monitor: Nede
- 418 (Unused) Reserved, not used The reserved “I’m a teapot” code from an April Fools’ RFC. Monitor: Nede
- 421 Misdirected Request The request reached a server that can’t answer for this host name. Monitor: Nede
- 422 Unprocessable Content The request is well-formed but its content isn’t valid. Monitor: Nede
- 423 Locked The WebDAV resource is locked. Monitor: Nede
- 424 Failed Dependency A WebDAV action failed because another one it depended on failed. Monitor: Nede
- 425 Too Early The server won’t risk processing a request that could be replayed. Monitor: Nede
- 426 Upgrade Required The server requires the client to switch to another protocol. Monitor: Nede
- 428 Precondition Required The server requires a conditional request. Monitor: Nede
- 429 Too Many Requests The client sent too many requests in a given time. Monitor: Nede
- 431 Request Header Fields Too Large The request headers are too large for the server. Monitor: Nede
- 444 No Response Ikke-standard · nginx Nginx closed the connection without sending anything. Monitor: Nede
- 451 Unavailable For Legal Reasons Access is denied because of a legal demand. Monitor: Nede
- 499 Client Closed Request Ikke-standard · nginx The client hung up before nginx could answer. Monitor: Midlertidig
5xx Server error
The server, or something in front of it, failed to answer the request.
- 500 Internal Server Error The server hit an unexpected error. Monitor: Nede
- 501 Not Implemented The server doesn’t support what the request needs. Monitor: Nede
- 502 Bad Gateway A proxy got an invalid response from the server behind it. Monitor: Nede
- 503 Service Unavailable The server is temporarily overloaded or down for maintenance. Monitor: Nede
- 504 Gateway Timeout A proxy didn’t get an answer from the server behind it in time. Monitor: Nede
- 505 HTTP Version Not Supported The server doesn’t support the request’s HTTP version. Monitor: Nede
- 506 Variant Also Negotiates The server’s content negotiation is misconfigured. Monitor: Nede
- 507 Insufficient Storage The server has no room to store what the request needs. Monitor: Nede
- 508 Loop Detected The server found an infinite loop while processing the request. Monitor: Nede
- 510 Not Extended Obsolete An obsolete code from the HTTP extension framework. Monitor: Nede
- 511 Network Authentication Required The network needs you to sign in before you get access. Monitor: Nede
- 520 Web Server Returned an Unknown Error Ikke-standard · Cloudflare Cloudflare got an empty or unexpected response from the origin server. Monitor: Nede
- 521 Web Server Is Down Ikke-standard · Cloudflare The origin server refused Cloudflare’s connection. Monitor: Nede
- 522 Connection Timed Out Ikke-standard · Cloudflare Cloudflare couldn’t connect to the origin server in time. Monitor: Nede
- 523 Origin Is Unreachable Ikke-standard · Cloudflare Cloudflare can’t reach the origin server at all. Monitor: Nede
- 524 A Timeout Occurred Ikke-standard · Cloudflare The origin server accepted the connection but answered too slowly. Monitor: Nede
- 525 SSL Handshake Failed Ikke-standard · Cloudflare The TLS handshake between Cloudflare and the origin failed. Monitor: Nede
- 526 Invalid SSL Certificate Ikke-standard · Cloudflare Cloudflare couldn’t validate the origin server’s certificate. Monitor: Nede
Tjek, hvad dit site returnerer
Det gratis website-tjek henter en hvilken som helst URL fra Stockholm og viser den statuskode, den svarer med, hver omdirigering på vejen, svartiden og hvornår certifikatet udløber.
Tjek et websiteHvilke koder skal en monitor alarmere på?
De statuskoder, der betyder noget for oppetid, hvilke der betyder reelle problemer, og hvordan du sætter tjek op, der ikke råber ulven kommer.
Læs snydearketSpørgsmål
Hvad betyder de fem klasser af statuskoder?
Det første ciffer angiver klassen: 1xx information (forespørgslen er i gang), 2xx succes, 3xx omdirigering, 4xx klientfejl (serveren afviser forespørgslen, som den blev sendt) og 5xx serverfejl. En klient, der ikke kender en kode, behandler den som x00-koden i dens klasse, så en ukendt 4xx håndteres som 400.
Hvilke statuskoder tæller Uptimecheck som nede?
Som standard tæller en HTTP-monitor 200–399 som oppe og alt andet som nede, og et nedbrud meldes først, når et andet tjek bekræfter det. Omdirigeringer følges, op til 10, og det endelige svar afgør det. Du kan angive de forventede statuskoder for hver monitor, for eksempel 200-299, 401. Det gratis Is it down?-værktøj tæller ethvert svar under 500 som, at sitet svarer.
Hvad er forskellen på 502, 503 og 504?
Alle tre kommer typisk fra en proxy eller load balancer foran applikationen. 502 Bad Gateway: serveren bagved gav et ugyldigt svar eller intet, ofte fordi den gik ned. 503 Service Unavailable: serveren er overbelastet eller under vedligeholdelse og siger det. 504 Gateway Timeout: serveren bagved svarede ikke i tide.
Er Cloudflares 52x-koder og nginx' 444 og 499 standard?
Nej. Cloudflare sender 520–526 for at beskrive problemer mellem sit netværk og origin-serveren, og nginx bruger 444 (luk forbindelsen uden at svare) og 499 (klienten afbrød) i sine egne logs. De står ikke i nogen RFC, så de er markeret som ikke-standard her.
Lad Uptimecheck holde øje
Dette gratis værktøj besvarer ét spørgsmål ad gangen. I Uptimecheck kører det samme arbejde af sig selv og alarmerer dig, når noget kræver opmærksomhed.
Flere gratis værktøjer
Alle værktøjer- Redirect-checker Indtast en URL for at se hvert omdirigeringshop med dets statuskode, hvor det ender, og om HTTP går til HTTPS, tjekket live fra Stockholm. Åbn værktøj
- Er det nede? Tjek, om et website svarer, hvor hurtigt, og hvornår dets certifikat udløber. Åbn værktøj
- SSL-certifikattjek Se, om et websites certifikat er gyldigt, hvornår det udløber, hvem der har udstedt det, hvilke navne det dækker og hele kæden, tjekket fra Stockholm. Åbn værktøj
Nedetid er fortid.
Opret din første monitor på under et minut, eller se dig omkring i livedemoen først.
14 dages gratis prøveperiode · Derefter gratis med 5 monitorer · Intet betalingskort