Outside-in checks for what agents miss
DomainWarn needs no install and no credentials on the client side. Monitors are created automatically for each domain and look at it the way mail servers, browsers and resolvers do:
- Registration via RDAP: expiry date, registrar, status and name servers; a registrar change is reported.
- DNS at the authoritative name server: every change to A, MX, NS, TXT and CAA shows before and after, confirmed on a second name server.
- Email: MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, DANE, blacklists and the mail server itself with STARTTLS and its certificate.
- Website: availability, status code, redirects and the certificate with chain, hostname and days left.
- Certificate Transparency: newly issued certificates for the domain and its subdomains, with a warning for an unknown issuer.
Tickets in NinjaOne, HaloPSA, Autotask and ConnectWise (beta)
From the Agency plan you can connect DomainWarn to NinjaOne, HaloPSA, Autotask or ConnectWise PSA. All four integrations are in beta: they follow the vendors' official APIs but are new, so review the first tickets and mappings.
A new alert opens exactly one ticket per connected system, on the company that owns the domain or, without a mapping, on the default company you set. Reminders and escalations are added as notes on the same ticket: internal notes in NinjaOne, HaloPSA and ConnectWise, and in Autotask with the note type and visibility you choose. On recovery DomainWarn can set the status you picked for it and adds a note. You choose priority per severity and the statuses, plus ticket type (HaloPSA), board (ConnectWise), queue (Autotask) or form (NinjaOne) depending on the system; like any channel, it has a minimum severity.
NinjaOne also gets the domain status on the client record: DomainWarn writes a table with health, expiry date and open alerts into an organization field, so technicians see it inside NinjaOne.
Bring your tenants over from the PSA
Organizations from NinjaOne and companies from HaloPSA, Autotask and ConnectWise can be imported as clients through the integrations (beta) once you have switched on the import for the connection, one by one or all unmapped ones at once. A client with the same name is mapped instead of duplicated, and nothing is ever deleted on either side. In the other direction, the NinjaOne export creates missing organizations.
Team members have roles, with an audit log from Agency and single sign-on through your identity provider in Agency Pro. Maintenance windows per domain or client keep planned migrations out of the alerts.
Evidence and visibility per client
From Agency, each client can get a monthly PDF report: availability, alerts, detected changes, expiring certificates and domains, emailed automatically at the start of the month. The compliance report maps check results to BSI TR-03108, TR-03182 and the NIS2 measures that can be evidenced from the outside; it is a technical indication, not a certification.
Client access shows a client only their own domains, read-only, and does not count towards the member limit. The status page per client works without a login. In Agency Pro, reports carry your logo and colour.
Data for your own monitoring stack
If you run Zabbix, Checkmk, PRTG, Grafana or Uptime Kuma, pull the state of all domains through a Prometheus-format endpoint or the JSON overview. The REST API with tokens is part of every plan, alongside signed webhooks, a calendar feed of expiry dates and a CSV export of the domain list.