Web & HTTP

HTTP Status Code Reference

Free online tool · runs in your browser

Quick reference for HTTP status codes.

Code	Name	Description	Typical Use
100	Continue	The server has received the request headers.	Large uploads where the client waits for a go-ahead before sending the body.
101	Switching Protocols	The server agrees to switch protocols.	WebSocket upgrades and HTTP/2 negotiation.
102	Processing	The server has received and is processing the request.	Long-running WebDAV operations.
200	OK	The request succeeded.	Standard successful GET, PUT, or PATCH responses.
201	Created	A new resource was created.	POST requests that create records.
202	Accepted	The request was accepted but processing is not complete.	Async jobs queued for background processing.
204	No Content	Success with no response body.	DELETE or PUT where no payload is needed.
301	Moved Permanently	The resource has a new permanent URL.	SEO-friendly permanent redirects.
302	Found	Temporary redirect to another URL.	Post-login redirects or temporary moves.
304	Not Modified	Cached version is still valid.	Conditional GET with ETag or Last-Modified.
307	Temporary Redirect	Temporary redirect preserving the HTTP method.	Form submissions that must stay POST.
308	Permanent Redirect	Permanent redirect preserving the HTTP method.	Canonical URL changes for non-GET requests.
400	Bad Request	The server could not understand the request.	Malformed JSON, missing required fields, invalid syntax.
401	Unauthorized	Authentication is required or failed.	Missing or invalid access tokens.
403	Forbidden	Authenticated but not allowed to access the resource.	Role-based access control denials.
404	Not Found	The resource does not exist.	Unknown routes or deleted records.
405	Method Not Allowed	The HTTP method is not supported for this endpoint.	POST sent to a read-only GET route.
408	Request Timeout	The server timed out waiting for the request.	Slow clients or stalled uploads.
409	Conflict	The request conflicts with the current state.	Duplicate email registration or version conflicts.
413	Payload Too Large	The request body exceeds the allowed size.	File upload limits.
415	Unsupported Media Type	The Content-Type is not supported.	Sending XML to a JSON-only API.
422	Unprocessable Entity	Validation failed on well-formed input.	Schema validation errors in REST APIs.
429	Too Many Requests	Rate limit exceeded.	API throttling and abuse prevention.
500	Internal Server Error	An unexpected error occurred on the server.	Unhandled exceptions in backend code.
502	Bad Gateway	Invalid response from an upstream server.	Reverse proxy or gateway failures.
503	Service Unavailable	The server is temporarily unavailable.	Maintenance windows or overload.
504	Gateway Timeout	Upstream server did not respond in time.	Slow downstream microservices.

…

Quick tutorial

1Use the search box to filter codes.
2Browse by category (1xx–5xx).

Free online http status code reference

Look up HTTP status codes with short meanings and when to use them. Search 404, 401, 403, 500, 502, 503, and the rest of the 1xx–5xx ranges. This is a developer reference, not an RFC reprint — common standard codes are listed so you can pick the right response while debugging APIs and web apps.

How to use HTTP Status Code Reference

Use the search box to filter codes.
Browse by category (1xx–5xx).

Limitations

Reference only — not all non-standard codes are listed.

Example

Input

Search: 404

Output

404 Not Found
The resource does not exist.
Typical use: Unknown routes or deleted records.

FAQ

Frequently Asked Questions

What does HTTP 404 mean?

Not Found — the server cannot find the requested resource. Typical for unknown routes or deleted records.

Are unofficial status codes included?

The list focuses on commonly used standard codes, not every historical or vendor-specific code.

Is 418 included?

This reference focuses on commonly used standard codes.

Is HTTP Status Code Reference free to use?

Yes. HTTP Status Code Reference on ShadowReference is free, with no account, no watermarks, and no server-side processing.

Does this tool send my data to a server?

No. All processing happens locally in your browser. Your input never leaves your device.