G2

Roni C.

Lead Business Systems Analyst

Financial Services

Small-Business (50 or fewer emp.)

9/26/2026

"Email authentication finally fits into our normal workflow"

5/5

What do you like best about Palisade DMARC?

Email authentication used to live in a separate dashboard that only one person on the team opened. That made it easy to postpone, especially when the rest of our infrastructure work happened through the assistants and tools we use every day. We connected the Palisade MCP server so the team can ask the assistant for the state of a domain, the records it needs, or the tickets that are still open. Someone on call can ask whether a sender is failing DKIM and get the real task back, rather than asking me to remember what we saw last week. It has been useful for planning as well, because we can ask what needs to happen before a domain moves toward enforcement. The MCP connection does not remove the approval step. Changes are still reviewed in Palisade, where we can see the exact record diff and decide whether to publish it. That is a sensible split: quick answers in the workflow we already use, and change control where it belongs. Review collected by and hosted on G2.com.

What do you dislike about Palisade DMARC?

The API reference covers individual endpoints, but I had to infer the end-to-end workflow. More end-to-end implementation examples would shorten the setup. Review collected by and hosted on G2.com.

What problems is Palisade DMARC solving and how is that benefiting you?

The underlying problem was that email authentication knowledge was trapped with one engineer instead of being available through the team's own tooling. Palisade makes live domain, sender, and ticket context available inside the assistant the team already uses. That gives the team a repeatable path forward instead of relying on guesswork or one specialist. Review collected by and hosted on G2.com.