HTTP Status Code Lookup
FreeLook up meaning and description of any HTTP status code
1xx · Informational
Continue
The server received the request headers and the client should proceed to send the body.
Switching Protocols
The server is switching protocols as requested by the client (e.g. to WebSocket).
Early Hints
Used to preload resources while the server prepares the final response.
2xx · Success
OK
The request succeeded. The meaning depends on the method (GET returns the resource, POST the result).
Created
The request succeeded and a new resource was created — usually after a POST.
Accepted
The request was accepted for processing, but is not yet complete.
No Content
The request succeeded but there is no content to return (common for DELETE/PUT).
Partial Content
The server is delivering only part of the resource (range requests — video, resumable downloads).
3xx · Redirection
Moved Permanently
The resource has permanently moved to a new URL. Search engines update their links.
Found
The resource is temporarily at a different URL. Keep using the original URL.
Not Modified
The cached version is still valid — the client can reuse it. Saves bandwidth.
Temporary Redirect
Like 302, but the request method must not change on the redirect.
Permanent Redirect
Like 301, but the request method must not change on the redirect.
4xx · Client Error
Bad Request
The server cannot process the request due to a client error (malformed syntax, invalid data).
Unauthorized
Authentication is required and has failed or not been provided.
Payment Required
Reserved for future use — sometimes used by APIs for billing/quota limits.
Forbidden
The server understood the request but refuses to authorize it. You don’t have permission.
Not Found
The server cannot find the requested resource. The URL may be wrong or the resource deleted.
Method Not Allowed
The HTTP method is not supported for this resource (e.g. POST to a read-only endpoint).
Request Timeout
The server timed out waiting for the request.
Conflict
The request conflicts with the current state of the resource (e.g. duplicate entry).
Gone
The resource is permanently gone and will not return. Stronger than 404.
Payload Too Large
The request body is larger than the server is willing to process.
Unsupported Media Type
The request’s Content-Type is not supported by the server.
I'm a teapot
An April Fools’ joke from RFC 2324 — the server refuses to brew coffee because it is a teapot.
Unprocessable Entity
The request was well-formed but contains semantic errors (common for validation failures).
Too Many Requests
The client has sent too many requests in a given time — rate limited. Slow down.
Request Header Fields Too Large
The header fields are too large for the server to process.
Unavailable For Legal Reasons
The resource is blocked for legal reasons (censorship, takedown).
5xx · Server Error
Internal Server Error
A generic server-side error — something went wrong on the server.
Not Implemented
The server does not support the functionality required to fulfil the request.
Bad Gateway
The server, acting as a gateway/proxy, got an invalid response from the upstream server.
Service Unavailable
The server is temporarily overloaded or down for maintenance. Try again later.
Gateway Timeout
The server, acting as a gateway, did not get a response in time from the upstream server.
HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
About HTTP Status Code Lookup
HTTP status codes are a shared language, but few of us remember every one. Is 422 the right code for a validation error? What exactly does 409 mean? The HTTP Status Code Lookup lets you enter any status code and instantly get its name and a clear description, so you can use the correct code in your API and understand the ones you receive.
Type a code like 301, 418, or 503 and the tool returns its meaning along with a short explanation of when it applies. It's free, runs in your browser, and needs no signup. Whether you're choosing the right response for an endpoint you're building or decoding an error from someone else's service, it gives you an authoritative answer without digging through a spec document.
Common uses
- Decide between 401 and 403 when designing how your API responds to auth failures.
- Quickly decode an unfamiliar code like 451 or 426 returned by a third-party service.
- Confirm the right success code, such as 201 versus 200, for a resource-creation endpoint.
- Look up a redirect code to choose between a permanent 301 and a temporary 302.
- Settle a code-review debate about the correct status for a particular error condition.
How to use
- 1
Configure options
Set your preferences using the options panel below.
- 2
Click Generate
Click the process button to generate your result instantly.
- 3
Copy or download
Copy the result to clipboard or download it directly to your device.
Why ToolHub?
- Test APIs instantly
- No Postman needed
- Full header control
FAQ
Which status codes does it cover?
It covers standard HTTP status codes across the informational, success, redirection, client error, and server error ranges.
Does it explain when to use a code?
Each result includes a description of the code's meaning so you can judge whether it fits your situation.
Can I look up unusual codes like 418?
Yes. You can search any valid code, including the less common ones, to find what it represents.
Is it just a reference, or does it test anything?
It's a reference lookup. To see codes returned by a live endpoint, use the API testing tools instead.
Can I use HTTP Status Code Lookup on mobile?
Yes — ToolHub is fully responsive and works on iPhone, Android, tablets and all modern browsers. No app install needed.