Use case

Evidence NIS2 and email security for your clients

Since NIS2, clients ask their IT providers and agencies for evidence: is our email secured, are our domains monitored, what of that can be shown? DomainWarn checks what can be checked from the outside, maps it to the requirements and turns it into a report per client. What it cannot do is stated just as clearly.

Every feature, no credit card, cancel monthly.

Between directive and DNS record

  • The requirement is abstract

    The directive says "cryptography" and "secured communications". Day to day that means TLS on the mail server, DNSSEC, SPF, DKIM, DMARC. Someone has to do the translation.

  • A screenshot is not evidence

    Today's state says nothing about the state in March. Whoever is asked needs a date, a result and something that can be verified.

  • Clients want a simple answer

    "Are we NIS2 safe?" cannot be answered with yes. What can be answered is which technical points are met and which are open.

What can be evidenced from the outside

Article 21(2) of the NIS2 Directive lists risk management measures that entities in scope must implement. Most are organizational and invisible from outside: policies, training, continuity plans, supplier management. Some leave traces that can be measured, and DomainWarn maps its check results to those:

  • Cryptography and secured communications: TLS version and certificate on website and mail server, HSTS, DNSSEC, DANE.
  • Email authentication: SPF, DKIM and DMARC with a policy that actually protects.
  • Operations and vulnerabilities: reachable name servers, CAA, outdated CMS versions, open items from the running checks.
  • Incident detection: whether the domain is monitored continuously and incidents are reported, plus a security.txt as a contact route.

BSI TR-03108 and TR-03182 as the yardstick

For email, the German Federal Office for Information Security (BSI) has published two technical guidelines: TR-03108 for secure transport between mail servers and TR-03182 for sender authentication. DomainWarn checks criteria based on these guidelines: STARTTLS, TLS version and certificate of the mail server, DNSSEC of the domain and of its mail servers' zone, DANE, MTA-STS, TLS-RPT, and SPF, DKIM and DMARC with quarantine or reject and a report address.

Domains that send no email are covered too: for them it counts whether null MX, "v=spf1 -all" and DMARC reject lock them against spoofing. If the mailboxes are at Microsoft 365, implicit TLS for mail clients only appears as a note because it cannot be configured there.

The compliance report per client

From the Agency plan the compliance report is available per domain and for all domains of a client, as a PDF. For each requirement it states met, partly met, not met or not verifiable, with evidence and a recommendation. "Not verifiable" is a result of its own: if a check is switched off or the domain receives no email, the report claims nothing.

Client logins see the report for their own domains. In Agency Pro it carries your logo and colour.

Check report with report number, and seal

For the email security of a domain you create a dated check report at the push of a button: a unique report number, the check date, the result in the form "13 of 14 criteria met" and every criterion with its outcome. A QR code and a link lead to a verification page that shows the state at the time of the check. The report is never altered afterwards and is kept for 13 months.

The "Email security checked" seal can be issued for client domains and embedded on the client's website. It is only valid while the latest check report is at most 48 hours old and all counted criteria are met; DomainWarn re-checks daily for that. If a check fails, the image shows "no longer valid". Check report and seal are part of all paid plans.

What these reports are not

Compliance report, check report and seal are based on an automated check from the outside. They are not a certification by the BSI, do not confirm conformity with a technical guideline or with NIS2, and do not replace an audit. DomainWarn cannot see organizational measures, internal systems or outbound mail servers.

Whether a company falls under NIS2 and which duties follow is a legal question. DomainWarn gives no advice on that; the reports are a technical basis for the conversation with the client, an auditor or legal counsel.

Recommended plan

Agency: compliance report per client

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

Like the monthly report, the compliance report is included from Agency. The check report and the "Email security checked" seal are available from Freelancer and during the trial. The two quick checks for a single domain are free and need no account.

Compare all plans in detail

From quick check to evidence

  1. Run the free quick check on the client domain and note the open items.
  2. Add the domain to monitoring and create missing records, with one click if the DNS provider is connected.
  3. Pull the compliance report for the client and create a check report for email security.
  4. Renew the report regularly: monitoring tells you when a criterion slips.

Check the email security of a domain

The quick check tests STARTTLS, DANE, DNSSEC, TLS-RPT, SPF, DKIM and DMARC with criteria based on BSI TR-03108 and TR-03182 and gives a recommendation per criterion. Free, no sign-up.

Frequently asked questions

Does DomainWarn make a company comply with NIS2?
No. NIS2 mainly requires organizational measures that no tool can check or create from the outside. DomainWarn shows which of the technically measurable points are met and keeps monitoring them.
Does NIS2 mandate SPF, DKIM and DMARC?
The directive names no specific mechanisms. It requires state-of-the-art measures, including for cryptography and secured communications. The BSI technical guidelines describe what that looks like for email. What is mandatory in a given case is a matter for legal advice.
Is the check report an attestation by the BSI?
No. It is an automated check from the outside by DomainWarn, with criteria based on BSI TR-03108 and TR-03182. It records which criteria were met at the time of the check.
How are criteria counted when one does not apply?
Criteria that do not apply and pure notes are not counted, nor is MTA-STS, which the guideline only lists as an option next to DANE. "Partly met" and "not verifiable" count as not met.
Can my client show the report to an auditor?
As technical evidence, yes: the check report carries a date and a report number and can be verified on the verification page. Which further evidence an auditor asks for is up to them.