Palisade recognized Microsoft 365 and Google Workspace quickly, then separated SendGrid and Mailchimp into distinct sources with enough detail for owner assignment. In the DKIM pass on a subdomain case, it did not treat the pass as a full green light for the parent domain, which helped us keep the marketing subdomain policy separate from the corporate domain. The unknown sender was not perfectly named on first pass, but the workflow gave us a practical place to classify it and connect it to an action.

DMARC Monitor covered the basics cleanly: Microsoft 365 and Google Workspace were visible, SendGrid and Mailchimp appeared in grouped reporting, and the spoof sample was easy to find in the review output. The SPF pass with visible From mismatch was visible as an authentication problem, but the product leaned more on report interpretation than guided repair. Unknown sender classification took more manual work, so the feature set fit periodic review better than daily remediation.

Onboarding the corporate domain, marketing subdomain, and parked domain was quick, with DMARC record instructions that separated monitoring from enforcement changes. The unknown sender was easy to find after filtering by volume and authentication result, and the forwarded mail SPF failure had enough context to avoid treating it like the spoof sample.

DMARC Monitor's setup flow was understandable, but adding the three domains felt more sequential and less operator-focused. We found the unknown sender through report review rather than an action queue, and the forwarded SPF failure was visible without enough explanation for a junior admin to close it without help.

During setup, Palisade's public plan structure and in-product direction made DNS handoff cleaner for the primary domain and parked domain. The paid tiers tied support to DMARC engineer help, managed DNS records, priority human support, and enterprise offload, so escalation expectations were clearer before a policy change.

DMARC Monitor's Bronze, Silver, and Gold plans set an expectation of standard support plus one review meeting, while Advance adds quarterly review meetings. That model works for teams that want periodic interpretation, but our test left more unanswered detail around urgent escalation, exact DNS ownership, and enterprise onboarding steps.

Palisade handled the MSP-style parts of the test better: domain grouping was clearer, client handoff had a better path through white label reporting and portal-style controls, and role-based access made account separation easier to reason about. For enterprise buyers, the custom plan and managed execution route fit teams that want Palisade to carry more of the DMARC operational load.

DMARC Monitor fit SMB and review-led use cases better than MSP operations. Active and inactive domain allowances were easy to map to the corporate domain, marketing subdomain, and parked domain, and recurring reports were usable for status updates. Client handoff stayed more manual because we did not see strong account separation, portal controls, or recurring owner notes for different clients.