What Are HTTP Status Codes?
HTTP status codes are three-digit numeric responses sent by web servers to indicate the result of a client’s HTTP request. Every browser request, API call, and web service interaction receives a status code — from a simple page load returning 200 OK to a failed authentication returning 401 Unauthorized or a missing page returning 404 Not Found.
Status codes are grouped into five classes, each indicating a different type of outcome:
| Class | Range | Meaning |
|---|---|---|
| 1xx | 100–199 | Informational — request received, processing continues |
| 2xx | 200–299 | Success — request was received, understood, and accepted |
| 3xx | 300–399 | Redirection — further action is needed to complete the request |
| 4xx | 400–499 | Client Error — the request contains bad syntax or cannot be fulfilled |
| 5xx | 500–599 | Server Error — the server failed to fulfil an apparently valid request |
How to Use This Reference Tool
- Search by code number (e.g.
404), status name (e.g.not found), or description keyword (e.g.redirect). - Filter by category using the buttons (1xx, 2xx, 3xx, 4xx, 5xx, Non-Standard).
- Click any card to see the full details: meaning, when to use it, common causes, and a ready-to-use curl example.
- Copy Code + Name with one click — useful for documentation, bug reports, and code comments.
The Most Important HTTP Status Codes
2xx — Success
200 OK is the standard success response. The server returned the requested content. 201 Created is returned after a successful POST that creates a new resource. 204 No Content signals a successful operation (such as a DELETE) with no response body.
3xx — Redirects
301 Moved Permanently tells browsers and search engines that a URL has moved forever — link equity is transferred. 302 Found is a temporary redirect used in the Post/Redirect/Get pattern. 304 Not Modified tells the browser to use its cached version of a resource.
4xx — Client Errors
400 Bad Request indicates malformed syntax or invalid input. 401 Unauthorized means authentication is required or failed. 403 Forbidden means the server understands the request but refuses to authorize it. 404 Not Found is the most recognisable error — the requested resource does not exist. 422 Unprocessable Content signals valid JSON with invalid business logic (common in REST APIs). 429 Too Many Requests is returned by rate-limited APIs.
5xx — Server Errors
500 Internal Server Error is the catch-all for unhandled exceptions. 502 Bad Gateway means a proxy received an invalid upstream response. 503 Service Unavailable signals temporary downtime — often with a Retry-After header. 504 Gateway Timeout indicates the upstream server did not respond in time.
Non-Standard Codes
Beyond the official RFC-defined codes, several vendors and platforms have introduced their own extensions:
- nginx 444 closes a connection without sending any response
- Cloudflare 520–527 signal various issues between Cloudflare’s edge and the origin server
- AWS 460/463 indicate load balancer connection issues
- Laravel 419 is returned when a CSRF token is missing or expired
These codes are widely encountered in production infrastructure and are included in this reference for completeness.
Privacy
This tool runs entirely in your browser using a static JavaScript data set. No search queries, URLs, or status codes are ever sent to a server, stored in cookies, or logged.