HTTP Status Code Lookup
Plain-English reference for every HTTP status code — 200, 301, 404, 500 and more.
- Runs in your browser
- No upload on server
- Free, forever
- Enter details
- Run check
- Copy result
The server has received the request headers and the client should proceed.
The server is switching protocols as requested.
Standard success — the request worked.
The request succeeded and a new resource was created.
Request accepted for processing, but not yet completed.
Success, but there is no body to return.
The server is returning part of the resource (range requests).
The resource has a new URL — update bookmarks and links.
Temporary redirect to a different URL.
The cached copy is still fresh — no need to re-download.
Same method, different URL, just for now.
Like 301 but the original method is preserved.
The server can't understand the request.
You need to sign in.
You're signed in but not allowed.
The page or resource doesn't exist.
The HTTP method isn't supported on this URL.
The server gave up waiting for the request.
The request conflicts with the current state (e.g. duplicate).
The resource used to exist but is permanently removed.
The upload is bigger than the server allows.
The server doesn't accept the body's format.
An April Fools' joke from RFC 2324 — still served as an Easter egg.
Request is well-formed but failed validation.
Rate-limited — slow down or wait.
Something broke on the server side.
The server doesn't support this feature.
An upstream server gave an invalid response.
The server is overloaded or down for maintenance.
An upstream server didn't respond in time.
The HTTP version in the request isn't supported.
How this works — and why it's private
- Type a code or part of a name to filter the list.
- Use it to explain an error to a non-technical teammate.
Rate HTTP Status Code Lookup
One tap. Anonymous. Helps others find the good tools.
No account, no email, no tracking — just a 1–5 number.