HTTP Status Code Checker
100% PrivateDeveloper ToolsLook up any HTTP status code and read a plain explanation of what it means.
Runs entirely in your browser. Your input is not uploaded to Ovatly or anywhere else.
This is a reference lookup for codes you paste in. It does not fetch or test any live website.
Reference table (30 codes)
- 100 Continue, Informational (1xx). The server received the request headers and the client should send the body.
- 101 Switching Protocols, Informational (1xx). The server agreed to switch protocols, for example to WebSocket.
- 200 OK, Successful (2xx). The request succeeded. For GET this means the page or data was returned.
- 201 Created, Successful (2xx). The request succeeded and a new resource was created, usually after a POST.
- 202 Accepted, Successful (2xx). The request was accepted for processing but is not complete yet.
- 204 No Content, Successful (2xx). The request succeeded but there is no content to return.
- 206 Partial Content, Successful (2xx). The server returned only part of the resource, as requested by a Range header.
- 301 Moved Permanently, Redirection (3xx). The resource has permanently moved to the URL in the Location header. Browsers and search engines update their records.
- 302 Found, Redirection (3xx). The resource is temporarily at another URL. The original URL stays the canonical one.
- 303 See Other, Redirection (3xx). The client should fetch the Location URL with a GET request.
- 304 Not Modified, Redirection (3xx). The cached copy is still valid, so no body is sent.
- 307 Temporary Redirect, Redirection (3xx). Temporary redirect that keeps the original method and body.
- 308 Permanent Redirect, Redirection (3xx). Permanent redirect that keeps the original method and body.
- 400 Bad Request, Client Error (4xx). The server could not understand the request because of malformed syntax or invalid data.
- 401 Unauthorized, Client Error (4xx). Authentication is required or the credentials given were rejected. Despite the name, this means unauthenticated.
- 403 Forbidden, Client Error (4xx). The server understood the request but refuses to allow it. Logging in again usually does not help.
- 404 Not Found, Client Error (4xx). The server cannot find anything at this URL.
- 405 Method Not Allowed, Client Error (4xx). The URL exists but not for this HTTP method, for example a POST to a read-only endpoint.
- 408 Request Timeout, Client Error (4xx). The client took too long to send the request, so the server closed the connection.
- 409 Conflict, Client Error (4xx). The request conflicts with the current state of the resource.
- 410 Gone, Client Error (4xx). The resource was deliberately and permanently removed. Stronger than 404: it tells crawlers to drop the page.
- 413 Content Too Large, Client Error (4xx). The request body is larger than the server allows.
- 415 Unsupported Media Type, Client Error (4xx). The server refuses the request body's format.
- 422 Unprocessable Content, Client Error (4xx). The syntax is fine but the data fails validation.
- 429 Too Many Requests, Client Error (4xx). The client sent too many requests in a given time and is rate limited.
- 500 Internal Server Error, Server Error (5xx). A generic server-side failure. The application crashed or hit an unhandled error.
- 501 Not Implemented, Server Error (5xx). The server does not support the functionality needed for this request.
- 502 Bad Gateway, Server Error (5xx). A proxy or gateway received an invalid response from the upstream server.
- 503 Service Unavailable, Server Error (5xx). The server cannot handle the request right now, usually temporarily.
- 504 Gateway Timeout, Server Error (5xx). A proxy or gateway did not receive a timely response from the upstream server.
- 1Type a code (404), a response line (HTTP/1.1 503 Service Unavailable), or a keyword (timeout).
- 2Read the explanation card: class, meaning and common causes.
- 3Or browse and filter the full reference table below the result.
Worked example
Looking up a response line
Pasting "HTTP/1.1 503 Service Unavailable" extracts the code 503 and explains: class Server Error (5xx), the server cannot handle the request right now, usually temporarily, with overload, maintenance and in-progress deployments as the common causes. Looking up 410 gives "Gone": deliberately and permanently removed, stronger than a 404.
- The reference covers the standard codes developers meet daily (30 codes across the 1xx to 5xx classes). A valid but uncommon code still gets its class explanation.
- This tool never contacts a server: paste-based checking only, so nothing about your sites or systems is sent anywhere.
- Class rules of thumb: 4xx means the request was at fault, 5xx means the server was, 3xx means look elsewhere, 2xx means it worked.
No. It explains codes you paste in; it does not fetch URLs. Your host's uptime monitor or a status page is the right tool for live checks.
About this tool
The HTTP Status Code Checker explains the code you paste: a bare number, a full response line like HTTP/1.1 503, or a keyword. For each code it gives the class, what it actually means and the common causes, plus a searchable reference table. It is a lookup for codes you already have; it does not fetch or test any live website.
Related tools
User Agent ParserBreak a user agent string down into browser, engine, operating system and device typeDeveloper ToolsOpenDNS Record Formatter and ExplainerFormat pasted DNS records into a clean table and explain what each record doesWebsite & Webmaster ToolsOpenMeta Tag Checker (from pasted HTML)Analyze the meta tags in HTML you paste, including title, description and social tagsWebsite & Webmaster ToolsOpenRedirect Rule GeneratorTurn a list of old and new URLs into ready-to-paste .htaccess or Nginx redirect rulesWebsite & Webmaster ToolsOpen
Advertisement
Part of Ovatly's free tools in Developer Tools.