100Continue
The server received the request headers and the client should continue sending the body.
HTTP Status Codes
Look up HTTP status codes from 1xx through 5xx. Search by code or name and copy the number instantly.
28 codes
101Switching Protocols
The server agrees to switch protocols, such as upgrading an HTTP connection to WebSocket.
200OK
The request succeeded. This is the usual response for a successful GET.
201Created
The request created a new resource. The response often includes a Location header.
202Accepted
The request was accepted for processing, but the work is not finished yet.
204No Content
The request succeeded and there is no response body, common for DELETE and some PUT requests.
301Moved Permanently
The resource has a new permanent URL. Clients and caches should use that URL from now on.
302Found
The resource is temporarily at another URL. The original URL should still be used later.
304Not Modified
The cached copy is still valid, so the server sends no body.
307Temporary Redirect
A temporary redirect that keeps the original HTTP method.
308Permanent Redirect
A permanent redirect that keeps the original HTTP method.
400Bad Request
The server could not understand the request because of invalid syntax or malformed data.
401Unauthorized
Authentication is missing or invalid. The client needs to send valid credentials.
403Forbidden
The server understood the request but refuses to authorize it.
404Not Found
The server cannot find the requested resource.
405Method Not Allowed
The HTTP method is not supported for this resource.
408Request Timeout
The server timed out waiting for the rest of the request.
409Conflict
The request conflicts with the current state of the resource, such as a duplicate create.
410Gone
The resource used to exist but has been permanently removed.
413Content Too Large
The request body is larger than the server is willing to process.
415Unsupported Media Type
The payload format is not supported by this resource.
422Unprocessable Content
The syntax is valid, but the server cannot process the instructions, often a validation error.
429Too Many Requests
The client sent too many requests in a given time. Retry after the indicated delay.
500Internal Server Error
The server hit an unexpected condition and could not complete the request.
501Not Implemented
The server does not support the functionality required to fulfill the request.
502Bad Gateway
A gateway or proxy received an invalid response from an upstream server.
503Service Unavailable
The server is temporarily unable to handle the request, often because it is overloaded or down for maintenance.
504Gateway Timeout
A gateway or proxy did not receive a timely response from an upstream server.
More
Related tools
Web
URL Encoder / Decoder
Encode and decode URLs and query string parameters online, instantly. Supports value encoding, full URL encoding, and decoding — free tool.
Web
HTML Entities Encoder / Decoder
Encode and decode HTML entities like < and > instantly online. Free tool for safely embedding user content in HTML, emails, and templates.
Web
URL Parser
Parse any URL into its components online — protocol, host, path, query params, and hash. Free URL parser for debugging redirects and OAuth callbacks.
Web
Slug Generator
Convert any text into a clean, URL-friendly slug instantly online. Free slug generator for blog post URLs, API routes, and file names.
Frequently asked questions
What is HTTP Status Codes?+
Search the status codes you actually meet in APIs and browsers, from 200 OK to 504 Gateway Timeout.
How do I use HTTP Status Codes?+
Filter by class: informational, success, redirect, client error, and server error. Copy a code in one click. Short explanations for the common codes, with no account and no upload
Is HTTP Status Codes free?+
Yes, HTTP Status Codes is completely free. No account or sign-up required, and all processing happens in your browser — nothing is sent to a server.
Is my data safe when I use HTTP Status Codes?+
Yes. HTTP Status Codes runs entirely in your browser using JavaScript and Web APIs — your input is never uploaded, transmitted, or stored on any server.