How to define scope for a managed DMARC service

Updated on 8 Nov 2026: We clarified managed DMARC service boundaries and added an offboarding checklist to preserve authentication when service ends.
Scope for a managed DMARC service should define the domains covered, the senders reviewed, the DNS changes included, the remediation work performed, the policy milestones, the reporting cadence, and the decisions that stay with the client. Treat it as a delivery contract, not a loose promise to monitor DMARC.
For MSPs, the best scope is narrow enough to deliver repeatably and broad enough to protect the client from spoofing gaps. A good DMARC for MSPs program has a standard service model, then uses client-specific findings to decide which work becomes a project, an add-on, or a client-owned task.
The most common scoping mistake is selling managed DMARC as unlimited remediation. DMARC exposes old tools, forgotten sending systems, weak DNS hygiene, vendor misconfiguration, and client approval delays. Scope should say which of those problems the MSP fixes, which it coordinates, and which it escalates.
What belongs in scope
Start with the service boundary in the statement of work (SOW). That boundary should be visible to sales, onboarding, help desk, engineering, and the client. If each team has a different idea of what managed DMARC includes, tickets become slow and clients expect work that was never priced or resourced.
- Domain coverage: List primary domains, subdomains, aliases, parked domains, and client brands. Document which subdomains inherit a parent policy and which have their own DMARC record.
- Sender review: Identify mailbox platforms, marketing systems, CRMs, billing systems, scanners, websites, and support desks that send as the client.
- DNS work: State whether the MSP edits DNS, prepares records only, or asks the client to approve every change.
- Remediation: Define the included sender fixes or engineering hours per billing period, what counts against that allowance, and when additional work needs an approved change request.
- Enforcement: Name the criteria for moving to quarantine or reject, plus who approves that change.
- Data and exit: Set report access, retention, export format, and deletion terms, plus the records and documentation handed over when service ends.
This keeps managed DMARC practical for operators. The service covers authentication for the client's exact domains; it does not guarantee inbox placement. Treat inbound filtering and lookalike-domain monitoring as separate services unless expressly included. Compromised-account response needs separate scope. Some issues belong in scope, such as a missing DKIM record for an approved sender. Others belong outside it, such as rewriting a client's marketing automation strategy.
Build the client inventory
A managed DMARC service starts with inventory because DMARC reports only become useful when the sender list has owners. Capture domains, subdomains, DNS access, known mail sources, business owners, vendor contacts, and the client decision maker before the first policy change. Confirm that the client owns each domain or has written authority to approve changes. Record confirmed non-sending domains separately so they can move to enforcement without active-sender remediation.
|
|
|
|
|---|---|---|---|
Domains | Sending and parked | Personal domains | DNS list |
Senders | Approved and unknown sources | Fixing unapproved senders | Reports and owner confirmation |
Access | Authorized DNS and sender access | Unapproved vendor access | Access register |
Approvals | Policy moves | Brand disputes | Ticket notes |
A compact scope inventory for MSP onboarding.
For repeatable client onboarding, require the inventory before remediation starts. If the client cannot name a sender owner, the MSP can monitor and flag it, but the client has to decide whether that sender stays. An unfamiliar IP address alone is not enough to approve a sender. Confirm it with message headers, the return-path domain, the DKIM signing domain, vendor configuration, and an internal owner. Track unknown senders in an exception register, with an investigation owner and a review date.
?
What's your domain score?
Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.
A domain health check turns the scope conversation into visible DNS findings for DMARC and SPF. DKIM checks also need each sender's selector; validate delivered-message headers to confirm signing and DMARC results before committing to enforcement timelines.
Split monitoring from remediation
Monitoring and remediation are different services. DMARC monitoring gives visibility into authentication results and sender behavior. Managed remediation turns those findings into DNS changes, vendor requests, DKIM setup, SPF cleanup, and policy movement.
Monitoring only
- Visibility: Collect aggregate reports and identify passing, failing, and unknown sources.
- Reporting: Send status summaries with authentication trends and unresolved issues.
- Limits: No vendor fixes, no DNS updates, and no policy movement without a separate task.
Managed remediation
- Fixes: Create or update SPF, DKIM, and DMARC records for approved sources.
- Coordination: Open vendor tasks and track the client-side approvals needed to finish them.
- Outcome: Implement the client-approved enforcement policy after sender checks and a delivery-risk review.

Issue steps to fix dialog showing the issue overview, tailored fix steps, and verification action
Suped's product helps MSPs make this split clear because issues can be reviewed with source context and fix steps. That supports a scoped workflow: monitor all approved domains, remediate agreed issues, and escalate unclear senders for client approval instead of absorbing unlimited investigation.
Assign ownership before rollout
Every managed DMARC scope needs a responsibility matrix. A message fails DMARC when neither SPF nor DKIM produces an authenticated domain that satisfies the strict or relaxed comparison with the visible From domain. The fix often sits with a marketing vendor, website team, copier vendor, billing platform, or DNS owner. The MSP should own the process, not every external dependency.
|
|
|
|
|---|---|---|---|
Add DMARC | Prepare | Approve | None |
Fix DKIM | Guide | Authorize | Configure |
Approve reject | Recommend | Decide | None |
Retire sender | Flag | Decide | Confirm |
A simple responsibility matrix for managed DMARC delivery.
Avoid open-ended remediation
Do not let managed DMARC become unpaid vendor management. Include a defined number of remediation cycles or ticketed fixes, then require a change request for extended investigation, sender migration, or business process cleanup.
Scope clause example
The managed DMARC service includes monitoring, source identification, recommended DNS changes, and remediation for approved senders within the SOW's stated allowance for each billing period. Work beyond that allowance requires an approved change request. Client approval is required before quarantine or reject. Third-party vendor work beyond standard DNS guidance is handled as a separate project.
Set technical deliverables
The technical scope should list deliverables that can be checked. That usually includes DMARC reporting, SPF validation, DKIM coverage, policy staging, alerting, and a final enforcement recommendation. Hosted DMARC and Hosted SPF can reduce repetitive DNS work when the MSP manages many client domains.
- DMARC record: Create or update the policy record, verify authorization for any external aggregate-report destination, and confirm reports are flowing.
- SPF cleanup: Remove stale senders and validate SPF against its limit of 10 DNS-querying terms per evaluation, including nested includes. See RFC 7208.
- DKIM coverage: Enable DKIM for approved systems and verify a passing signature with a suitable d= domain in delivered-message headers. Record selector and key-rotation ownership.
- Policy staging: Agree an observation window that covers infrequent senders and business-critical sending cycles before enforcement.
Illustrative DMARC record optionstext
Host: _dmarc.client.example Type: TXT Value: "v=DMARC1; p=none; rua=mailto:reports@client.example" Provider-hosted alternative, where supported: Use the assigned provider target, not this illustrative value. Host: _dmarc.client.example Type: CNAME Value: client-managed-dmarc.example
A hosted CNAME must resolve to a valid DMARC TXT record. Publish either the TXT record or the CNAME at _dmarc.client.example, never both. RFC 9989 removed the pct tag, so use evidence-backed policy changes instead of percentage rollouts. RFC 9990 defines aggregate reporting, including authorization for external report destinations. Keep blocked work visible by assigning each item an owner and a next action.
Run the rollout in stages
A scoped managed service needs rollout gates. The client should know what must be true before the domain moves to stronger policy. That avoids a rushed reject policy and gives the MSP a defensible reason to wait when the sender data is still incomplete. Quarantine and reject state the domain owner's requested handling, but receiving systems can apply local policy.

Managed DMARC rollout for MSPs: inventory, monitor, fix senders, client approval, and enforce.
Policy rollout gates
Use these policy options as operational gates; reject requires a domain-specific risk assessment.
Monitor
p=none
Reports flow and unknown senders are being classified.
Contain
p=quarantine
Known legitimate senders pass and risky sources are reviewed.
Reject, where suitable
p=reject
Valid DKIM signing is confirmed and the client has accepted indirect-mail risks.
RFC 9989 advises against p=reject for general-purpose email domains, especially where users post to mailing lists. Review forwarding and mailing-list paths before recommending reject. Domains using reject must apply valid DKIM signatures rather than rely solely on SPF. Test each business-critical sender separately; a high aggregate pass rate can hide low-volume failures.
Before enforcement, run sender audits and document every unresolved sender. If a high-value sender still fails, the scope should require an owner, a fix path, and a client decision to delay enforcement, move the mail to a dedicated subdomain with its own policy, or retire the sender.
Define change control and rollback
Production DNS and sender changes need a documented path. Scope should distinguish standard changes from emergency changes and name the approver, maintenance window, verification method, rollback trigger, and evidence retained in the ticket. Define when the remediation clock pauses for client approval or vendor action, record the reason, and keep notification and escalation duties active.
- Capture the current DNS value, TTL, report baseline, affected senders, and business owner before the change.
- Record client approval, the change window, the person implementing it, and the exact proposed value.
- Verify public DNS, send a controlled message through affected systems, and record the authentication result.
- Restore the prior value or lower the policy when the agreed rollback trigger occurs, then escalate to the named decision owner.
A rollback plan should name observable triggers, such as failed transactional mail or a material rise in DMARC failures for an approved sender. A generic promise to reverse the change is not enough for a service desk runbook.
Operate the agreed scope in Suped
Suped's product gives MSPs a shared workflow for monitoring, source review, issue detection, alerts, hosted records, and multi-tenant client management. Operators can move between client organizations, review an issue with its fix steps, and keep managed-record work inside the agreed service boundary.

MSP organizations page showing client organizations, domain counts, email volume, and domain status columns
Scope-friendly Suped workflows
- Client separation: Use the MSP dashboard to manage client organizations without mixing their domains.
- Issue handling: Use automated issue detection and steps to fix for repeatable remediation.
- Record hosting: Use Hosted DMARC, Hosted SPF, SPF flattening, and Hosted MTA-STS where the service scope includes managed records.
- Risk signals: Combine DMARC with blocklist (blacklist) monitoring and deliverability insights when reputation visibility is part of the package.
Set reporting and response commitments
Agree the review cadence and client report contents in the service level agreement (SLA). A starting point is weekly internal review and monthly client reporting, adjusted to the client's risk. Report policy status by domain and authentication results for approved senders, with unresolved exceptions and the client's next decisions. Require new domains and senders to pass the agreed approval process before they enter the service.
State support hours and severity-specific acknowledgement targets separately from remediation targets. Start the response clock when a qualifying alert or ticket reaches the agreed queue. RFC 9990 describes daily or more frequent aggregate feedback, which summarizes prior activity. Report-based monitoring cannot promise immediate detection or visibility into every receiver. Set review targets against data received.
After that, connect scope to service tiers. Monitoring, managed remediation, hosted records, policy enforcement, blocklist or blacklist monitoring, and executive reporting can each sit in a defined tier. That makes the service easier to sell and much easier to deliver.
Define offboarding before service starts
Include an exit plan in the SOW, with notice requirements, the handover deadline, the responsible DNS owner, and any transition fee. Preserve the client's agreed policy and working authentication records when monitoring ends.
- Hand over the domain and sender inventory, current DNS values, policy-change history, and open exceptions with their owners. Specify report export formats and the period of data available.
- Agree the replacement rua destination and verify any required external reporting authorization before retiring the old reporting endpoint.
- Replace or transfer hosted DMARC and SPF dependencies before cancelling them. Verify public DNS and authentication results after the change, and confirm that reports reach the new destination.
- Record when operational responsibility transfers, revoke MSP access to the client tenant, and apply the agreed retention and deletion terms to remaining report data.
Frequently asked questions
Yes, if the MSP has DNS access and the contract includes managed remediation. If DNS access stays with the client, the service should include prepared records, validation, and clear implementation steps, but the client owns the change.
The client should approve quarantine and reject because those policies can affect mail delivery. The MSP should provide the evidence, explain remaining risk, document rollback triggers, and recommend the policy move.
Include every client-owned domain that sends mail or can be abused for impersonation, then separate active sending domains from parked or defensive domains. Name each domain and document subdomain coverage so later additions need an agreed change request.
Basic vendor guidance should be in scope for managed remediation. Extended vendor project work, platform migration, or repeated follow-up should have a defined limit or a separate project path. Pause the remediation clock only under the agreed SLA terms, while maintaining client communication and escalation.
Suped's product supports repeatable operations across clients through DMARC monitoring, verified and unverified source review, issue steps, alerts based on available data, hosted authentication records, client reporting, and multi-tenant management.

