Digital Solutions Agency
HTTP Status Code Lookup
Interactive, searchable reference handbook for HTTP response status codes with official specifications and debugging use cases.
Continue
The initial part of a request has been received and has not yet been rejected by the server.
Sent when client sends Expect: 100-continue before uploading large payload.
Switching Protocols
The requester has asked the server to switch protocols and the server has agreed to do so.
WebSocket upgrade handshake over HTTP/1.1.
OK
Standard response for successful HTTP requests.
Returning a successful GET payload or successfully handled request.
Created
The request has been fulfilled, resulting in the creation of a new resource.
Successfully creating a record via POST request (e.g. POST /api/users).
No Content
The server successfully processed the request and is not returning any content.
Successful DELETE operations or PUT updates where client needs no response body.
Partial Content
The server is delivering only part of the resource due to a Range header sent by the client.
Video streaming, audio seeking, and resumable file downloads.
Moved Permanently
This and all future requests should be directed to the given URI.
Domain migrations, HTTPS enforcement redirects, permanent URL structure changes.
Found (Temporary Redirect)
Tells the client to look at another URL temporarily.
Redirecting unauthenticated users to a login page, or short-lived marketing campaigns.
Not Modified
Indicates that the resource has not been modified since the version specified by the request headers.
Browser HTTP caching using If-None-Match (ETag) or If-Modified-Since headers.
Temporary Redirect
The request should be repeated with another URI; however, future requests should still use the original URI.
Redirecting POST requests without allowing the browser to change method to GET.
Permanent Redirect
The target resource has been assigned a new permanent URI and any future references should use one of the returned URIs.
Permanent redirect ensuring original HTTP method (POST, PUT) is strictly preserved.
Bad Request
The server cannot or will not process the request due to an apparent client error.
Malformed JSON body, missing required parameters, or invalid header formatting.
Unauthorized
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
Missing or invalid JWT Bearer token, expired session token.
Forbidden
The request contained valid data and was understood by the server, but the server is refusing action.
User is authenticated but lacks required admin roles or permissions for that resource.
Not Found
The requested resource could not be found but may be available in the future.
Querying an ID that does not exist in the database, or mistyped API URL endpoints.
Method Not Allowed
A request method is not supported for the requested resource.
Sending a POST or DELETE to a route that only accepts GET requests.
Request Timeout
The server timed out waiting for the request from the client.
Slow client connection or stalled file upload stream before full headers arrive.
Conflict
Indicates that the request could not be processed because of conflict in the current state of the resource.
Attempting to register with an email that already exists, or concurrent edit version conflict.
Gone
Indicates that the resource requested was previously in use but is no longer available and will not be available again.
Permanently purged API versions or intentionally deleted promotional offers.
Payload Too Large
The request is larger than the server is willing or able to process.
Uploading an image or file exceeding the server limit (e.g. 10MB limit exceeded).
I'm a teapot
Any attempt to brew coffee with a teapot should result in the error code 418 I'm a teapot.
RFC 2324 April Fools' joke specification; often used as an easter egg in APIs.
Unprocessable Content
The request was well-formed but was unable to be followed due to semantic errors.
Validation failure (e.g. valid JSON payload, but 'age' is negative or 'email' format is invalid).
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
API rate limits reached; often accompanied by a Retry-After response header.
Internal Server Error
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
Unhandled exceptions, database connection crash, or fatal runtime crash.
Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfil the request.
API route placeholder or unsupported HTTP verb.
Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
Nginx / Cloudflare reverse proxy cannot connect to backend Node.js / Docker container.
Service Unavailable
The server cannot handle the request (because it is overloaded or down for maintenance).
Temporary maintenance mode or upstream server under heavy load spikes.
Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
Long-running database query or slow third-party API call causing reverse proxy timeout.
How to use this tool
Search by Code or Keyword
Type an HTTP status code like '404' or a keyword like 'rate limit', 'timeout', or 'unauthorized'.
Filter by Status Class
Use the filter buttons (2xx Success, 4xx Client Error, 5xx Server Error) to narrow down results.
Read Practical Scenarios
Review typical use cases to understand what triggers each code in production REST APIs and web servers.
Related Tools
Other utilities you might find helpful for your workflow
Text Case Converter
Instantly transform text between UPPERCASE, lowercase, Title Case, Sentence case, and Capitalize Each Word.
Word & Character Counter
Real-time count of words, characters, characters without spaces, sentences, paragraphs, and reading time.
Text Cleaner
Strip redundant whitespace, collapse multiple spaces, remove blank lines, trim lines, and normalize line endings.