Ctrl+K
Popular searches:
UtilStation

HTTP Status Codes

v1.0.0

HTTP Status Codes

Complete reference for HTTP response status codes with descriptions, use cases, and categories.

Warning

This tool is not supported on mobile devices, please use a desktop device for better experience.

Export CSV:
1xx
Informational
4
status codes
2xx
Success
7
status codes
3xx
Redirection
7
status codes
4xx
Client Error
29
status codes
5xx
Server Error
11
status codes
Total Status Codes
58
HTTP status codes
Most Common
200, 404, 500
Frequently encountered
Showing
58
Filtered results
CodeNameCategoryDescriptionActions
100Continue
1xx
The server has received the request headers and the client should proceed to send the request body.
101Switching Protocols
1xx
The requester has asked the server to switch protocols and the server has agreed to do so.
102Processing
1xx
The server has received and is processing the request, but no response is available yet.
103Early Hints
1xx
Used to return some response headers before final HTTP message.
200OK
2xx
The request was successful and the server has returned the requested data.
201Created
2xx
The request was successful and a new resource has been created as a result.
202Accepted
2xx
The request has been accepted for processing, but the processing has not been completed.
203Non-Authoritative Information
2xx
The request was successful but the information may be from a cached or third-party source.
204No Content
2xx
The request was successful but there is no content to return.
205Reset Content
2xx
The request was successful and the client should reset the form that caused the request.
206Partial Content
2xx
The server is delivering only part of the resource due to a range header sent by the client.
300Multiple Choices
3xx
The request has more than one possible response and the user should choose one.
301Moved Permanently
3xx
The URL of the requested resource has been changed permanently.
302Found
3xx
The URI of the requested resource has been changed temporarily.
303See Other
3xx
The server is redirecting the user agent to a different resource.
304Not Modified
3xx
The resource has not been modified since the last request.
307Temporary Redirect
3xx
The request should be repeated with another URI but future requests should still use the original URI.
308Permanent Redirect
3xx
The request and all future requests should be repeated using another URI.
400Bad Request
4xx
The server cannot process the request due to invalid syntax or other client error.
401Unauthorized
4xx
The request requires authentication or the authentication provided is invalid.
402Payment Required
4xx
Reserved for future use. Originally intended for digital payment systems.
403Forbidden
4xx
The server understood the request but refuses to authorize it.
404Not Found
4xx
The server can not find the requested resource.
405Method Not Allowed
4xx
The request method is not supported for the requested resource.
406Not Acceptable
4xx
The server cannot produce a response matching the list of acceptable values.
407Proxy Authentication Required
4xx
The client must authenticate itself with the proxy before the request can be processed.
408Request Timeout
4xx
The server timed out waiting for the request.
409Conflict
4xx
The request conflicts with the current state of the target resource.
410Gone
4xx
The target resource is no longer available at the origin server.
411Length Required
4xx
The server requires a Content-Length header field in the request.
412Precondition Failed
4xx
One or more conditions in the request header fields evaluated to false.
413Payload Too Large
4xx
The request entity is larger than limits defined by server.
414URI Too Long
4xx
The URI requested by the client is longer than the server is willing to interpret.
415Unsupported Media Type
4xx
The media format of the requested data is not supported by the server.
416Range Not Satisfiable
4xx
The range specified by the Range header field cannot be fulfilled.
417Expectation Failed
4xx
The expectation indicated by the Expect request header field cannot be met.
418I'm a teapot
4xx
The server refuses the attempt to brew coffee with a teapot (April Fools' joke).
421Misdirected Request
4xx
The request was directed at a server that is not able to produce a response.
422Unprocessable Entity
4xx
The request was well-formed but was unable to be followed due to semantic errors.
423Locked
4xx
The resource that is being accessed is locked.
424Failed Dependency
4xx
The request failed because it depended on another request that failed.
425Too Early
4xx
The server is unwilling to risk processing a request that might be replayed.
426Upgrade Required
4xx
The server refuses to perform the request using the current protocol.
428Precondition Required
4xx
The origin server requires the request to be conditional.
429Too Many Requests
4xx
The user has sent too many requests in a given amount of time.
431Request Header Fields Too Large
4xx
The server is unwilling to process the request because header fields are too large.
451Unavailable For Legal Reasons
4xx
The server is denying access to the resource as a consequence of a legal demand.
500Internal Server Error
5xx
The server has encountered a situation it doesn't know how to handle.
501Not Implemented
5xx
The request method is not supported by the server and cannot be handled.
502Bad Gateway
5xx
The server got an invalid response while working as a gateway to get a response.
503Service Unavailable
5xx
The server is not ready to handle the request due to temporary overload or maintenance.
504Gateway Timeout
5xx
The server is acting as a gateway and did not get a response in time.
505HTTP Version Not Supported
5xx
The HTTP version used in the request is not supported by the server.
506Variant Also Negotiates
5xx
The server has an internal configuration error.
507Insufficient Storage
5xx
The server is unable to store the representation needed to complete the request.
508Loop Detected
5xx
The server detected an infinite loop while processing the request.
510Not Extended
5xx
Further extensions to the request are required for the server to fulfill it.
511Network Authentication Required
5xx
The client needs to authenticate to gain network access.

  • Encode and decode URLs with support for both standard URI encoding and component encoding methods.

  • ASCII Table
    Similar tool

    Complete ASCII character reference table with decimal, hexadecimal, binary, and octal values.

  • HTML Entities
    Similar tool

    Complete HTML character entity reference with symbols, special characters, and escape codes.

  • Country Codes
    Similar tool

    Comprehensive reference for ISO country codes with flags, names, and regional information.

  • MIME Types
    Similar tool

    Complete reference for MIME types and file extensions used in web development and file handling.

  • Port Numbers
    Similar tool

    Comprehensive reference for network port numbers, protocols, and services used in networking and development.

  • CSS Color Codes
    Similar tool

    Complete CSS color reference with hex, RGB, HSL values, and visual previews for web development and design.

  • Meta Tag Generator
    Similar tool

    Generate essential meta tags for better SEO including title, description, keywords, and Open Graph tags.

What are HTTP Status Codes?

HTTP status codes are three-digit numbers returned by web servers to indicate the outcome of HTTP requests. They provide essential information about whether a request was successful, encountered an error, or requires additional action. Understanding these codes is crucial for web developers, API designers, and anyone working with web technologies.

HTTP Status Code Categories

HTTP status codes are organized into five main categories based on their first digit:

🔵 1xx - Informational Responses

These codes indicate that the request was received and is being processed. They are interim responses and rarely seen in everyday web browsing. Common examples include 100 Continue and 101 Switching Protocols.

✅ 2xx - Success Responses

Success codes indicate that the request was successfully received, understood, and processed. The most common is 200 OK, but others like 201 Created and 204 No Contentare frequently used in APIs.

🔄 3xx - Redirection Responses

Redirection codes indicate that further action is needed to complete the request.301 Moved Permanently and 302 Found are commonly used for URL redirects, while 304 Not Modified is important for caching.

❌ 4xx - Client Error Responses

Client error codes indicate that the request contains bad syntax or cannot be fulfilled. The famous 404 Not Found belongs to this category, along with 400 Bad Request,401 Unauthorized, and 403 Forbidden.

💥 5xx - Server Error Responses

Server error codes indicate that the server failed to fulfill a valid request.500 Internal Server Error is the most common, while 502 Bad Gatewayand 503 Service Unavailable often indicate infrastructure issues.

Features of Our HTTP Status Code Reference

Our comprehensive reference tool provides:

  • Complete Coverage: All standard HTTP status codes from 100 to 511
  • Category Filtering: Filter by status code category (1xx, 2xx, 3xx, 4xx, 5xx)
  • Smart Search: Search by code number, name, or description
  • Visual Categories: Color-coded badges for easy category identification
  • Detailed Descriptions: Clear explanations of what each code means and when it's used
  • Export Functionality: Download the filtered results as CSV for reference
  • Copy Features: Quick copy buttons for codes and names

Common HTTP Status Codes

🎯 Most Frequently Encountered
  • 200 OK: The request succeeded and the response contains the requested data
  • 404 Not Found: The requested resource could not be found on the server
  • 500 Internal Server Error: The server encountered an unexpected condition
  • 301 Moved Permanently: The resource has permanently moved to a new URL
  • 403 Forbidden: The server understood the request but refuses to authorize it
📱 API Development Essentials
  • 201 Created: A new resource has been successfully created
  • 204 No Content: Request succeeded but there's no content to return
  • 400 Bad Request: The request syntax is invalid or malformed
  • 401 Unauthorized: Authentication is required or has failed
  • 422 Unprocessable Entity: Request is well-formed but contains semantic errors
  • 429 Too Many Requests: Rate limiting is in effect

Best Practices for Using HTTP Status Codes

🔧 For Web Developers
  • Use Appropriate Codes: Choose the most specific status code for each situation
  • Consistent Error Handling: Implement consistent error responses across your application
  • Client-Side Handling: Handle different status code categories appropriately in your JavaScript
  • SEO Considerations: Use proper redirect codes (301 vs 302) for search engine optimization
🌐 For API Design
  • RESTful Conventions: Follow REST conventions for CRUD operations
  • Error Documentation: Document which status codes your API returns
  • Rate Limiting: Use 429 for rate limiting with appropriate headers
  • Validation Errors: Use 422 for semantic validation errors

Historical Context and Standards

HTTP status codes were first defined in HTTP/1.0 (RFC 1945) and expanded in HTTP/1.1 (RFC 2616). The system has proven so useful that it's been adopted beyond HTTP, appearing in APIs, web services, and even some database systems. The three-digit format allows for clear categorization while providing specific error information.

How to Use This Reference Tool

  1. Browse All Codes: Scroll through the complete list of HTTP status codes
  2. Filter by Category: Use the dropdown to focus on specific categories (1xx-5xx)
  3. Search Functionality: Type to search by code, name, or description
  4. Quick Copy: Use copy buttons to quickly copy codes or names
  5. Export Data: Download filtered results as CSV for offline reference
  6. Category Overview: View the distribution of codes across categories

Fun Facts

  • 418 I'm a teapot: An April Fools' joke from 1998 that became an official status code
  • 451 Unavailable For Legal Reasons: Named after Ray Bradbury's "Fahrenheit 451"
  • Status Code 420: Not officially assigned to avoid legal complications
  • Most Unused Range: 1xx codes are rarely seen by end users

Try Our HTTP Status Code Reference

Whether you're debugging API responses, designing web applications, or learning about HTTP, our status code reference provides all the information you need in a searchable, organized format. Perfect for developers, system administrators, and anyone working with web technologies.