HTTP Status Code Reference – Lookup 100–599 Responses
Search any HTTP status code to get category, description, RFC reference, and real-world usage for APIs and websites.
HTTP Status Codes
Reference guide for HTTP status codes
Related tools
Show moreShow more
› About this tool · FAQ
Stop searching for HTTP status code meanings! Complete reference guide with detailed descriptions, usage examples, RFC references, and practical guidance for web developers and API designers. Covers all codes from 100 to 599 with real-world examples. Free, works offline, searchable.
What are the main HTTP status code categories?
1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error). Each category indicates the type of response from the server.
When should I use 422 vs 400?
Use 400 for malformed requests (syntax errors), and 422 for well-formed requests that fail semantic validation (business logic errors).
What's the difference between 401 and 403?
401 means authentication is required or failed (login needed), while 403 means the user is authenticated but lacks permission for the resource.
Which status codes are most commonly used?
Most common: 200 (OK), 201 (Created), 204 (No Content), 301/302 (Redirects), 400 (Bad Request), 401 (Unauthorized), 403 (Forbidden), 404 (Not Found), 422 (Unprocessable Entity), 500 (Internal Server Error), 502 (Bad Gateway), 503 (Service Unavailable).
How do I choose between 301 and 302 redirects?
Use 301 for permanent redirects (SEO juice transfers, caching encouraged) and 302 for temporary redirects (original URL will be used again).