Solution by audience

Domain and email monitoring for MSPs

Your RMM knows every server and workstation on a client site. The domain, its DNS, the certificate and the email records live at a registrar, a hosting company or Microsoft 365, where no agent runs. DomainWarn checks that side from the outside for every client and files the alert where your technicians already work: as a ticket in the PSA.

Every feature, no credit card, cancel monthly.

The gap in the RMM

  • No agent at the registrar

    Domain expiry, name servers and the DNS zone sit outside the managed estate. When something breaks there, the RMM only tells you the server is still up.

  • Someone else edits the email records

    A web agency moves the site, the client signs up for a newsletter tool, and an include drops out of the SPF record or the MX points elsewhere. You hear about it as "our email is not arriving".

  • Alerts outside the ticket queue

    One more tool with its own inbox goes unread on a busy day. If it is not a ticket on the right client, it does not get done.

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.

Recommended plan

Agency: the plan with PSA integrations

€49 per month net · 100 domains · 15 team members

NinjaOne and the PSA integrations (beta), monthly reports per client, client access and the audit log start with Agency, and websites are checked every minute. Agency Pro adds more domains, single sign-on and reports in your own design. The 14-day trial unlocks the full scope of Agency Pro.

Compare all plans in detail

Up and running in three steps

  1. Create an account and connect the PSA: companies come in as clients, existing clients are mapped.
  2. Add the domains per client or import them from the zone at the DNS provider. Monitors are created for you.
  3. Create the PSA channel, pick a minimum severity and send a test. From then on each alert becomes a ticket on the right client.

Check a client domain now

The domain check covers website, email, DNS and domain in one run and scores each area. No sign-up needed, which makes it handy for a first call with a prospect.

Frequently asked questions

Does DomainWarn replace an RMM?
No. DomainWarn does not monitor anything that needs an agent: no servers, workstations or patching. It adds the side that is visible from the outside: domain, DNS, certificates, email records and the website.
What does beta mean for NinjaOne and the PSA integrations?
They are fully built on the official APIs but new and not yet long in production use. Each function is switched on separately, and everything is off after connecting. They are included from the Agency plan.
How are clients kept apart?
Each domain belongs to at most one client. Alerts, tickets, reports, the status page and client access hang off the client; a client login only ever sees its own domains and none of your team's notes.
Does DomainWarn monitor DMARC for all client domains?
Yes. SPF, DKIM and DMARC are checked per domain and every change is reported. DomainWarn also provides an address per domain for DMARC aggregate reports and shows which senders pass and which fail.
Where is the data hosted?
DomainWarn runs on IONOS servers in Germany; the encrypted backups are kept with Cloudflare R2 in Western Europe. For your clients’ data, the data processing agreement is a PDF in the dashboard on the Agency Pro plan and available on request on other plans.