Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.utnor.com/llms.txt

Use this file to discover all available pages before exploring further.

​

Custom Status does not work with personal data. The tool only reads a single input: the value you provide in the query parameter. That value is used to decide which HTTP status code to return. Nothing else about the request is required for the response to work. There is no concept of users, accounts, sessions, profiles, or identity. Requests are handled independently and then discarded. The tool does not store request history, response history, or behavioral metadata. In simple terms: if it’s not required to return a status code, it isn’t used.

​
Abuse protection on the hosted service

The hosted version of Custom Status includes basic abuse protection to keep the service stable for everyone. This protection may include throttling or rate limiting at the platform edge. These controls are handled by the underlying infrastructure provider rather than by Custom Status itself. For hosted deployments, Cloudflare provides network‑level protections such as request filtering and abuse prevention. If you’re curious about how that data is handled at the infrastructure layer, you can review Cloudflare’s privacy policy directly. Custom Status does not add its own tracking or analytics on top of this.

​
Limitations

HTTP status codes are defined as three‑digit positive integers. This definition comes from the HTTP specifications maintained by the IETF and documented through related standards. The official registry of HTTP status codes is maintained by IANA (Internet Assigned Numbers Authority), which is responsible for coordinating protocol parameters used across the internet. In practice, the hosted platform enforces an additional boundary. Because the service runs on a stateless edge environment, only status codes in the range 200–599 can be returned. Requests outside this range cannot be represented as valid HTTP responses on the platform. When a value falls outside the allowed range, the request results in a range violation error, indicating that the requested status cannot be served. This is a platform constraint, not an interpretation of the HTTP standard.

​
Responsible use

Custom Status exists to help observe how clients behave when a real HTTP response is returned. It is not designed for traffic generation, stress testing, disruption, or any form of harm toward individuals, services, organizations, or infrastructure. Using the tool for abuse or interference goes against its intended purpose. If you need full control over limits, protections, or deployment behavior, you can self‑host the tool in your own stateless environment. The behavior remains the same, while operational controls are entirely yours.