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.

​
Request format

Custom Status is accessed through a simple HTTP request with a single query parameter. 
https://status.utnor.org/?status={status_code}

​
Properties

​
status
integer
required
The HTTP status code you want the server to return.If the value is missing, invalid, or unsupported, the request will return an error response.
The status code must be between 200 and 599.

​
Example requests

Custom Status can be used from any platform or environment that can send an HTTP request. It is not tied to a specific language, framework, or tool. The examples below show a few common ways to call the tool. They are provided only as reference — any CLI, programming language, or HTTP client can be used. 
curl -i https://status.utnor.org/?status=404

​
Response behavior

When the request is valid, the response is intentionally minimal. 
HTTP/1.1 {status_code} {reason_phase}

​
What the response includes

  • The requested HTTP status code
  • Standard HTTP headers required to deliver the response

​
What the response does not include

  • No response body
  • No JSON payload
  • No message string
  • No metadata or diagnostics
This design keeps the focus on how your client reacts to the HTTP status itself.

​
Success vs error responses

If the provided status value is valid and supported, the server responds using that status code directly. If the value is invalid, missing, or outside the allowed rules, the server returns an error response instead. Error responses include a small JSON body explaining what went wrong.
Detailed error formats and meanings are documented in the Common Errors section.