Palisade DMARC Reviews & Product Details

I am not technical, and I was worried about breaking our email while trying to secure it. Each change shows up as a diff: here is what is live, here is what is proposed. Nothing goes into our zone until I approve it. That is why I felt comfortable doing this. Review collected by and hosted on G2.com.

I had to contact support to confirm how an old sending service should be treated. They resolved it, but the answer would have been useful directly in the workflow. Clearer propagation status would make the last step easier to trust. Review collected by and hosted on G2.com.

We send as our clients' domains, so their deliverability is our problem whether or not it is our fault. Before a big send I open the view and check nothing has moved into the failed column. Twice this year it caught a client's IT team adding a tool without telling anyone, and we knew before the campaign went out. Review collected by and hosted on G2.com.

I would like a faster way to give a client a read only view without showing the full workspace. More historical comparison in the sender view would make trends easier to explain. Review collected by and hosted on G2.com.

Our abandoned cart sequence was half arriving, which looks like weak copy rather than a fault. Seeing failed volume climb on the chart is what made it obvious. I rewrote that sequence twice before finding out, and every A/B result from that period is worthless. I would still like a before and-after view around a fix. Review collected by and hosted on G2.com.

The product finds the failing sender, but it cannot always tell me which campaign or automation owns it. More historical comparison in the sender view would make trends easier to explain. Review collected by and hosted on G2.com.

A client blamed us for six months of poor open rates. Palisade named their own CRM as the service failing SPF, misconfigured before we ever met them. Agencies get blamed for deliverability because we are the ones who pressed send, and being able to name the actual sender is worth more than any other feature here. Review collected by and hosted on G2.com.

The dashboard can get noisy when several client domains have the same low priority warning. More historical comparison in the sender view would make trends easier to explain. Review collected by and hosted on G2.com.

Our insurer's renewal form asked a very blunt question: do you enforce DMARC? At the time, we were still at p=none, so the honest answer was no. The difficulty was not deciding that we wanted to improve it. It was proving which systems still sent mail for us and making sure invoices, order notices, and customer communications would keep working as we tightened the policy. The Deliverability view gave us the list by sender, volume, and authentication status instead of one generic warning. We worked through the failures, checked the legitimate senders, and could show finance what was changing before we moved from monitoring to quarantine and then reject. Seven weeks later, the renewal answer was different and we had the evidence behind it. Finance stopped having to take this on faith, and the insurer got a clear record of the work rather than a promise that we were looking into it. Review collected by and hosted on G2.com.

The compliance evidence is useful, but tailoring it to a specific questionnaire still involves manual work. More historical comparison in the sender view would make trends easier to explain. Review collected by and hosted on G2.com.

Our change board is not interested in whether a tool is clever. They want to know exactly what it will change, who approved it, and how we can explain that decision six months later. We connected our DNS provider through its own authorisation window, so there was no shared registrar password and no request to move the rest of our zone. When the first DKIM change came up, Palisade showed the current record and the proposed value side by side. The ticket included the sender it related to and the reason the change was needed. I took that to the board, got the approval, and only then did it publish. Afterwards, the record was live in our own zone and the verification confirmed receivers could see it. That is a very different conversation from asking the board to trust an autonomous DNS tool. It fit our process rather than asking us to make an exception for it. Review collected by and hosted on G2.com.

The product fits our control model, but bulk changes across many domains still deserve a stronger review screen. Clearer propagation status would make the last step easier to trust. Review collected by and hosted on G2.com.

Before this, every DNS change meant emailing the people who host our website and waiting for a reply. We connected the provider once. Now I see the current value, the proposed value, and the approval button in one place. That is all I need. Review collected by and hosted on G2.com.

The initial setup took longer than I expected because I was waiting on a DNS change and learning the names of a few sending services. Clearer propagation status would make the last step easier to trust. Review collected by and hosted on G2.com.

We had been marking addresses as gone away when our mail was actually being rejected. Palisade named the sending service that was failing and showed how much of our volume it was. Ninety people is a meaningful part of a list our size and we had given up on every one of them for a technical reason nobody could see. Review collected by and hosted on G2.com.

The setup is manageable, but some of the terminology still assumes more email knowledge than our team has. More historical comparison in the sender view would make trends easier to explain. Review collected by and hosted on G2.com.

We run eight brand domains plus a pile of defensive registrations. Palisade's flat volume pricing includes all of them, which ended the per-domain math we did with our previous vendor every time marketing launched something. Hosted DNS is the other keeper: records are delegated once by our DNS team, and after that every fix is drafted by the agent and deployed from Palisade after approval. No more DNS change tickets idling in a queue. Review collected by and hosted on G2.com.

When a delegated record updates, I'd like clearer in-app status on propagation. It's usually fast, but 'is it live yet' still sends me to a terminal. Review collected by and hosted on G2.com.

Palisade has an MCP server, so I connect it and ask which of my clients is failing DKIM this week without opening anything. The answer comes back with the actual ticket behind it. Approvals still happen in Palisade with me clicking, which is right. Nobody expects a DMARC tool to meet you where you already work. Review collected by and hosted on G2.com.

The client facing view is heavier than I need for a quick read only handoff. More end to end implementation examples would shorten the setup. Review collected by and hosted on G2.com.