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.

A SECURITY_VIOLATION error occurs when a request is temporarily blocked by security or abuse-protection systems. This protection exists to keep the hosted service stable, available, and safe for all users. In most cases, blocks are temporary and are automatically lifted once traffic is considered safe again. Custom Status may return a static JSON response indicating the request was blocked for security reasons.

​
Why this happens

A request may be blocked for reasons such as:
  • Sending too many requests in a short time (rate limiting)
  • Repeated rapid retries
  • Suspicious or malformed request structure
  • Traffic that appears automated or bot-like
  • Network-level filtering by the infrastructure security provider
For hosted deployments, some protections are enforced at the infrastructure layer (for example, edge-level abuse detection and request filtering). Learn more.

​
If you receive this error

If you encounter SECURITY_VIOLATION:
  • Wait briefly and try again.
  • Reduce request frequency if sending many requests.
  • Verify your headers, payload structure, and request format.
  • If a security challenge prompt is shown, complete it to confirm legitimate usage.
False positives can occur. If traffic is later determined to be safe, restrictions are automatically lifted. If the issue persists for an extended period, contact support and include:
  • Full request URL
  • HTTP method
  • Timestamp
  • Any relevant request identifiers
Contact: [email protected]
SECURITY_VIOLATION does not indicate permanent suspension.

​
Data and privacy

Custom Status does not personally collect user data for security enforcement. Security filtering is performed solely to protect service stability and prevent abuse. Custom Status does not add tracking, analytics, or behavioral profiling. Learn more about the Security and Privacy overview.
Detailed security signals are never exposed in API responses. Minimal information is returned intentionally to protect platform integrity.