Suped

How to create DMARC service tiers for MSP clients

Published 4 Jul 2026
Updated 5 Nov 2026
15 min read
Summarize with
DMARC service tiers for MSP clients, illustrated as stacked service layers.
Updated on 5 Nov 2026: We added cost-based tier pricing and clarified policy testing and support commitments.
DMARC service tiers for MSP clients should be built around operational scope, not only around policy names. A useful tier model starts with monitoring, adds managed remediation, then adds enforcement, reporting, hosted DNS services, and higher-touch review for clients with more brands, domains, vendors, or compliance pressure.
For most MSPs, three tiers cover the required work: a baseline visibility tier, a managed authentication tier, and a protection tier. Each tier should state exactly what the client gets, what the MSP owns, what the client still approves, and what triggers an escalation. That structure makes DMARC easier to sell and deliver without creating an open-ended support burden.
  1. Baseline: Collect reports, identify legitimate senders, and explain risk. Use p=none for discovery on domains without enforcement; preserve working quarantine or reject policies.
  2. Managed: Fix SPF, DKIM, and alignment gaps, coordinate with vendors, and move clients through a controlled policy rollout.
  3. Protection: Maintain enforcement, watch new sources, send client-ready reporting, and include reputation checks such as blocklist and blacklist monitoring.
Suped is our DMARC and email authentication platform. Its MSP dashboard supports client switching and source review; hosted DMARC and hosted SPF support policy changes and sender management when those tasks are included in the service.

Start with service ownership

The first design choice is who owns each part of the DMARC workflow. A client can buy software and still fail if nobody owns source discovery, vendor follow-up, DNS changes, policy staging, and executive reporting. MSP tiers work when they turn those tasks into named responsibilities.
A practical MSP tier is a promise about a repeatable service. It should answer: how many domains are covered, how many sending platforms are investigated, how often reports are reviewed, what remediation work is included, and what happens when a new sender appears. Use a shared MSP DMARC operating model, where authentication is handled like any other managed security service.
Weak tier design
  1. Capability list: The plan names tools but does not say who investigates failures.
  2. Policy only: The tier says p=reject without defining rollout checks.
  3. Unbounded support: Every third-party sender issue turns into ad hoc ticket work.
Strong tier design
  1. Workflow scope: The tier says what is monitored, fixed, reviewed, and reported.
  2. Clear gates: Policy moves happen after source approval and failure-rate checks.
  3. Defined exceptions: Vendor remediation outside normal scope has a named escalation path.
Separate initial project work from ongoing service work. Onboarding a client domain, finding all mail sources, and fixing inherited SPF or DKIM issues is different work from monthly monitoring. Mixing those into one vague package makes margins hard to predict.

Use three core tiers

The simplest useful structure has three core tiers. You can rename them to match your catalog, but the work behind them should stay clear: visibility, remediation, protection, and ongoing client communication. This keeps sales language simple while giving delivery teams enough boundaries to run the service consistently.

Tier

Best fit

MSP owns

Client owns

Monitor
Visibility-only scope
Reports, source list
Vendor decisions
Managed
Active senders
Fixes, rollout
DNS approval
Protect
Compliance risk
Enforcement, alerts
Business exceptions
Example service responsibilities for MSP DMARC tiers.
The monitor tier is for clients who need visibility and source review without included remediation. It includes DMARC report collection, source identification, authentication status, and a plain-language summary of what is sending as the client. The MSP should not promise broad vendor remediation here unless it is separately scoped.
The managed tier is where the MSP starts doing the operational work. This includes reviewing SPF and DKIM results, identifying senders with domain alignment failures, coordinating DNS changes, and moving the domain through quarantine or reject after agreed policy gates are met. Document included fixes in a DMARC monitoring package so sales and delivery use the same scope.
The protection tier is for clients where spoofing, compliance, vendor sprawl, or brand risk makes ongoing attention necessary. It includes enforcement maintenance, alerts based on received reports, recurring review, client reporting, and domain or IP reputation checks. Hosted DMARC and hosted SPF can be included when the MSP owns policy changes and sender management.
Operational weight by tier
Illustrative effort allocation, not measured benchmarks. Actual work depends on sender complexity and the contracted scope.
Monitoring
Remediation
Reporting
Escalation

Price tiers against delivery costs

Choose a minimum monthly fee per client or a fee per monitored domain. State whether parked domains and separately managed subdomains count toward the allowance, and whether report-volume limits affect the price. Separate onboarding project fees from monthly recurring revenue (MRR).
Internal monthly pricing formulatext
Monthly fee = (platform cost + expected delivery labor + allocated service overhead) / (1 - target gross margin) Use a decimal for gross margin: 60% = 0.60. Count each cost once and use costs for the same client or domain scope.
  1. Included work: Budget technician time for source review, vendor follow-up, policy changes, and client reporting.
  2. Overages: Define charges for extra domains and sender investigations, with approval before chargeable work starts.
  3. Support coverage: Price business-hours and out-of-hours response separately when staffing costs differ.
  4. Margin review: Compare actual ticket time with the allowance at renewal and after material sender changes.
A domain at reject still needs monitoring and sender-change handling. If ongoing effort exceeds the allowance, agree on a remediation project or a tier change instead of absorbing unlimited support.

Define the onboarding package

Every tier needs an onboarding path. DMARC is not a switch that starts cleanly on day one. Many clients have old CRMs, payroll systems, ticketing systems, scanners, marketing platforms, and line-of-business applications sending mail. The MSP has to discover those sources before promising enforcement.
Make onboarding a defined phase with a checklist. In Suped, that means adding the client organization, adding domains, publishing the reporting record, waiting for mail data, reviewing verified and unverified sources, then creating client-facing notes for the first review. Add reporting without weakening a working policy, and collect representative mail data before remediation decisions.
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
Your onboarding scope should say how many domains are included, which identity platforms are expected, and how unknown senders are handled. Parked domains need protective records, but confirm they send no mail before treating them as non-sending domains. A web redirect alone does not establish that a domain sends no email.
Do not bundle unlimited discovery
A client with one primary domain and two known senders is not the same as a client with six domains and twenty vendor platforms. Put a sender investigation allowance in each tier, then define how extra vendor work is approved.
  1. Domain inventory: List primary, alias, parked, and campaign domains before publishing records.
  2. Sender inventory: Document mailbox platforms, SaaS platforms, web servers, and devices.
  3. DNS access: Confirm who can change TXT and CNAME records before remediation starts.
  4. Client access: Keep reports and DNS permissions separated by client, grant only required access, and agree on retention and export terms.
  5. Report authorization: When the rua address uses an external domain, confirm the report consumer has authorized the destination and verify that reports arrive.
  6. Approval path: Name the client stakeholder who approves blocking unauthenticated mail.
Give delivery teams an onboarding checklist that they can use inside the ticket queue.

Map capabilities to each tier

Capability mapping should follow service responsibility. If the MSP is only providing visibility, DMARC monitoring and summary reporting are enough. If the MSP is committing to remediation, the tier needs authentication diagnostics and change tracking. If the MSP is committing to protection, the tier needs alerts, policy staging, hosted services, and broader deliverability signals.
Clients often assume their mailbox platform already handles everything. Message-level authentication results inside a mailbox platform do not replace a multi-domain MSP workflow for DMARC reporting, source discovery, policy staging, client reports, and cross-client triage. The service tier should explain that difference without overstating it.

Capability

Monitor

Managed

Protect

DMARC reports
Included
Included
Included
Sender fixes
Separately scoped
Included
Included
Hosted DMARC
Optional
Useful
Recommended
Hosted SPF
Optional
Useful
Recommended
Alerts
Basic
Standard
Priority
Blocklists
Optional
Optional
Included
Capability placement by service tier.
Use Suped's DMARC monitoring in every tier for report collection and source review. Offer hosted DMARC and hosted SPF when the contract includes policy changes or sender management. Blocklist (blacklist) monitoring adds reputation checks in the Protect tier; define investigation and provider escalation separately.
?

What's your domain score?

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

A domain health check is useful during sales and onboarding because it shows published authentication records. It cannot prove that every sending platform passes DMARC. Confirm DKIM using the selector and headers from an actual message, then review aggregate reports before assigning a tier.
Use authentication health to scope onboarding effort, then choose the ongoing tier based on client risk and the responsibility the MSP accepts.

Set policy gates and remediation limits

DMARC policy staging is where MSP service tiers often become messy. The client wants protection, the MSP wants clean delivery, and the data shows a few sources still failing. A tier should define what happens before moving a domain from monitoring to quarantine or reject.
Baseline monitoring recorddns
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com;"
Policy testing recorddns
_dmarc.example.com. TXT "v=DMARC1; p=quarantine; t=y; rua=mailto:dmarc@example.com;"
Full enforcement recorddns
_dmarc.example.com. TXT "v=DMARC1; p=reject; rua=mailto:dmarc@example.com;"
Account for policy test mode support
RFC 9989 retired pct and introduced t=y. Receivers supporting the tag treat p=quarantine; t=y as none and p=reject; t=y as quarantine. Because unrecognized tags are ignored, assume older implementations can apply the published p policy. Test mode is a request, not a guarantee against blocking. Remove t=y only after testing and client approval support the stronger policy. See RFC 9989.
The exact record depends on your reporting mailbox, platform routing, and policy strategy. The service tier should not hard-code one record forever. Move policy only after legitimate sources pass DMARC, failures affecting business-critical mail are resolved, client stakeholders understand the effect, and the rollback record is documented. DMARC requires SPF or DKIM to pass with domain alignment to the visible From address. Before reject, require working DKIM and test forwarding and mailing-list use. Review a full business sending cycle, including infrequent payroll and campaign mail.
Policy movement gates
Example thresholds an MSP can adapt before moving a client to stronger DMARC enforcement.
Monitor
Unresolved legitimate or unknown sender
Investigate unresolved sources before requesting stronger policy.
Quarantine
No unresolved business-critical failures
Use after legitimate business senders pass DMARC and delivery tests succeed.
Reject
No known business-critical failures
Use after legitimate sender failures are fixed and policy impact is approved.
Hosted DMARC makes this easier for MSPs because policy changes can be staged without asking for repeated DNS edits. Suped's hosted DMARC workflow is useful in managed and protection tiers where policy changes are part of the service, not a one-time setup.
Hosted DMARC configuration dialog showing policy controls, CNAME setup, and expanded advanced options
Remediation limits should be just as clear as policy gates. Include a fixed number of sender reviews, vendor coordination attempts, or DNS change requests in each tier. When a sender requires custom vendor support, legal approval, or application changes, move it into an approved project or escalation queue. Client approval does not exempt a failing sender from DMARC. Fix authentication or agree on a different sending domain before enforcement.

Build reporting into the service

Reporting is part of the service, not an afterthought. Clients do not need raw XML or a long list of authentication rows. They need to know which domains have DMARC enforcement, what changed, what needs approval, and whether any vendors are putting mail delivery at risk.
Each tier should have a reporting cadence. A monitor tier can use a monthly summary. A managed tier can include onboarding updates and policy movement notes. A protection tier should include recurring executive reporting, alert summaries, and action items when new sources appear.
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
Suped's client reports are useful here because they help MSPs turn authentication data into a client-ready artifact. A clean report reduces meeting prep and gives account managers something specific to discuss: pass rates, policy status, sender changes, and remaining work.
Report what changed
Good DMARC reporting says what changed since the last period. A client should see new senders, fixed failures, policy movement, open risks, and decisions needed from their side. Separate legitimate-sender pass rates from unauthenticated traffic; a low overall pass rate alone does not show that business mail is failing.
  1. Executive view: Use simple status language: monitoring, improving, enforcing DMARC, or action needed.
  2. Technical view: Show failing sources, alignment gaps, DNS changes, and sender ownership.
  3. Account view: Connect authentication progress to the client's email security roadmap.
  4. Renewal view: Show ongoing monitoring value after the domain reaches enforcement.
Build a DMARC progress report template that records completed work and outstanding client approvals.

Add operational add-ons carefully

Add-ons can help, but too many add-ons make the service hard to explain. Keep the core tiers stable and use add-ons for work that changes effort materially: extra domains, high-volume vendor remediation, hosted SPF management, blocklist and blacklist monitoring, MTA-STS, and executive review meetings.
Hosted SPF is useful when client sender lists change frequently. SPF evaluation has a limit of 10 DNS-querying mechanisms and modifiers, including nested includes, as defined in RFC 7208. Suped's hosted SPF and SPF flattening workflows support sender management without repeated direct DNS edits. When flattening is included, define who refreshes provider IP changes and checks SPF after each sender change.
Good add-ons
  1. Extra domains: Charge separately when each domain needs source review.
  2. Hosted SPF: Use for clients with frequent sender changes.
  3. Blocklist checks: Add for clients with outbound deliverability risk.
Risky add-ons
  1. Unlimited vendors: This creates open-ended support work.
  2. Instant reject: This skips the evidence needed for safe enforcement.
  3. Raw exports: Most clients need decisions, not unfiltered data.
When blocklist or blacklist monitoring is included, define what the MSP does when a listing appears. The useful service includes identifying the affected domain or IP, checking whether the client controls the sending path, and deciding whether remediation belongs to the MSP, the mailbox provider, or a third-party sender.
Blocklist monitoring page showing domain and IP checks across blocklists with importance and status
Blocklist monitoring page showing domain and IP checks across blocklists with importance and status
Keep add-ons tied to defined outcomes. If the add-on does not change monitoring depth, remediation work, alert handling, or reporting, it probably belongs in internal tooling rather than the client-facing tier list.

Turn tiers into a runbook

A tier only works if technicians can deliver it the same way every time. Create a runbook for each tier with intake steps, DNS templates, review cadence, escalation triggers, client messages, and closure criteria. The runbook should also define what gets logged in tickets and what gets reviewed in the DMARC platform.
MSP DMARC service workflow: intake, reporting setup, sender review, remediation, policy staging, and client reporting.
MSP DMARC service workflow: intake, reporting setup, sender review, remediation, policy staging, and client reporting.
The runbook should use the same decision language as the service tiers. If the client is on monitor, the technician identifies sources and reports risk. If the client is on managed, the technician opens remediation tasks. If the client is on protection, the technician triages new failures by business impact as well as volume.
Set service-level agreement (SLA) targets for alert acknowledgment and investigation, with support hours and vendor dependencies stated separately. For example, a Protect contract can target acknowledgment within four business hours of alert receipt, without promising resolution in that window. Aggregate reports usually arrive daily, as described in RFC 9990, so start response commitments when an alert or incident report is received, not when the message was sent. Check delivery immediately after policy changes, set an observation window, and name the rollback approver.
A simple escalation rule
Escalate when a new unauthenticated source sends meaningful volume, when a known vendor changes authentication behavior, or when enforcement would block mail the client says is business-critical.
  1. Create the organization: Add the client and domains in the MSP dashboard.
  2. Publish records: Set DMARC reporting and confirm DNS is visible.
  3. Review senders: Classify known, unknown, authorized, and suspicious sources.
  4. Fix alignment: Work through SPF, DKIM, and domain alignment issues.
  5. Move policy: Test quarantine or reject only after agreed gates are met.
  6. Report status: Send the client a summary of progress, risks, and decisions.

Define the offboarding handoff

Define offboarding in the service agreement before the client leaves. DMARC records remain in DNS after the managed service ends, so the client needs a named owner for policy changes, reporting, sender exceptions, and future authentication work. The agreement should also state the notice period, included handoff work, chargeable migration work, and support cutoff.
  1. Capture current state: Record DMARC policy, SPF sources, DKIM selectors, hosted records, and accepted exceptions.
  2. Transfer working records: Give the client the sender inventory, decision log, open issues, and latest report.
  3. Cut over reporting: Replace the MSP-controlled rua destination, confirm external authorization where required, and verify report arrival.
  4. Remove dependencies: Move any hosted DMARC or hosted SPF records before the MSP stops managing them.
  5. Close access: Remove MSP and client accounts according to the agreed cutoff and data retention terms.
  6. Confirm acceptance: Get written confirmation that the new owner has the records and understands the current policy.
For a client managed in Suped, use the current domain status and client report to document the handoff. Replace any Suped-managed reporting or hosted DNS dependency, verify the new destination, then remove access under the agreed retention schedule. This prevents a client from losing reports or leaving a policy record dependent on a service it no longer receives.

How Suped fits the tier model

Suped is our DMARC and email authentication platform. Its client organizations keep domain monitoring and reports separated by customer, while the MSP dashboard supports reviews across clients.
Suped can hold the authentication evidence for the service, while the MSP's PSA or ticketing system handles task assignment and approvals. Suped shows what is happening across DMARC, SPF, DKIM, hosted services, and reputation signals. The PSA tracks who is doing the work and what the client approved.

Suped workflow

Tier fit

Service value

MSP dashboard
All tiers
Client switching
Issue detection
Managed and Protect
Failure review
Hosted DMARC
Managed and Protect
Policy staging
Hosted SPF
Managed and Protect, if scoped
Sender control
Client reports
All tiers, scope varies
Account review
A practical Suped mapping for MSP service tiers.
DMARC reduces unauthorized use of the domain in the visible From address. It does not prevent lookalike-domain messages or compromised-account email, and passing authentication does not guarantee inbox placement. These limits are described in RFC 9989.

Check scope before selling a tier

Before quoting a client, define domains, sender allowances, review cadence, policy gates, alert handling, exclusions, escalation, and offboarding. Record these commitments in the service agreement so sales and delivery use the same scope.
  1. Keep scope visible: A tier should be easy for sales, delivery, and clients to understand.
  2. Separate setup from service: Initial discovery and remediation should not quietly consume ongoing support time.
  3. Use policy gates: Move to quarantine or reject when the data and approval path support it.
  4. Report decisions: Clients pay for clarity, not raw authentication noise.

Frequently asked questions

Three tiers are usually enough: monitor, managed, and protect. More tiers create sales complexity and delivery confusion unless you have a very mature service catalog.

Active remediation and policy changes belong in tiers where the MSP owns that work. A monitor-only contract can observe an already-enforced domain without weakening its policy, but new fixes and policy changes need an agreed scope.

Hosted DMARC fits best in managed and protection tiers because it reduces repeated DNS work when policies change. It can be optional for monitor-only clients.

Separate active mail domains from confirmed non-sending domains. Active domains need source review and remediation. Parked domains need protective records, but check for mail use before assigning the simpler scope. State whether each domain or subdomain counts toward the tier allowance.

Blocklist and blacklist monitoring fits best in the protection tier, where the MSP is already watching enforcement, sender behavior, alerts, and domain reputation.

Transfer the current policy, sender inventory, open exceptions, and latest report. Replace MSP-controlled rua and hosted DNS dependencies, verify the new owner receives reports, remove access on the agreed date, and follow the contracted retention terms.
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