Suped

How to set client responsibilities for DMARC rollout

Published 6 Jul 2026
Updated 7 Nov 2026
12 min read
Summarize with
MSP and client DMARC rollout responsibilities for DNS, sender approval, and reporting.
Updated on 7 Nov 2026: We clarified client approval gates and incident responsibilities, including the limits of DMARC policy testing.
Client responsibilities for DMARC rollout should be set before the first DNS record changes. The client owns business approval, sender confirmation, DNS authorization, risk sign-off, and internal communication. The managed service provider (MSP) owns discovery, technical configuration, monitoring, change sequencing, evidence, and reporting. When that split is written down, the rollout has fewer pauses, fewer surprise senders, and a clearer path to enforcement.
For an MSP DMARC program, written responsibilities keep approvals and technical work moving. DMARC touches marketing systems, finance tools, CRM platforms, help desk mail, website forms, and mailbox platforms. Aggregate reports reveal observed sources, but do not cover every receiver or seasonal sender. The client still needs to confirm which senders are legitimate and who can approve a policy change.
Minimum split
The MSP manages the technical rollout and evidence, while the client confirms business senders, authorizes DNS changes, approves enforcement timing, and accepts documented delivery risk.

Set a RACI for client and MSP responsibilities

A DMARC rollout needs a responsibility assignment matrix (RACI) that the client understands. Responsible means doing the work, accountable means owning the outcome and final decision, consulted means providing facts, and informed means receiving updates. Assign one accountable owner to each work item. The mistake is asking the client to approve enforcement without showing which senders were found, which ones passed authentication, and which ones still need fixes.
Add the matrix to the MSP statement of work or onboarding checklist. Keep names attached to each role, rather than departments only. A named marketing owner beats a generic marketing team entry when a campaign platform starts failing SPF or DKIM checks.

Work item

MSP

Client

Evidence

Domain intake
Responsible
Accountable
Domain list and scope approval
DNS access
Consulted
Responsible and accountable
Delegated access or named publisher
Sender review
Responsible
Accountable
Business-approved sender inventory
SPF changes
Responsible
Accountable
Before/after records and validation
DKIM setup
Responsible
Accountable
Signing test and platform owner
Policy change
Responsible
Accountable
Written sign-off and rollback value
Monthly report
Responsible and accountable
Informed
Report link and action owners
Compact RACI for a client DMARC rollout.
The sender review row matters most. Before enforcement, use a sender audit to turn noisy DMARC aggregate data into a business-approved sender list. If a source is unknown, the client needs to identify it or explicitly accept its failure under enforcement. Do not authorize an unverified source in SPF just to improve a pass rate.
  1. Named owner: Require a real person for DNS, security approval, marketing systems, finance systems, and executive sign-off.
  2. Decision clock: Set a deadline for sender decisions and escalate missed responses. Silence is not approval to enforce.
  3. Escalation path: Name who resolves conflicts when marketing wants speed and security wants enforcement.
  4. Change window: Agree when DNS changes can happen and who confirms success after propagation.

Define client inputs before the audit

DMARC rollout workflow covering domains, DNS access, sender review, policy sign-off, and reporting.
DMARC rollout workflow covering domains, DNS access, sender review, policy sign-off, and reporting.
Client inputs need to be requested in a format that creates evidence. A free-form email that says marketing uses a newsletter platform is not enough. Request domains, subdomains, known senders, system owners, DNS contacts, and any upcoming email campaigns that would make enforcement timing risky. Include monthly billing, quarterly notices, and annual campaigns even when they are absent from recent reports. Keep client approval separate from observed source IPs, sending identities, DKIM selectors, and test dates in the sender inventory.
The client does not need to understand every authentication detail, but the client does need to confirm whether a sender is allowed to use the domain. That confirmation is a business decision. An MSP can show that a source fails DMARC because neither SPF nor DKIM passes with the required match to the visible From domain. The client decides whether to fix or retire an approved sender, or accept its failure under enforcement.
  1. Domain scope: Ask for every domain that sends mail, plus parked domains that should be protected from spoofing.
  2. Known senders: Collect billing systems, marketing platforms, website forms, help desk tools, scanners, and CRM mail.
  3. Business owners: Map each sender to a person who can approve authentication work or retirement and arrange vendor administrator access or supplier follow-up.
  4. Risk windows: Capture launches, invoices, fundraising, and customer notices that should not overlap with enforcement.
Client delay risk
An unknown sender without a business owner can delay enforcement. Put unknown sender review into the responsibility plan with a deadline and escalation owner.

Separate DNS authority from email authority

DNS authority and email authority are different responsibilities. Some clients give the MSP DNS access, some require internal IT to make changes, and some use a web agency for DNS. Write down who can add TXT records, who can add CNAME records, who can approve SPF edits, and who can validate that the production record matches the agreed change. Use named accounts with the minimum available permissions, or client-applied changes, rather than shared administrator credentials.
Also separate DMARC policy authority from DNS access. A person who can edit DNS should not be forced to decide whether the domain is ready for p=reject. The client security or business owner should approve that policy step after the MSP shows authentication results and remaining risk.
Example policy stages, subject to client approvaldns
# Illustrative records: use the client's actual domain and report destination # Replace the existing record; publish one DMARC TXT record per name # t=y is ignored by older receivers, which can apply p in full # Approve full published-policy exposure before either optional test # 1. Monitor _dmarc.example.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com" # 2. Optional quarantine test after approval _dmarc.example.com TXT "v=DMARC1; p=quarantine; t=y; rua=mailto:dmarc@example.com" # 3. Apply quarantine after approval _dmarc.example.com TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com" # 4. Optional reject test, only if rejection is appropriate for this domain _dmarc.example.com TXT "v=DMARC1; p=reject; t=y; rua=mailto:dmarc@example.com" # 5. Apply reject only after explicit approval _dmarc.example.com TXT "v=DMARC1; p=reject; rua=mailto:dmarc@example.com"
Suped's DMARC checker validates the visible TXT record before and after a DNS change. Keep that result in the change record alongside authentication data over time; a valid DNS record alone does not show that approved senders pass DMARC.

DMARC checker

Look up a domain's DMARC record and catch policy issues.

?/7tests passed
Do not let DNS access become the hidden blocker. If the client cannot grant access, the MSP should provide exact records, TTL guidance, expected verification steps, and a rollback path. Save the current record and TTL before editing, verify the authoritative answer and a public resolver afterward, and allow for existing DNS caches. Stop if the live record differs from the approved baseline. If the MSP has access, the client still needs to approve the business effect of the change.

Set approval gates for policy changes

DMARC policy changes should have gates that both sides understand. Avoid calendar-only rollouts because the data should decide the pace. Observe representative business cycles and test critical senders before advancing; a high overall pass rate alone is not an approval gate. Review forwarding and mailing-list paths. RFC 9989 advises against p=reject for general-purpose email domains, so rejection is not a universal rollout endpoint.
Policy gate readiness
Approval gates for a domain suited to enforcement; optional t=y tests require acceptance of full published-policy exposure.
Discovery
p=none
Reports arriving; business owners confirm sender inventory.
Optional quarantine test
p=quarantine; t=y
Critical senders tested; client accepts full quarantine exposure.
Apply quarantine
p=quarantine
Representative traffic reviewed and written approval recorded.
Optional reject test
p=reject; t=y
Domain suited to rejection; client accepts full reject exposure.
Apply reject
p=reject
Client approves rejection and rollback criteria for this domain.
Check receiver support before policy testing
RFC 9989 removed pct and introduced t=y. Supporting receivers treat quarantine as none and reject as quarantine during testing. Older receivers ignore t=y and can apply the published p policy in full. Obtain approval for that exposure before testing; remove t=y only after reviewing evidence. Publish one DMARC TXT record at each name.
The client should approve each gate in writing. That approval does not need to be a legal document, but it should contain the domain, current policy, proposed policy, testing status, evidence reviewed, known exceptions, rollback contact, rollback trigger, and planned change window. Record the remediation owner and expiry date for every exception. Written risk acceptance does not exempt a sender from receiver DMARC checks.
For a larger service process, the enforcement move needs to include client approval gates, technical evidence, and post-change monitoring. The MSP should not carry the full business risk of a reject policy without client sign-off.
MSP owns
  1. Evidence pack: Source breakdown, DMARC results for each approved sender, critical-path tests, and recommended fixes.
  2. Change plan: Proposed record, testing status, timing, verification, and rollback steps.
  3. Monitoring: Authentication results after the change and alerts for unexpected failure spikes.
Client owns
  1. Approval: Written acceptance of the policy change and known sender exceptions.
  2. Owners: Business contacts for senders that still need vendor or platform work.
  3. Communication: Internal notice for support, marketing, finance, and customer-facing teams.

Agree incident and rollback responsibilities

Before enforcement, agree who can act when legitimate mail fails, including outside normal support hours. Put the response target and emergency authority in the statement of work or service-level agreement (SLA). Do not wait for the next client report to investigate a delivery incident.
  1. Client contact: Report the affected business process and urgency, provide bounce messages or message IDs, and coordinate an approved alternative sending route.
  2. MSP responder: Review authentication headers, mail logs, bounce evidence, and recent changes to establish whether DMARC caused the failure.
  3. Rollback authority: Name who can restore the last verified policy and its saved value, the trigger for doing so, and a backup approver. Pre-authorize emergency action within written limits.
  4. Recovery owner: Account for DNS cache expiry, retest the affected sender, and have the client confirm business recovery before closing the incident.
A rollback does not resend rejected messages. Assign the sender owner to retry affected mail after the fix, then record the cause and obtain approval before tightening policy again.

Document reporting and support expectations

Reporting responsibilities should be part of the rollout plan, not an afterthought. The client needs to know what will be reported, how often, and what counts as an action item. A useful report explains progress in business language, then shows enough technical evidence for the client's IT or security contact to trust the recommendation.
Client reports page showing a generated client report, date range, created date, and actions
Client reports page showing a generated client report, date range, created date, and actions
The client should approve the aggregate report destination, authorized users, and retention period. When rua points to an MSP or another external domain, the MSP should confirm that the report consumer has published the required external destination authorization and verify that reports arrive. A valid DMARC TXT record alone does not prove reporting works.
Aggregate reports usually arrive daily and are not real-time delivery telemetry. RFC 9990 defines their reporting format. Agree who checks for missing reports, and use bounce evidence and mail logs for urgent delivery problems. Authentication results do not prove inbox placement.
Suped supports this workflow with MSP client reports, organization switching, issue detection, and alerting. That matters because responsibility tracking gets harder when one MSP manages many client domains. A single DMARC monitoring workflow gives the service desk the same source review, policy status, and issue history for each client.
The MSP should define what is included in support. For example, fixing a missing DKIM selector for a managed mailbox platform can be in scope, while coordinating with an unmanaged marketing agency can require client ownership. That boundary should be clear before enforcement pressure starts.
  1. Report cadence: Weekly during rollout, then monthly after enforcement unless alerts require faster review.
  2. Action owner: Every unresolved sender should have an MSP owner, client owner, or vendor owner.
  3. Risk note: Separate suspected unauthorized use, approved-sender failures, forwarding effects, and unknown sources; assign investigation rather than labeling failures harmless without evidence.
  4. Ticket link: Keep fixes connected to the client support system so decisions are auditable.
A good progress report does not bury the client in XML terminology. It states what changed, what is still failing, who owns the next action, and whether the domain is ready for the next policy gate.

Use Suped workflows for MSP delivery

Suped is our DMARC and email authentication platform. MSP teams can use its client workspaces to review authentication results, assign follow-up work in their support system, and prepare evidence for client policy approvals. Blocklist (blacklist) monitoring adds a separate reputation signal; it does not determine DMARC readiness.
Hosted services can also reduce client dependency on repeated DNS edits. With Hosted DMARC, the MSP can stage policy changes through Suped once the client has approved the CNAME setup. With Hosted SPF, the MSP can manage sender includes and stay under lookup limits without asking the client for DNS access every time a vendor changes.
Traditional DNS-only rollout
Every policy or sender update depends on DNS access, change timing, and manual verification. This works for simple clients, but it creates friction when the MSP manages many domains or when the client has slow internal DNS approvals.
  1. Control: Client DNS team stays involved for most updates.
  2. Speed: Changes wait for normal client change windows.
Suped hosted workflow
The client approves initial setup and policy gates, while the MSP manages approved changes inside Suped and records the decision in the client change ticket.
  1. Control: Client keeps approval authority for enforcement.
  2. Speed: MSP handles approved policy staging and sender maintenance.
Best practical split
Use Suped to centralize monitoring, alerts, reports, hosted records, and fix steps. Keep client approval for sender legitimacy and enforcement. That gives the MSP operational control without taking ownership of business decisions.

Make sender onboarding an ongoing client duty

DMARC responsibility continues after the agreed enforcement policy is active. The client should require teams to notify the MSP before any platform starts sending with a protected From domain. This prevents a legitimate new source from appearing as an unknown failure after enforcement.
The request should arrive before procurement or launch and name the business owner, sending domain or subdomain, expected volume, launch date, and vendor technical contact. The MSP should test SPF, DKIM, and DMARC alignment on the production sending path, update the approved sender inventory, and record the go-live decision.
  1. Client request: Submit each new sender before use and approve its business purpose.
  2. MSP validation: Verify that a production message passes DMARC through SPF or DKIM alignment.
  3. Go-live gate: Hold launch until the sender has an owner, authentication evidence, and approval.
  4. Retirement: Have the client report discontinued senders so the MSP can remove obsolete DNS authorization and inventory entries.

Keep the responsibility matrix in client records

Put the responsibility matrix into the proposal, repeat it during onboarding, attach it to policy approvals, and keep it in the client report. Include the approval ticket, current exceptions, decision deadlines, and next action owner so the service desk can follow the agreed decision.

Frequently asked questions

The client should approve the policy change, usually through a security, IT, or business owner with authority over email risk. The MSP should provide the evidence, recommended record, expected effect, and rollback plan.

It depends on access. If the MSP manages DNS, the MSP can make the approved change. If the client or another provider manages DNS, the MSP should provide exact records and verification steps. The client still owns authorization.

Treat it as a client-owned decision with a deadline. The MSP can show the source, volume, authentication result, and risk. The client needs to identify it or explicitly accept its failure under enforcement. Escalate an unanswered request; do not treat silence as approval.

Weekly client reporting works during rollout, then monthly after enforcement. Review alerts as data arrives; aggregate DMARC reports usually arrive daily and do not provide real-time delivery monitoring. Escalate authentication failures and blocklist or blacklist changes under the agreed support process.

RFC 9989 removed pct. Use t=y only with approval for full published-policy exposure, because older receivers ignore it. Review actual receiver behavior before removing t=y; do not assume it prevents rejection everywhere.

Suped gives MSPs one place to monitor client domains, detect issues, manage hosted DMARC and SPF workflows, send reports, and track alerts. The client still owns business approvals and sender legitimacy.
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