utilitybelt.dev
Sponsored

HTTP Status Code Reference

A quick, searchable index of all standard HTTP response status codes. Quickly identify the meaning behind 200, 404, 500, and more.

Search & Filter

Ctrl+/

Results (58)

100Continue
101Switching Protocols
102Processing
103Early Hints
200OK
201Created
202Accepted
203Non-Authoritative Information
204No Content
205Reset Content
206Partial Content
300Multiple Choices
301Moved Permanently
302Found
303See Other
304Not Modified
307Temporary Redirect
308Permanent Redirect
400Bad Request
401Unauthorized
402Payment Required
403Forbidden
404Not Found
405Method Not Allowed
406Not Acceptable
407Proxy Authentication Required
408Request Timeout
409Conflict
410Gone
411Length Required
412Precondition Failed
413Payload Too Large
414URI Too Long
415Unsupported Media Type
416Range Not Satisfiable
417Expectation Failed
418I'm a teapot
421Misdirected Request
422Unprocessable Entity
423Locked
424Failed Dependency
425Too Early
426Upgrade Required
428Precondition Required
429Too Many Requests
431Request Header Fields Too Large
451Unavailable For Legal Reasons
500Internal Server Error
501Not Implemented
502Bad Gateway
503Service Unavailable
504Gateway Timeout
505HTTP Version Not Supported
506Variant Also Negotiates
507Insufficient Storage
508Loop Detected
510Not Extended
511Network Authentication Required
Sponsored

What is HTTP Status Code Reference?

HTTP response status codes indicate whether a specific HTTP request has been successfully completed. They are grouped into five classes: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error). Understanding these codes is crucial for debugging web applications, monitoring server health, and building robust API integrations. This reference provides a searchable, categorized index of all standard HTTP status codes with clear descriptions.

Common Use Cases

  • Debugging REST APIs and identifying why a request failed (e.g., 401 Unauthorized vs 403 Forbidden).
  • Writing error-handling logic in frontend code (like Axios or Fetch intercepts).
  • Server administration and parsing access logs.
  • Understanding and troubleshooting HTTP responses during development.

Example: Input & Output

Sample Input

See the tool above for interactive examples.

Expected Output

The processed output will appear here instantly.

How to Use

  1. Step 1: Type an HTTP status code (e.g., '418') into the search bar to instantly jump to its definition.
  2. Step 2: Filter by class (e.g., 'Client Errors') to browse related codes.
  3. Step 3: Click on any code card to expand and read its full description.
  4. Step 4: Use the 'Copy' button to quickly grab the code and name for documentation.

Frequently Asked Questions

What is the difference between 401 and 403?

401 means you are unauthenticated (not logged in), while 403 means you are authenticated but lack permission to access the resource.

What does a 502 Bad Gateway mean?

The server, while acting as a gateway or proxy, received an invalid response from the upstream server. This is often a temporary issue caused by misconfigured proxies or overloaded upstream services.

What is the funny 418 status code?

418 I'm a teapot—an April Fools' joke from 1998 (RFC 2324) that became a permanent part of developer culture.

Is my data secure?

Yes. This tool runs entirely in your browser. No data or search queries are sent to external servers.

Privacy & Security

All data processing for the HTTP Status Code Reference happens entirely on your local machine within your browser. No data is ever sent to our servers, ensuring your information remains private and secure. We believe in privacy by design, and our tools are built to be used without compromising your data.