Skip to content
Example · names and domains are placeholders

What your client receives.

One pack per client, under your name: who sends as each domain and who approved it, what has to be true before enforcement, every exception with its reason, and every record change with its reviewer. Pilot accounts get theirs prepared from their own report data.

Back to the pilot offer
DMARC enforcement readiness

Prepared by Example MSP for Example Clinic

Domains: example.com, example.net, lists.example.net

Prepared on 2026-10-01

Senders

DomainSourceProviderMessages, 30 daysSPFDKIMOwnerApprovedAction
example.comStaff mailboxesMicrosoft 36518,420PassPassIT leadYesNone
example.comPatient remindersPractice management system6,210PassFailPractice managerYesCustom DKIM key requested from the vendor
example.comNewsletterMailchimp2,900PassPassMarketing leadYesNone
example.netInvoicesQuickBooks Online410PassPassOffice managerYesNone
example.netUnknown host, AS64500Not identified37FailFailNot claimedNoNo owner after two requests; treated as unauthorized
lists.example.netStaff posting to an industry listExternal mailing list120FailFailIT leadYesDocumented exception, see below

Readiness checklist

ItemStatusEvidence
DMARC record published with aggregate reportingDoneReports received daily since 2026-08-04
At least 30 days of aggregate reports reviewedDone58 days of reports from 14 receivers
Every sending source identifiedDone6 sources, listed above
Every source has a named owner or is marked unauthorizedDone5 owners named, 1 source unclaimed
The client approved each legitimate sourceDoneApproved by the practice manager on 2026-09-22
SPF aligned for every approved sourceDoneAligned in the last 14 days of reports
DKIM aligned for every approved sourceOpenPatient reminders still sign with the vendor's domain
Mailing-list traffic assessedExceptionlists.example.net stays below reject, see exceptions

Documented exceptions

lists.example.net

Staff post to an external mailing list that rewrites messages, so their mail fails DMARC at the list's recipients. Under reject, those recipients would refuse it.

Policy held at p=quarantine · RFC 9989 section 7.4

DNS changes

DateRecordChangeReviewed by
2026-09-12SPFAdded the newsletter platform's include to example.comService desk lead, approved by the IT lead
2026-09-26DMARCexample.net moved from p=none to p=quarantine after sign-offService desk lead, approved by the practice manager

Sign-off

Client owner
Practice manager, Example Clinic
Approved on
Awaiting sign-off
Signature