HTTP Status Codes Reference
Complete reference for all HTTP status codes — search by number or keyword and get plain-English explanations instantly.
HTTP Status Codes
Lookup reference for HTTP status codes.
The request has succeeded.
The request succeeded, and a new resource was created as a result.
There is no content to send for this request, but the headers may be useful.
The URL of the requested resource has been changed permanently.
URI of requested resource has been changed temporarily.
Used for caching purposes. Tells the client that the response has not been modified.
The server could not understand the request due to invalid syntax.
The client must authenticate itself to get the requested response.
The client does not have access rights to the content.
The server can not find the requested resource.
The user has sent too many requests in a given amount of time.
The server has encountered a situation it does not know how to handle.
The server got an invalid response while working as a gateway to get a response.
The server is not ready to handle the request (e.g. down for maintenance).
The server acting as a gateway cannot get a response in time.
Why use our HTTP Status Code Reference?
Complete Reference
All HTTP/1.1 and HTTP/2 status codes from 100 Continue to 599, organized by category.
Instant Search
Search by code number or keyword — find the status code you need in milliseconds.
Plain English Descriptions
Every status code includes a clear description of what it means and when it's used in real APIs.
Category Grouping
Browse by category: 2xx Success, 3xx Redirection, 4xx Client Errors, 5xx Server Errors.
Frequently Asked Questions
What are HTTP status codes?
HTTP status codes are 3-digit numbers that servers return in response to a client's request. They indicate whether the request was successful, redirected, or resulted in an error.
What's the difference between 401 and 403?
401 Unauthorized means the user is not authenticated — they need to log in. 403 Forbidden means the user is authenticated but doesn't have permission to access the resource.
What causes a 500 Internal Server Error?
A 500 error means something went wrong on the server side. It's a generic error that can be caused by unhandled exceptions, misconfigurations, database failures, or bugs in the server code.
Is 301 or 302 better for permanent redirects?
Use 301 for permanent redirects — browsers and search engines will update their cached URL. Use 302 for temporary redirects where the original URL should remain indexed by search engines.
📚 Latest Articles
See moreJSON Formatting Best Practices
Learn how to structure, format, and organize your JSON data for maximum readability and team collaboration.
HTML Beautification Guide
A comprehensive guide on maintaining clean, indented, and professional HTML code in modern web development.
Base64 Encoding Explained
Demystifying Base64 encoding: what it is, how it works, and when to use it securely in your applications.