Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Email & DNS

DMARC report reading: turn aggregate XML into useful sender evidence

Published August 2026 · 2 min read · Updated 2026-09-05

DMARC aggregate reports summarize how receivers saw mail claiming to use your domain. They are useful for discovering legitimate senders, alignment failures, and obvious abuse patterns, but the source IP rows need context before you authorize or block anything.

Group by sending source and disposition

Look at source IP, message count, SPF result/alignment, DKIM result/alignment, and policy disposition. Large recurring sources deserve identification first because they affect the most mail.

A receiver may aggregate multiple days or systems differently, so report volume is not a perfect count of mail sent.

Map sources to known services

Compare IP/host ownership and DKIM selectors with mailbox providers, CRMs, newsletters, support platforms, invoicing, websites, and other approved senders. Maintain an internal sender inventory so approved services do not need to be rediscovered during every incident.

Unknown low-volume sources can be abuse, old infrastructure, forwarded mail, or a forgotten legitimate tool.

Distinguish authentication from alignment

A source can pass SPF for its own bounce domain but fail alignment with your From domain. DKIM can pass cryptographically but sign with a provider domain. DMARC cares about aligned pass, so read both dimensions.

Forwarded messages are especially useful when evaluating whether aligned DKIM survives.

Use trends before tightening policy

Fix recurring legitimate failures, watch report volume across a comparable period, and only then raise policy. Keep reports after enforcement so new vendors or regressions are detected.

  • Prioritize high-volume sources.
  • Map selectors/IPs to owners.
  • Separate pass from alignment.
  • Tighten policy only after legitimate senders are clean.

Next step

Read DMARC aggregate reports by source, authentication result and alignment so unknown senders, forwarding and policy problems become actionable.

Explore DotMoose domains and DNS

Keep reading

Related guides.

CAA record planning: control which certificate authorities may issue for a domain

Plan CAA records around the certificate providers you use, subdomains and incident contacts, then verify issuance will still work before enforcing restrictions.

Read the guide

CNAME chain problems: why extra DNS aliases can break or slow resolution

Trace CNAME chains, loops, missing terminal records and provider restrictions, then shorten unnecessary aliases without changing the intended hostname.

Read the guide

DKIM selector rotation: change signing keys without breaking verification

Rotate DKIM selectors by publishing the new key first, switching signers, monitoring authentication and retaining the old selector long enough for queued mail.

Read the guide

More domains & dns guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move