xlnszia Docs App
Self-hosted test monitoring

xlnszia Documentation

Watch your SSL/TLS certificates and DNS records, track status over time, and get alerted when something goes wrong — with teams, role-based access control, integrations and a real-time event stream.

Usage Guide Design system

Quick start

  1. 1

    Sign in

    Open https://app.xlnszia.com and sign in with your email address and password.

  2. 2

    Create a test

    Add an SSL expiry or DNS resolution test and assign it to a team and environment.

  3. 3

    Set up alerting

    Create an alert rule so you are notified when a test fails.

  4. 4

    Monitor

    Watch the dashboard and the real-time event stream.

See the Usage Guide for the full walkthrough.

Endpoints

EndpointPurpose
https://xlnszia.comPublic landing page
https://app.xlnszia.comThe application (web UI)
https://api.xlnszia.comThe REST API (versioned under /api/v1)
https://api.xlnszia.com/api/healthHealth check (unversioned)
https://docs.xlnszia.comThis documentation

What you can do

Tests

Monitor SSL/TLS certificate expiry and DNS resolution.

Alerts

Rules that fire when a test fails, with severities and notifications.

Teams & roles

Team-based access with granular permissions.

Integrations

Push alerts to Email, Datadog, OpenTelemetry or databases.

API tokens

Personal access tokens for automation.

SSO & roles

Microsoft Entra SSO, SAML role mapping, SCIM.

Test optimization

Enhanced SSL checks, intervals, alerts, retention.

Operations

Scaling for enterprise and high availability.

Troubleshooting

Diagnose failures and tune performance.

API reference

Full endpoint reference at /api/v1.

How it works

  • A background checker wakes up every CHECKER_INTERVAL_SECONDS (default 60s) and verifies each active test.
  • Results update the test's status, are stored as check history, and are pushed to connected browsers over WebSockets.
  • Alert rules fire when their condition matches a check result; fired alerts auto-resolve when the test becomes healthy again.
  • Key Vault secrets (passwords / API keys used by integrations) are stored encrypted with Fernet.
  • Every meaningful action is written to the audit trail.