Palisade identified Microsoft 365 and Google Workspace quickly, then grouped SendGrid and Mailchimp into recognizable sources after the first full aggregate report cycle. The support desk sender first appeared as shared infrastructure, and we had to tag the owner before the reports made sense for handoff. The DKIM pass on the marketing subdomain stayed connected to the parent-domain policy plan, and the forwarded SPF failure was explained as forwarding rather than spoofing.

ProDMARC presented Microsoft 365 and Google Workspace cleanly and made SendGrid evidence easy to inspect at the domain and source level. Mailchimp was visible, but the unknown sender needed more drilldown before we were comfortable classifying it. The SPF pass with visible-from mismatch was handled as an authentication risk, and the unauthorized spoof sample was easier to prioritize after reviewing the attack and threshold views.

In Palisade, we added the primary domain, the marketing subdomain, and the parked domain in one session, then connected Microsoft 365, Google Workspace, SendGrid, Mailchimp, and the support desk sender as approved services. The unknown sender surfaced with enough context to assign a likely owner, although the final classification still required our decision. The forwarded mail SPF failure had a plain explanation, so it did not get mixed into the spoofing queue.

In ProDMARC, the setup flow felt more dependent on trial onboarding and support context, especially when moving beyond the primary domain. The unknown sender took extra drilldown because the first view emphasized raw authentication evidence over ownership. The forwarded mail SPF failure was understandable after we checked the investigation detail, but it was less obvious on the first pass.

For Palisade, DNS handoff was direct: the product gave us the TXT values, the monitoring state, and a clear view of what changed after the records propagated. Our escalation test around the support desk sender produced a practical answer, but the depth depended on tier expectations. Enterprise onboarding was visible as a paid path rather than something we did not fully verify in the self-serve test.

For ProDMARC, support felt central to the experience. The strongest moments came when we paired the dashboard with guidance on the spoof sample, the SPF mismatch, and the forwarded mail failure. The tradeoff is that DNS handoff and enterprise onboarding expectations were less transparent from pricing and public plan material alone.

Palisade handled the three-domain setup in a way that mapped cleanly to client-style grouping: the primary domain, marketing subdomain, and parked domain stayed separate for review without losing the overall policy plan. Recurring reporting and white label language were useful for MSP handoff. The main gap was price certainty for MSP scale, since the per-domain model was public but the actual per-domain amount was not.

ProDMARC was better suited to an internal security or infrastructure team than to a client-heavy MSP workflow. The recurring reports were readable, and the enterprise support cues matched a team that wants review calls and escalation. Account separation, client handoff, and repeatable domain grouping felt more manual during our test.