Suped

How to write DMARC monitoring into an MSP proposal

Published 7 Jul 2026
Updated 8 Nov 2026
12 min read
Summarize with
DMARC monitoring in an MSP proposal, illustrated with an email envelope, DNS tag, shield, and report.
Updated on 8 Nov 2026: We added enforcement acceptance criteria and rollback wording, with clearer reporting limits and service responsibilities.
DMARC monitoring belongs in an MSP proposal as a managed email authentication service. The proposal should define discovery, DNS record changes, source authorization, policy staging, alerting, monthly reporting, and support responsibilities. It should also state what the client must approve, which mail sources are in scope, and what happens before the domain moves to p=reject.
For MSP owners, the commercial value sits in the operational work: finding every legitimate sender, fixing broken SPF and DKIM, reducing the successful delivery of spoofed mail, and proving progress over time. The broader DMARC for MSPs model works because DMARC produces ongoing evidence and recurring exceptions, with a clear reporting cadence.
Write the proposal around client outcomes first, then map those outcomes to service delivery. That keeps the proposal concrete and avoids selling acronyms. The client sees what changes, who does the work, how risk goes down, and how they will know the service is working.

Start with the outcome clients understand

A good DMARC proposal starts with the business problem: attackers can send messages that use the client's domain in the visible From address. DMARC lets the domain owner request how receivers handle messages that fail DMARC and provides reporting for review. A DMARC pass requires SPF or DKIM to pass with its authenticated domain matching the visible From domain under the configured alignment mode, as defined in RFC 9989. Lead with domain protection and evidence that approved systems authenticate correctly.
The proposal should commit to managed progression toward DMARC enforcement, with testing to reduce disruption to legitimate mail. Publishing a record alone does not tell you whether payroll, CRM, ticketing, marketing, invoicing, and line-of-business systems are authenticated. Do not guarantee inbox placement. Correct authentication and alignment remove one cause of filtering, but DMARC does not control every deliverability decision. DMARC does not stop lookalike-domain impersonation or abuse through a compromised account that passes authentication.
  1. Outcome: Reduce successful delivery of mail that spoofs the client's domain through monitored DMARC policy progression.
  2. Visibility: Identify legitimate and unknown senders using aggregate DMARC data and source review.
  3. Control: Fix SPF, DKIM, and domain alignment issues before enforcement affects valid mail.
  4. Reporting: Show monthly progress, remaining exceptions, and recommended next actions.
Approve enforcement after validation
Do not promise immediate enforcement unless discovery is complete. Write enforcement as a staged goal with explicit checkpoints, because some clients have mail sources that nobody documented during onboarding.

Define the scope before the technical work

Scope is where many MSP proposals get weak. A DMARC service touches DNS, identity, mail platforms, third-party senders, client approvals, and incident handling. If those boundaries are vague, the service turns into unpaid cleanup.
The proposal should name the domains, the records you manage, the reporting period, the policy target, and the support channel. If the client has subsidiaries or parked domains, state whether those domains are included or require a separate onboarding step.
In scope
  1. Domains: Primary sending domains and agreed subdomains listed in the proposal.
  2. Records: DMARC, SPF, DKIM, and related DNS entries needed for authentication.
  3. Operations: Monitoring, issue triage, sender review, alerts, and recurring reports.
  4. Policy: A staged move through none, quarantine, and reject when data supports it.
Out of scope unless added
  1. Unknown apps: Remediation for undisclosed software beyond the included triage and sender-review allowance.
  2. Vendor work: Custom integration work inside third-party systems outside managed access.
  3. Legal review: Compliance attestations beyond the service report unless separately agreed.
  4. Bulk cleanup: Historical domain consolidation, abandoned systems, and brand governance.
Keep client-specific scope and delivery milestones in the statement of work (SOW). Reference the master services agreement (MSA) for the recurring relationship terms. A useful companion is a DMARC service scope that lists responsibilities before the client signs.

Run discovery before quoting the work

A proposal written before discovery should use cautious language. You can still sell the service, but the first phase should be assessment. That protects margin because the hardest part of DMARC is usually identifying and validating every legitimate sender.
Check the domain's current authentication state before writing the proposal. Suped's domain health checker checks published SPF and DMARC records and DKIM keys at common selectors. A missing DKIM result needs a lookup using the sender's actual selector. Test real messages to verify signing and domain alignment; a DNS scan alone does not establish DMARC readiness.
?

What's your domain score?

Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.

Discovery should produce a short list of client-specific risks. That list becomes proposal evidence. Instead of saying DMARC is important, show that the client's domain has no enforcement policy, missing DKIM on a sender, SPF lookup risk, or no reporting address.
Cloudflare DNS records screen showing DMARC, SPF, and DKIM entries.
Cloudflare DNS records screen showing DMARC, SPF, and DKIM entries.
  1. Current policy: Record each domain's effective DMARC policy, including subdomain coverage, and verify that reports are being collected.
  2. Known senders: List mail platforms, apps, devices, ticketing tools, and finance systems, with a business owner for each sender.
  3. DNS access: Confirm who can approve and publish authentication changes.
  4. Risk items: Note SPF lookup pressure, missing DKIM, and unauthenticated sources.
Demo prospecting report findings page showing email security score, risk level, and DMARC, SPF, and DKIM findings
Demo prospecting report findings page showing email security score, risk level, and DMARC, SPF, and DKIM findings

Write the implementation phases

The proposal should split implementation into phases. This makes the work easier to approve and manage. A client does not need every DNS detail, but they do need to understand why enforcement waits until legitimate mail passes DMARC.
DMARC policy stages
A practical proposal should show how the domain moves through policy stages after evidence improves.
Observe
p=none
Collect reports, identify sources, and fix authentication gaps.
Contain
p=quarantine
Request quarantine handling after approved senders pass DMARC.
Protect
p=reject
Request rejection when reporting shows legitimate mail is covered.
Maintain
ongoing
Watch for new senders, DNS drift, and authentication failures.
A typical first record should collect aggregate reports and avoid enforcement until the sender inventory is known. Verify that the rua destination can receive and process reports; external destinations also need reporting authorization under RFC 9990. RFC 9989 removed the pct tag, so proposal milestones should use explicit policy changes for a domain or subdomain instead of percentage-based rollout. If the client has many departments or vendors, slow the policy path and make client approvals explicit.
Example starting DMARC record for monitoringtext
_dmarc.example.com TXT v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com
Replace example.com and the reporting address with the client domain and assigned report destination. The destination must process aggregate XML reports; publishing a mailbox address alone does not create a monitoring service.
Implementation language
State that policy progression depends on observed DMARC results, sender owner approval, and successful remediation. That clause prevents the client from expecting p=reject before the environment is ready.

Define acceptance criteria and rollback before enforcement

Define acceptance criteria for each milestone instead of promising enforcement on a fixed day. Choose an observation window that covers the client's normal sending cycle, including infrequent payroll or invoicing runs.

Milestone

Acceptance evidence

Monitoring accepted
Domain and sender inventories have owners, and aggregate reports are arriving at the agreed destination.
Ready for enforcement
Critical senders pass real-message tests. Remaining legitimate-mail failures have a documented resolution before the policy changes.
Change approved
The client approves the target policy and subdomain impact. The ticket records the change window and escalation contact.
Change verified
Test representative mail flows after the change, review subsequent reports, and investigate related service-desk incidents.
Record the evidence and approval for each policy change in the service ticket.
Agree rollback authority before the change. If a policy change causes verified delivery failures for legitimate mail, restore the last approved DMARC policy while fixing the source and keep reporting enabled. DNS caching delays the effect of a rollback; do not promise immediate recovery.

Make responsibilities explicit

DMARC projects stall when the MSP owns the technical work but the client owns the missing business context. The proposal should make responsibility visible. Your team can inspect reports and recommend fixes, but the client often needs to confirm whether a sender is legitimate.

Work item

Owner

Proposal note

DNS access
Shared
Client grants access or approves changes.
Sender review
Shared
MSP flags sources, client confirms use.
Record changes
MSP
MSP publishes approved SPF, DKIM, and DMARC updates.
Policy approval
Client
Client approves quarantine and reject milestones.
Monitoring
MSP
MSP reviews alerts, issues, and monthly reports.
Use simple ownership labels so the client knows where approvals sit.
Suped's product supports this operating model through its MSP and multi-tenancy dashboard. Teams can manage client organizations, domains, authentication status, alerts, and reports in one place, which makes the service easier to deliver through a repeatable workflow.
MSP organizations page showing client organizations, domain counts, email volume, and domain status columns
MSP organizations page showing client organizations, domain counts, email volume, and domain status columns

Set commercial terms and service levels

A managed DMARC proposal needs commercial limits around recurring work. Separate one-time onboarding from ongoing monitoring, then define the response clock, included remediation, client dependencies, and work that requires a change request. Tie the recurring fee to the agreed domain inventory or service bundle so newly added domains do not enter scope by assumption.

Proposal term

What to state

Onboarding fee
Cover discovery, the baseline report, sender inventory, and initial approved DNS work.
Recurring fee
Price the agreed active domains or bundle and state how subdomains and parked domains are counted.
Response target
State covered hours, alert severity, and the escalation contact. Start the response clock at alert creation or receipt of a service request; distinguish acknowledgement from resolution.
Included remediation
Set an included time or change allowance for DNS work and sender coordination.
Client dependency
Pause delivery milestones while required access, sender decisions, or policy approvals remain outstanding.
Change control
Route undisclosed senders, custom vendor work, and extra domains through a written change request that states the fee and schedule impact before approval.
Reporting cadence
Name the reporting period and delivery deadline, such as the fifth business day after each calendar month.
Report data handling
State where report data is stored, who has access, and the retention period. Treat failure reports containing message content as separate scope.
Data and offboarding
Define export format, access removal, and transfer of reporting destinations. Preserve SPF, DKIM, and the agreed DMARC policy; replace hosted dependencies before ending the service.
Adapt each term to the MSP's staffing model and contract.
Set the response clock carefully
Do not promise 24/7 response for DMARC changes unless the service is staffed for it. Aggregate reports usually cover a daily reporting period and are not a real-time incident feed. Measure MSP response from alert creation or report receipt, not from the time an underlying message was sent.

Add reporting and success metrics

Reporting should be part of the proposal, with completed work and remaining client decisions visible. A DMARC report should show authorized mail volume, authentication results, unresolved sources, policy status, and recommended next actions. Separate sender authorization from authentication results: a known sender still needs remediation if its legitimate mail fails DMARC. Investigate failures before classifying a source as unauthorized; forwarding and mailing-list changes also cause authentication failures.
Illustrative sender classification over time
Illustrative percentages of reported message volume, using invented data. Sender authorization requires client review. Actual results and enforcement timing depend on the client's mail sources.
Authorized
Needs review
Unauthorized
Unknown
Good reporting also gives account managers a reason to speak with clients about security progress. If the client has executive or board reporting and compliance needs, add a monthly or quarterly summary. A separate guide to DMARC progress reports can help turn raw authentication data into client-ready updates.
Demo client report summary page showing total emails, authorized delivery, threats blocked, and email volume trend
Demo client report summary page showing total emails, authorized delivery, threats blocked, and email volume trend
  1. Authentication: Show SPF and DKIM results plus DMARC pass rates by source. Calculate legitimate-mail pass rates using reported messages from confirmed legitimate senders, separate from suspected spoofing.
  2. Policy: Show the current policy, target policy, and decision needed for the next stage.
  3. Exceptions: List sources still needing remediation or business owner confirmation.
  4. Reputation: Include blocklist (blacklist) findings only when reputation monitoring is part of the agreed scope.
Aggregate reports cover participating receivers and do not prove inbox placement or the total number of attacks blocked. Set expectations using RFC 9990 and record any gaps in report coverage.

Use proposal language clients can sign

Effective proposal wording is specific enough for delivery and plain enough for a non-technical buyer. It should not read like a DNS tutorial. It should describe a managed service with clear phases, acceptance points, and exclusions.
Sample proposal wordingtext
Managed DMARC monitoring and enforcement We will monitor DMARC aggregate reports for the agreed client domains, review sending sources with client-nominated owners, and recommend required SPF, DKIM, and DMARC changes. We will stage DMARC policy changes after the agreed acceptance criteria are met and the client approves the policy milestone. Unknown sources will be investigated before being classified as unauthorized. The service includes issue triage, DNS change recommendations, sender review support, alert review, and monthly reporting. Client approval is required for new sender authorization, client-controlled DNS changes, and movement to quarantine or reject policy. Before each enforcement change, we will record the change window, escalation contact, and rollback authority. If the change causes verified delivery failures for legitimate mail, we will restore the last approved DMARC policy while remediation continues and keep reporting enabled. DNS caching affects how quickly a rollback takes effect. Monitoring does not guarantee inbox placement, complete receiver report coverage, or prevention of all email impersonation. Fees, response targets, reporting deadlines, and exclusions are defined in the statement of work.
If you offer tiered service packages, define each tier by included work. Entry tiers can cover monitoring and reports. Higher tiers can include active remediation, authentication-related DNS management, policy staging, and executive reporting.
Contract wording that protects delivery
Add a clause that new sending services must be reported to the MSP before use. This reduces surprise failures after the domain reaches p=quarantine or p=reject.

Where Suped fits in the service

Suped is our DMARC reporting and email authentication platform. MSPs can use Suped to monitor client domains, triage reported authentication issues, manage approved hosted records, and prepare client reports.
Describe Suped's product as the management layer for DMARC monitoring, source review, and reporting. When the client needs policy management without repeated DNS edits, hosted DMARC lets the MSP stage approved policy changes after the initial DNS delegation. Policy approval and verification remain part of the MSP workflow.
MSP delivery responsibilities
  1. Data: Review aggregate reports and confirm source ownership with the client.
  2. Alerts: Define review frequency and escalation rules for reported failures.
  3. Scale: Keep a sender inventory and change log for each client.
  4. Reporting: Record completed remediation and pending approvals in each update.
Suped product workflow
  1. Data: DMARC, SPF, DKIM, source, and issue views sit in one platform.
  2. Alerts: Configured alerts help the team react when new report data shows a problem.
  3. Scale: MSP dashboards support multiple clients and domains.
  4. Reporting: Client reports turn authentication progress into a repeatable review.
The proposal should describe the MSP's managed service and specify which Suped capabilities are included. Keep optional hosted SPF and blocklist (blacklist) monitoring explicit in the scope and recurring fee.

Frequently asked questions

It should include named domains, discovery, sender review, policy milestones, acceptance criteria, and rollback authority. Define the monitoring and remediation work, reporting deadline, fees, service levels, exclusions, and client responsibilities in the SOW.

Sell initial setup as a project phase if needed, but sell monitoring, issue review, sender changes, reporting, and policy maintenance as a managed service. New senders and DNS drift make DMARC an ongoing responsibility.

Commit to a managed path toward enforcement. Move to reject after the agreed legitimate-sender checks pass and the client approves the policy change, with an agreed rollback process. A high overall pass rate alone is not an acceptance criterion.

The MSP can prepare and apply changes where it has access, but the client should approve material policy changes, new sender authorization, and moves to quarantine or reject. Put that approval process in the proposal.

Measure acknowledgement after an alert is created, a report reaches the monitoring service, or a service request arrives. State covered hours, priority definitions, escalation contacts, client dependencies, and remediation limits. Track resolution separately; receivers deliver aggregate reports on their own schedules.

Suped is our DMARC reporting and email authentication platform. MSPs can manage client domains in separate organizations, review reported authentication issues, configure alerts, and prepare reports. Include hosted DMARC, hosted SPF, or blocklist (blacklist) monitoring only where agreed in the service scope.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing