Use case

Roll out and monitor DMARC for every client domain

Publishing a DMARC record with p=none takes two minutes. Getting fifty clients to p=reject without invoices, newsletters or ticket emails vanishing somewhere is a project. DomainWarn collects the reports per client domain, tells you when the next step is safe, and afterwards reports every change to the records.

Every feature, no credit card, cancel monthly.

Why DMARC gets stuck at p=none

  • Nobody reads the reports

    The rua address points to a mailbox where XML attachments from Google and Microsoft pile up daily. Without analysis nobody knows which senders fail.

  • Unknown senders

    The client uses a newsletter tool, a CRM and a ticket system the provider has never heard of. Moving to reject too early locks out exactly those emails.

  • One domain at a time

    Every client has a different DNS provider and a different starting point. Without an overview the rollout stalls after the first five domains.

A report address per client domain

DomainWarn provides a dedicated address for DMARC aggregate reports for every domain. Add it as rua to the client's DMARC record and the first reports arrive within a day. The analysis shows per domain: message count, alignment rate, the reported policy, unaligned messages per day, and every source with its DKIM, SPF and alignment result plus what the receiver did with the messages.

Reports from an existing mailbox can be uploaded by hand as XML, GZ, ZIP or a whole email. The same address accepts TLS-RPT reports, which show whether other mail servers reach the client's servers over TLS.

The DMARC assistant: the next step once it is safe

The assistant classifies every source, separates obvious forgeries without any authentication from legitimate mail, and only recommends moving from none through quarantine to reject when the data supports it:

  • at least 14 days of reports before the first step and 7 days since every further change,
  • at least 100 analysed messages,
  • at least 98 percent of legitimate mail passes DMARC,
  • no legitimate-looking sender fails to a notable degree, such as a newsletter service that only signs with its own domain.

One-click records, even at ten lookups

With the client's DNS provider connected, you apply the proposed record with one click after preview and confirmation. DomainWarn only changes p, pct and sp of the one existing DMARC record and aborts if it changed since the preview. Missing DMARC, SPF and TLS-RPT records are created from the finding in the same way; nine providers are supported, including Cloudflare, Hetzner, IONOS, INWX and Route 53.

If a client's includes exceed the limit of ten DNS lookups, SPF flattening (from the Freelancer plan) keeps the record below it: DomainWarn resolves the includes into networks and keeps them current.

Afterwards: watch what changes

The work is not over at p=reject. The client signs up for a new tool, someone adds a second SPF record, a DKIM key is rotated at the provider. DomainWarn checks SPF, DKIM, DMARC and MX continuously, reports every change with before and after, and the reports show when a new source appears that does not pass.

You can evidence this per client: the compliance report (from Agency) maps SPF, DKIM and DMARC to the requirements of BSI TR-03182, and the check report records the state of a domain with a date and report number. Both are technical checks from the outside, not a certification.

Recommended plan

Agency: DMARC as a service per client

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

Agency checks SPF and DMARC hourly and includes monthly and compliance reports per client, client access and the ticket integrations with NinjaOne and PSA systems (beta). SPF flattening and the check report are already part of Freelancer. Reports with your own logo (white label) come with Agency Pro.

Compare all plans in detail

Rollout per client

  1. Add the domain and put the report address into the DMARC record as rua, starting with p=none.
  2. Collect reports for two weeks and fix SPF and DKIM for legitimate senders that fail.
  3. Follow the assistant's steps: quarantine, then reject, in stages via pct if needed.
  4. Keep monitoring and show the client the state in the report.

Check a client domain's DMARC record

The DMARC checker shows policy, pct, report addresses and syntax errors of a record, with recommendations for the path to p=reject. Free, no sign-up.

Frequently asked questions

Does DomainWarn analyse DMARC reports?
Yes. Every domain gets a report address for aggregate reports; the analysis shows sources, alignment and what receivers did with the messages. Reports you upload by hand are included in the same way.
How long does it take to get from p=none to p=reject?
That depends on the client's mail. The assistant requires at least 14 days of reports before the first step and 7 days after every change; with a few well-configured senders it takes some weeks, with many unknown services longer.
Does the client have to do anything?
They need to know which services send email in their name and, where needed, enable DKIM for their domain there. You set the DNS records, with one click if the DNS provider is connected.
Is DomainWarn a replacement for a dedicated DMARC service?
For rolling out and monitoring DMARC across many client domains, yes. If you are looking for report analysis only, you also get monitoring of DNS, certificates, website and domain in the same tool here.
Does NIS2 require DMARC?
NIS2 does not name DMARC explicitly but requires state-of-the-art measures for secure communication. The German BSI describes SPF, DKIM and DMARC in TR-03182. Whether a client is in scope and what they must implement is a question for legal advice, not for this tool.