HTTP Status Code Lookup
BetaThis tool is in beta. Some features may change or have limited functionality.Look up any HTTP status code to understand what it means, when it's used, and how to fix common errors. Search by code number or description. Covers all 1xx to 5xx status codes with practical examples and solutions.
Results Count
Why Use HTTP Status Code Lookup?
HTTP status codes are the backbone of web communication, but remembering what each code means — especially the less common ones like 422, 429, or 503 — can be a challenge even for experienced developers. Our HTTP Status Code Lookup provides instant access to every standard HTTP status code with clear explanations, real-world use cases, and actionable solutions for error codes. Whether you're debugging an API response or configuring server behavior, this is your quick reference.
Each status code entry includes the code number, its official name, a plain-English description of what it means, typical scenarios where it appears, and for error codes (4xx and 5xx), practical steps to diagnose and resolve the issue. Filter by category — informational (1xx), success (2xx), redirection (3xx), client error (4xx), or server error (5xx) — to browse related codes, or search for any keyword to find the code you need.
Frequently Asked Questions
What are the main categories of HTTP status codes?
HTTP status codes are grouped into five categories: 1xx (Informational) for ongoing requests, 2xx (Success) for successful operations, 3xx (Redirection) for URL changes, 4xx (Client Error) for request problems, and 5xx (Server Error) for server-side failures.
What is the difference between 401 and 403?
A 401 (Unauthorized) means the request lacks valid authentication credentials — the user needs to log in. A 403 (Forbidden) means the server understood the request and the user may be authenticated, but they don't have permission to access the resource.
What does a 502 Bad Gateway mean?
A 502 error means a server acting as a gateway or proxy received an invalid response from an upstream server. This commonly happens when a backend service (like a Node.js or PHP application) crashes or becomes unresponsive while a reverse proxy (like Nginx) is trying to forward requests to it.
Are all HTTP status codes listed here?
Yes. We include all standard HTTP status codes defined in RFC 7231 and related RFCs, plus commonly used non-standard codes like 418 (I'm a Teapot) and 429 (Too Many Requests). Each entry reflects the latest IANA HTTP Status Code Registry.
Can I use this tool when debugging API responses?
Absolutely. When you receive an unexpected status code from an API, search for it here to understand what the server is telling you and what steps to take. The 'How to Fix' section for error codes provides practical debugging guidance.