Suped

How to bundle DMARC monitoring with email security

Published 3 Jul 2026
Updated 4 Nov 2026
14 min read
Summarize with
DMARC monitoring and email security bundle for managed service providers.
Updated on 4 Nov 2026: We clarified DMARC test-mode limits and added client access controls and reporting checks for MSP email security bundles.
DMARC monitoring belongs inside an MSP email security bundle when it has a clear service owner, a recurring review process, client-facing reporting, and escalation rules for authentication failures. Run it as a recurring managed control. The service identifies sources using a client domain, flags suspected exact-domain spoofing, and shows when legitimate mail systems need repair. Confirm authorization with the client because authentication success alone does not establish business approval.
A practical bundle has four parts: baseline every client domain, monitor DMARC, SPF, DKIM, and reputation signals continuously, fix sender problems through tickets, then report progress in plain language. That structure lets an MSP attach DMARC to the email security stack without overloading engineers or confusing account managers.
  1. Baseline: Inventory domains, current DNS records, approved senders, and mail volume before changing policy.
  2. Operate: Review DMARC reports, investigate failures, and route fixes into the same queue used for security work.
  3. Report: Show authenticated volume, unknown senders, policy progress, and open risks during client reviews.
  4. Improve: Move clients through policy staging only when approved senders pass DMARC and remaining failures are understood.

Build the bundle around operational outcomes

The bundle should promise outcomes an MSP can deliver repeatedly. Use terms such as domain authentication monitoring, spoofing visibility, DNS record health, sender inventory, and enforcement readiness. Those outcomes connect DMARC to email security without claiming that DMARC blocks every malicious message.
DMARC checks whether the visible From domain matches a domain authenticated by SPF or DKIM under the record's matching rules. The domain owner publishes a requested handling policy for failures in DNS. It reduces exact-domain spoofing, but it does not detect malicious content. It also does not stop lookalike-domain or display-name impersonation. Receivers retain discretion over final message handling. Monitoring covers use of the client's sending domains. Inbound filtering still needs to check incoming senders and inspect messages for threats. A DMARC pass does not guarantee inbox placement.
Core package promise
A practical MSP bundle promises that client domains are monitored, legitimate senders are documented, DNS issues are found, and enforcement is handled through a staged process.
  1. Visibility: Show which services send mail for the client domain.
  2. Control: Identify unknown senders before strict policy changes.
  3. Proof: Report authentication progress with data clients can understand.
  4. Action: Convert DMARC problems into assigned tickets with clear fixes.
This positioning also helps sales. A client does not need to understand every DNS mechanism to understand that unmonitored sending domains create brand abuse and delivery risk. The MSP owns the technical workflow and explains the risk in operational terms.
DNS add-on
  1. Scope: One record check and a short technical recommendation.
  2. Owner: Usually depends on whoever controls DNS that day.
  3. Risk: No recurring review, so sender drift returns over time.
Managed email security control
  1. Scope: Ongoing monitoring, fixes, policy staging, and reporting.
  2. Owner: The MSP service desk or security operations function.
  3. Risk: Recurring reviews help detect sender changes and limit delivery disruption.

Define the client scope before touching DNS

A repeatable MSP service starts with scope. Include every domain the client owns, including the primary email domain and any subdomain used in a From address. Parked domains, redirect domains, brand domains, and acquisition domains get abused when nobody monitors them. They also create awkward client conversations when a spoofed message appears to come from a domain nobody remembered.
Before changing records, gather who controls DNS, who approves sender changes, who owns marketing platforms, and who receives escalation notices. MSPs get into trouble when DMARC work depends on a single technical contact with no client-side decision maker. For a domain confirmed never to send mail, publish p=reject and an SPF record of v=spf1 -all after checking subdomain requirements. Missing reports alone do not establish that a domain is unused.

Scope item

What to include

Why it matters

Domains
Primary, parked, brand, subdomains
Stops coverage gaps
Senders
Mailboxes and business apps
Finds unknown services
DNS owner
Registrar, host, or client
Reduces ticket delays
Approver
Client sponsor
Keeps enforcement moving
Review cycle
Monthly or quarterly
Makes reporting predictable
Use this scope table during onboarding and quarterly reviews.
A domain health check is a useful first action because it gives the MSP a DNS baseline before the managed service starts. It also gives the account team a simple artifact for the first client conversation.
?

What's your domain score?

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

After the initial check, separate findings into setup work and operating work. Missing records, duplicate SPF or DMARC policy records, and an unsuitable DMARC policy are setup tasks. New senders, failing DKIM, and unexpected traffic are operating tasks that belong in the recurring service. Record the client's declared sender list separately from sources observed in aggregate reports, then reconcile the two before enforcement.

Connect DMARC to the security stack

Bundling works when DMARC data has a place to go. Map findings into the existing professional services automation (PSA) ticket queue and client review process: high-risk failures become tickets, policy milestones go into business reviews, and urgent spikes trigger alerts. That turns XML reporting into a managed service instead of a specialist task hidden inside DNS.
Microsoft Defender XDR incident screen used as an example security workflow destination.
Microsoft Defender XDR incident screen used as an example security workflow destination.
The connection does not need to be complex at first. Start with a simple rule: anything that affects legitimate mail delivery or spoofing visibility gets a service ticket. Anything that shows progress or residual risk goes into the client report. Set response targets from alert receipt: aggregate reports arrive after the reported traffic, so monitoring does not guarantee immediate incident detection.
Do not bury DMARC alerts
DMARC alerts should not land in a shared mailbox with no owner. Assign them to the same operational queue that handles mailbox security work and DNS or sender changes.
  1. Critical: Confirmed delivery disruption affecting business-critical mail.
  2. High: Approved sender starts failing DMARC after a vendor change.
  3. Normal: New low-volume sender needs review during the next service cycle.
  4. Informational: Weekly authentication summary with no action needed.

Set up the DNS and reporting path

For most clients, start with reporting mode, fix the obvious sender issues, then move toward an appropriate enforcement policy. The exact path depends on mail volume, sender complexity, indirect mail flows, and how quickly the client can approve vendor changes.
Keep the first record simple. Complex records during onboarding slow down the work and make troubleshooting harder. With rua configured, p=none requests reporting without requesting DMARC enforcement. Receivers still apply their other filtering rules. Publish one DMARC policy record at _dmarc.client.example, or use the host label _dmarc if the DNS editor appends the domain.
Starter DMARC reporting recordDNS
Name: _dmarc.client.example Type: TXT Value: v=DMARC1; p=none; rua=mailto:reports@client.example
RFC 9989 is the current DMARC standard. It makes the pct tag historic and adds t=y for policy testing, so new rollout plans should not depend on percentage sampling. Test-mode support varies by receiver; check the enforcement guidance below before using it. If the rua address is external to the publishing domain's organizational domain, the report destination domain must publish the required authorization TXT record. Confirm that authorization and actual report arrival before closing onboarding.
The reporting destination must also cope with aggregate XML volume. Reports are commonly daily summaries, and not every receiver sends them. RFC 9990 defines aggregate reporting. Route reports to a monitored processor or dedicated mailbox with retention, access, and privacy controls.
The DNS setup also needs SPF and DKIM discipline. Publish one SPF record per domain and include only approved sources. Keep SPF evaluation within the limit of 10 terms that trigger DNS queries, including terms in nested includes. DKIM should be active for each legitimate sender that supports it. DMARC passes when at least one method authenticates a domain that matches the visible From domain under the configured relaxed or strict rules.
DNS change workflow
  1. Collect: Document current SPF, DKIM, and DMARC records before edits.
  2. Publish: Add the reporting record and confirm DNS propagation.
  3. Observe: Review real mail flows before changing policy.
  4. Stage: Test quarantine or reject only after approved senders pass.

Use Suped for the managed layer

Suped's product provides the managed layer inside the bundle. It brings together DMARC monitoring, SPF and DKIM monitoring, hosted policy management, alerts, automated issue detection, and steps to fix identified issues.
The MSP value is practical: fewer manual report reviews, faster triage, and a cleaner path for client reporting. Hosted controls support routine policy changes after the client authorizes the initial DNS setup. Hosted DMARC helps manage policy testing and enforcement state, while hosted SPF keeps sender changes manageable when the MSP does not want every vendor update to become a DNS access problem.
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
For multi-client operations, use a multi-tenant dashboard to review domain status across clients. Suped has multi-tenancy for agencies and managed service providers, client switching, client reports, and domain status views. That makes it easier to standardize delivery across many small and mid-sized clients instead of rebuilding the workflow per tenant.
Include reputation visibility when the email security bundle covers deliverability risk. Suped's blocklist monitoring helps track domain and IP listing issues across major blocklists (blacklists), which gives the MSP an early-warning view when mail starts failing outside pure authentication.
The MSP owns the client process, while Suped supplies the data, alerts, hosted controls, and reporting workflow needed to deliver DMARC across a client portfolio. For teams building a broader DMARC for MSPs program, this keeps the service concrete.
Where Suped fits in the stack
  1. Monitor: Track authentication results, source activity, and policy health.
  2. Manage: Use hosted DMARC, hosted SPF, SPF flattening, and hosted MTA-STS where they reduce operational work.
  3. Alert: Notify the team when failures exceed thresholds or unknown senders appear.
  4. Report: Generate client-facing evidence for authentication progress and open risk.

Separate client access and reporting data

A multi-tenant DMARC service needs tenant isolation as well as portfolio visibility. Keep each client's reports and settings in its own workspace. Check role-based access before inviting client users or delegating work to technicians.
  1. Use named technician accounts with multi-factor authentication and only the access each role needs.
  2. Verify that client users can view only their own domains, reports, and alerts.
  3. Agree who receives reports, how long data is retained, and how exports and deletion work at offboarding.
  4. Record who approved each DNS or policy change and remove access when staff or client contracts change.
Keep aggregate reporting as the default. Optional ruf failure reports contain message headers or content and need a separate privacy review. RFC 9991 describes these exposure risks; failure reports are not a guaranteed source of incident alerts.

Package DMARC by scope and service level

Price the recurring service around monitored domains and included work. The client-facing offer should describe the scope, response time, review cadence, and included outcomes. A per-domain monthly fee gives clients a clear billing unit; sender complexity and service desk effort determine the scope. Quote initial remediation separately, define included change effort, and state what happens when a client adds domains or exceeds report-volume allowances.
Use simple package names tied to effort. A monitoring-only offer is useful for clients that need visibility. A managed offer adds fixes and vendor coordination. An enforcement offer adds policy testing and tighter client governance. Complex clients need a custom scope because marketing systems, franchises, acquisitions, and decentralized teams increase the work.

Package

Best fit

Included work

Monitor
Visibility-only scope
Reports and alerts; client owns fixes
Managed
Most SMBs
Fixes and reviews
Enforce
Domains ready for enforcement
Policy staging
Custom
Complex senders
Project scope
Service tiers should state the included work and who owns remediation.
If the commercial model is still being designed, the operational model should come first. The article on how to package DMARC monitoring goes deeper on packaging mechanics, but the key point is simple: scope drives margin.

Set service levels and plan the handoff

The statement of work should separate monitoring from remediation. Define alert coverage, the contracted response window, included change effort, approval dependencies, and what triggers project work. State whether the service operates during business hours or around the clock. Define contractual pauses for client-dependent remediation while keeping monitoring and incident escalation active.

Control

MSP commitment

Client commitment

Handoff evidence

Alerts
Triage by severity within the agreed window
Maintain escalation contacts
Ticket outcome and finding
DNS changes
Draft and verify approved records
Approve sender and change window
Before-and-after DNS evidence
Policy stage
Recommend the stage and rollback plan
Accept business risk
Approval and change record
Offboarding
Export policy state, senders, and open risks
Confirm the new report destination and DNS owner
Signed handoff checklist
Use the handoff evidence to close onboarding, policy changes, and offboarding.
A clean handoff includes the domain inventory, approved sender register, current SPF and DKIM state, the active DMARC record, policy history, unresolved exceptions, and client contacts. During offboarding, authorize the replacement reporting destination first, confirm that it receives reports, then remove the old destination and obsolete reporting authorizations. Transfer hosted policy or SPF dependencies before ending the old service. This sequence avoids a monitoring gap and gives the next owner a recoverable record of every open decision.

Run the monthly operating rhythm

A DMARC bundle fails when nobody reviews the data after setup. Set a monthly rhythm for standard clients and a weekly rhythm during onboarding or enforcement staging. Check alerts as reports arrive between scheduled reviews, including missing reports from previously active reporting sources.
  1. Review: Check authentication pass rates, new sources, policy status, and unresolved issues.
  2. Classify: Distinguish approved senders, forwarding paths, unknown sources, and suspected spoofing; ask the client to verify unfamiliar business services.
  3. Ticket: Assign fixes for SPF includes, DKIM activation, vendor sender changes, and DNS cleanup.
  4. Escalate: Ask the client to approve vendor changes or confirm whether a sender is still needed.
  5. Report: Summarize progress, risks, and next steps in the regular service review.
The review should be short and decisive. Most MSP clients do not need a long explanation of XML reports. They need to know which domains have an active policy, whether approved senders pass DMARC, and what the MSP is fixing next.
Issue steps to fix dialog showing the issue overview, tailored fix steps, and verification action
Issue steps to fix dialog showing the issue overview, tailored fix steps, and verification action

Stage DMARC enforcement around sender readiness

Enforcement is the part clients fear, so the MSP needs a staged path. Do not move a domain to a stricter policy just because the record exists. Move when approved senders pass DMARC consistently, indirect mail risk has been reviewed, and every remaining failure has an owner. Include infrequent business mail in the observation period. RFC 9989 advises against p=reject for general-purpose email domains because indirect mail can fail authentication.
MSP DMARC enforcement workflow showing monitoring, sender fixes, quarantine testing, and reject.
MSP DMARC enforcement workflow showing monitoring, sender fixes, quarantine testing, and reject.
At receivers supporting RFC 9989, t=y lowers quarantine to none and reject to quarantine. Older receivers following RFC 7489 ignore the unfamiliar t tag and can enforce the full p value. Treat the examples below as capable of full enforcement. Verify recipient behavior, review several complete reporting cycles, and document a rollback before increasing p. Keep existing legacy test settings until their replacement has been validated; DNS caching means rollback is not immediate.
Example stages; test mode requires receiver supportDNS
Stage 1: v=DMARC1; p=none; rua=mailto:reports@client.example Stage 2: v=DMARC1; p=quarantine; t=y; rua=mailto:reports@client.example Stage 3: v=DMARC1; p=quarantine; rua=mailto:reports@client.example Optional stage 4: v=DMARC1; p=reject; t=y; rua=mailto:reports@client.example Optional stage 5: v=DMARC1; p=reject; rua=mailto:reports@client.example
Enforcement readiness checks
Use these practical gates before moving a client to a stricter DMARC policy.
Ready
Proceed
Approved senders pass DMARC and failures are understood.
Review
Fix first
A known sender still needs SPF or DKIM repair.
Hold
Investigate
High-volume unknown sender exists.
Document
Record risk
Low-volume noise remains after client approval.

Report progress in client language

The client report should translate technical findings into decisions. Keep it focused on what changed, what is protected, what needs approval, and what the MSP will do next. Long lists of source IPs rarely help a business owner.
Create client report dialog with organization, date range, logo, and language options
Create client report dialog with organization, date range, logo, and language options
A useful report also prevents DMARC from becoming invisible after setup. It shows monitoring coverage and sender changes. Report the DMARC pass rate for approved mail separately from unknown-source failures, include message counts and reporting dates, and show the last report received. A global pass rate distorted by spoofing does not establish whether business mail is healthy.
  1. Progress: Policy stage, approved-mail DMARC pass rate, message counts, and unresolved issues since the last report.
  2. Risk: Unknown senders, failing services, weak domains, and blocklist or blacklist concerns.
  3. Decisions: Vendor approvals, abandoned senders, and timing for stricter DMARC policy.
  4. Next work: Tickets the MSP owns before the next review.

Avoid the common delivery mistakes

Unclear service ownership creates recurring MSP DMARC problems. The technical work is manageable when ownership is clear. The service breaks when nobody owns sender approvals, alert handling, or enforcement decisions.
Mistakes that create support load
  1. One-off setup: Publishing a record without monitoring the reports that follow.
  2. No sender owner: Letting marketing or line-of-business tools send mail without documentation.
  3. Fast enforcement: Moving to enforcement before legitimate services pass DMARC.
  4. Hidden alerts: Sending failure notices to a mailbox nobody checks.
  5. Weak reporting: Giving clients raw authentication data instead of decisions and next steps.
The fix is a service playbook. Define the onboarding checklist, review cadence, ticket routing, client approval path, and enforcement gates before the first client is sold. Standardized workflows make it easier to attach DMARC monitoring to every email security package.

Frequently asked questions

Yes, at least at a monitoring level. Every active client domain needs visibility into authentication results, unknown senders, and policy health. Non-sending domains need an explicit policy that states mail is unauthorized.

Yes, but the service needs a defined DNS change process. The MSP can monitor, recommend, and verify changes while the client or registrar executes the edits.

Consider reject for a dedicated sending domain after approved senders consistently pass DMARC, unknown sources are investigated, and the client accepts remaining exceptions. RFC 9989 advises against reject for general-purpose email domains because mailing lists and other indirect flows can break authentication. Sender readiness and business use determine the policy.

Review weekly during onboarding or enforcement staging, then monthly for stable clients. Check alerts as reports arrive between reviews. Aggregate reporting is delayed and incomplete, so use mail-system evidence for immediate delivery incidents.

Blocklist monitoring fits beside DMARC as a reputation signal. DMARC shows authentication and sender control. Blocklist and blacklist checks help explain delivery problems tied to domain or IP reputation.

RFC 9989 makes pct historic, so new plans should not rely on percentage sampling. Its t=y test mode lowers policy handling only at receivers that support it; older receivers can apply the full p policy. Validate sender readiness and receiver behavior before increasing p or removing legacy test settings.
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