Codici di stato HTTP per classe
I codici standard rimandano all’RFC che li definisce. I codici usati solo da Cloudflare o nginx sono indicati come non standard. L’etichetta su ogni riga dice se un monitor HTTP di Uptimecheck, con le impostazioni predefinite, considera il codice online o offline (200–399 è online).
Nessun codice di stato corrisponde. Prova un numero come 404 o una parola come “timeout”. Mostra tutti i codici
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: Provvisorio
- 101 Switching Protocols The server agrees to switch the connection to another protocol. Monitor: Down
- 102 Processing Deprecated A WebDAV server is still working on a long request. Monitor: Provvisorio
- 103 Early Hints The server sends preload hints before the final response is ready. Monitor: Provvisorio
2xx Success
The request was received, understood and accepted.
- 200 OK The request succeeded. Monitor: Online
- 201 Created The request created a new resource. Monitor: Online
- 202 Accepted The request was accepted but hasn’t been processed yet. Monitor: Online
- 203 Non-Authoritative Information The request succeeded, but a proxy changed the content. Monitor: Online
- 204 No Content The request succeeded and there is no body to send. Monitor: Online
- 205 Reset Content The request succeeded and the client should reset the form that sent it. Monitor: Online
- 206 Partial Content The server sends only the part of the file the client asked for. Monitor: Online
- 207 Multi-Status One WebDAV response holds a separate status for several resources. Monitor: Online
- 208 Already Reported WebDAV members were already listed earlier in the same response. Monitor: Online
- 226 IM Used The server answered with changes to a version the client already has. Monitor: Online
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: Online
- 301 Moved Permanently The page has moved to a new URL for good. Monitor: Online
- 302 Found The page is temporarily at another URL. Monitor: Online
- 303 See Other The client should get the result from another URL with a GET. Monitor: Online
- 304 Not Modified The copy the client already has is still current. Monitor: Online
- 305 Use Proxy Deprecated A deprecated code that told the client to use a proxy. Monitor: Online
- 306 (Unused) Reserved, not used A reserved code that is no longer used. Monitor: Online
- 307 Temporary Redirect The page is temporarily elsewhere and the method must be kept. Monitor: Online
- 308 Permanent Redirect The page has moved for good and the method must be kept. Monitor: Online
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: Down
- 401 Unauthorized The request needs valid authentication. Monitor: Down
- 402 Payment Required A code reserved for future use, used by some services for unpaid accounts. Monitor: Down
- 403 Forbidden The server understood the request but refuses it. Monitor: Down
- 404 Not Found The server has nothing at this URL. Monitor: Down
- 405 Method Not Allowed The URL exists but doesn’t accept this request method. Monitor: Down
- 406 Not Acceptable The server can’t answer in a format the client accepts. Monitor: Down
- 407 Proxy Authentication Required A proxy between the client and the server needs credentials. Monitor: Down
- 408 Request Timeout The server gave up waiting for the client to send the request. Monitor: Down
- 409 Conflict The request conflicts with the resource’s current state. Monitor: Down
- 410 Gone The page has been removed for good. Monitor: Down
- 411 Length Required The server requires a Content-Length header. Monitor: Down
- 412 Precondition Failed A condition in the request headers turned out false. Monitor: Down
- 413 Content Too Large The request body is larger than the server accepts. Monitor: Down
- 414 URI Too Long The URL is longer than the server will read. Monitor: Down
- 415 Unsupported Media Type The server doesn’t accept the format of the request body. Monitor: Down
- 416 Range Not Satisfiable The requested part of the file doesn’t exist. Monitor: Down
- 417 Expectation Failed The server can’t meet the request’s Expect header. Monitor: Down
- 418 (Unused) Reserved, not used The reserved “I’m a teapot” code from an April Fools’ RFC. Monitor: Down
- 421 Misdirected Request The request reached a server that can’t answer for this host name. Monitor: Down
- 422 Unprocessable Content The request is well-formed but its content isn’t valid. Monitor: Down
- 423 Locked The WebDAV resource is locked. Monitor: Down
- 424 Failed Dependency A WebDAV action failed because another one it depended on failed. Monitor: Down
- 425 Too Early The server won’t risk processing a request that could be replayed. Monitor: Down
- 426 Upgrade Required The server requires the client to switch to another protocol. Monitor: Down
- 428 Precondition Required The server requires a conditional request. Monitor: Down
- 429 Too Many Requests The client sent too many requests in a given time. Monitor: Down
- 431 Request Header Fields Too Large The request headers are too large for the server. Monitor: Down
- 444 No Response Non standard · nginx Nginx closed the connection without sending anything. Monitor: Down
- 451 Unavailable For Legal Reasons Access is denied because of a legal demand. Monitor: Down
- 499 Client Closed Request Non standard · nginx The client hung up before nginx could answer. Monitor: Provvisorio
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: Down
- 501 Not Implemented The server doesn’t support what the request needs. Monitor: Down
- 502 Bad Gateway A proxy got an invalid response from the server behind it. Monitor: Down
- 503 Service Unavailable The server is temporarily overloaded or down for maintenance. Monitor: Down
- 504 Gateway Timeout A proxy didn’t get an answer from the server behind it in time. Monitor: Down
- 505 HTTP Version Not Supported The server doesn’t support the request’s HTTP version. Monitor: Down
- 506 Variant Also Negotiates The server’s content negotiation is misconfigured. Monitor: Down
- 507 Insufficient Storage The server has no room to store what the request needs. Monitor: Down
- 508 Loop Detected The server found an infinite loop while processing the request. Monitor: Down
- 510 Not Extended Obsolete An obsolete code from the HTTP extension framework. Monitor: Down
- 511 Network Authentication Required The network needs you to sign in before you get access. Monitor: Down
- 520 Web Server Returned an Unknown Error Non standard · Cloudflare Cloudflare got an empty or unexpected response from the origin server. Monitor: Down
- 521 Web Server Is Down Non standard · Cloudflare The origin server refused Cloudflare’s connection. Monitor: Down
- 522 Connection Timed Out Non standard · Cloudflare Cloudflare couldn’t connect to the origin server in time. Monitor: Down
- 523 Origin Is Unreachable Non standard · Cloudflare Cloudflare can’t reach the origin server at all. Monitor: Down
- 524 A Timeout Occurred Non standard · Cloudflare The origin server accepted the connection but answered too slowly. Monitor: Down
- 525 SSL Handshake Failed Non standard · Cloudflare The TLS handshake between Cloudflare and the origin failed. Monitor: Down
- 526 Invalid SSL Certificate Non standard · Cloudflare Cloudflare couldn’t validate the origin server’s certificate. Monitor: Down
Verifica cosa restituisce il tuo sito
Il checker gratuito per siti web richiede qualsiasi URL da Stoccolma e mostra il codice di stato con cui risponde, ogni redirect lungo il percorso, il tempo di risposta e la scadenza del certificato.
Controlla un sito webSu quali codici dovrebbe avvisare un monitor?
I codici di stato che contano per l’uptime, quali indicano problemi reali e come impostare controlli che non diano falsi allarmi.
Leggi il prontuarioDomande
Cosa significano le cinque classi di codici di stato?
La prima cifra indica la classe: 1xx informativo (la richiesta è in corso), 2xx successo, 3xx reindirizzamento, 4xx errore del client (il server rifiuta la richiesta così com’è stata inviata) e 5xx errore del server. Un client che non conosce un codice lo tratta come il codice x00 della sua classe, quindi un 4xx sconosciuto viene gestito come un 400.
Quali codici di stato considera offline Uptimecheck?
Per impostazione predefinita un monitor HTTP considera up i codici 200–399 e down tutto il resto, e un down viene segnalato solo dopo la conferma di un secondo controllo. I redirect vengono seguiti, fino a 10, e decide la risposta finale. Puoi impostare i codici di stato attesi per ogni monitor, per esempio 200-299, 401. Il checker gratuito Is it down? considera qualsiasi risposta sotto 500 come sito che risponde.
Che differenza c’è tra 502, 503 e 504?
Di solito tutti e tre arrivano da un proxy o da un load balancer davanti all’applicazione. 502 Bad Gateway: il server dietro ha dato una risposta non valida o nessuna, spesso perché è andato in crash. 503 Service Unavailable: il server è sovraccarico o in manutenzione e lo dichiara. 504 Gateway Timeout: il server dietro non ha risposto in tempo.
I codici 52x di Cloudflare e i 444 e 499 di nginx sono standard?
No. Cloudflare invia i codici 520–526 per descrivere problemi tra la sua rete e il server di origine, e nginx usa 444 (chiude la connessione senza rispondere) e 499 (il client ha chiuso) nei propri log. Non sono in nessuna RFC, quindi qui sono indicati come non standard.
Lascia che Uptimecheck continui a controllare
Questo strumento gratuito risponde a una domanda alla volta. In Uptimecheck lo stesso lavoro gira da solo e ti avvisa quando qualcosa richiede attenzione.
Altri strumenti gratuiti
Tutti gli strumenti- Redirect checker Inserisci un URL per vedere ogni passaggio di redirect con il suo codice di stato, dove arriva e se HTTP passa a HTTPS, verificato in tempo reale da Stoccolma. Apri lo strumento
- È down? Verifica se un sito risponde, quanto è veloce e quando scade il suo certificato. Apri lo strumento
- Verifica certificato SSL Verifica se il certificato di un sito è valido, quando scade, chi l’ha emesso, quali nomi copre e la catena completa, con un controllo da Stoccolma. Apri lo strumento
I disservizi sono acqua passata.
Configura il tuo primo monitor in meno di un minuto, oppure esplora prima la demo live.
Prova gratuita di 14 giorni · Poi gratis con 5 monitor · Nessuna carta di credito