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.