HTTP status codes
Searchable reference of all HTTP status codes with descriptions.
A number such as 404 or a word such as redirect or timeout. The list below filters as you type.
Server received request headers. Client should send body.
Server switches protocol (e.g. to WebSocket).
Server sends early Link headers for preloading.
Request processed successfully.
Resource successfully created.
Request accepted, processing pending.
Successful, but no response body.
Partial content (range request).
Resource permanently moved. Search engines adopt new URL.
Temporary redirect. Original URL remains for search engines.
Redirect via GET to another URL (after POST).
Resource not modified (ETag/If-Modified-Since).
Temporary redirect, method preserved.
Permanent redirect, method preserved.
Malformed syntax or invalid parameters.
Authentication required (missing or invalid).
Access denied despite valid auth.
Resource does not exist at this URL.
HTTP method not allowed for this resource.
Server timed out waiting for request.
Conflict with current state of resource.
Resource permanently removed (stronger than 404).
Content-Length header missing.
Request body exceeds server limit.
URL too long for server.
Content-Type not supported.
April fools RFC 2324. Some APIs use it as Easter egg.
Syntax correct but semantically invalid (validation error).
Rate limit exceeded. Check Retry-After header.
Content blocked for legal reasons.
Unexpected server error.
Server does not support the requested functionality.
Upstream server returned invalid response.
Server overloaded or in maintenance.
Upstream server did not respond in time.
Server has no storage space left.
Infinite loop detected during processing.
Captive portal authentication required.
How this tool works
Searchable reference of all common HTTP status codes with German and English descriptions. From 1xx (informational) through 2xx (success), 3xx (redirect), 4xx (client error) to 5xx (server error) — each code with practical explanation of when and why it occurs.
Typical use cases
- Quickly look up what a specific status code means
- During API debugging, clarify the difference between 401 and 403
- Team meetings: choose correct status codes for REST API endpoints
- Students and beginners: learn HTTP fundamentals
Frequently asked questions
What is the difference between 301 and 302?
301 = permanently moved (search engines adopt new URL, link juice is passed). 302 = temporary (original URL stays in search engine index).
When to use 401 vs. 403?
401 = not authenticated (login missing). 403 = authenticated but not authorized. After 401 the client should be able to log in, after 403 login will not help.
What does 429 Too Many Requests mean?
Rate limit exceeded. The Retry-After header indicates when the next request is allowed. Typical for APIs with fair-use limits.
Are there official status codes above 500?
Yes — 501 (Not Implemented), 502 (Bad Gateway), 503 (Service Unavailable), 504 (Gateway Timeout), 507 (Insufficient Storage), 511 (Network Auth Required) are officially registered.
What is the 418 code?
An April fools joke from RFC 2324 (Hyper Text Coffee Pot Control Protocol). Some APIs use it as an Easter egg or to humorously reject invalid requests.
Is the list updated regularly?
Yes — all IANA-registered status codes are included. New codes (e.g. 103 Early Hints, standardized 2017) are added promptly.
Related tools
Continuous monitoring vs. one-shot?
XICTRAQ monitors uptime, SSL, security headers, GDPR and performance 24/7. Free plan, no credit card.