Palisade DMARC Reviews & Product Details

We are a consumer brand, so the inbox is part of the buying experience. Our logo getting shown beside our mail is not a vanity project; it gives people a quick way to recognise a message they should open. Before this, BIMI felt like a collection of technical hurdles: get the domain to enforcement, prepare the logo in the required SVG Tiny PS format, sort out the certificate, publish the record, and make sure the sending mail is still aligned. Palisade gave us one place to work through the authentication and hosted BIMI record instead of juggling a design export, a DNS ticket, and an email security project separately. Our designer's first export was not usable, so the conversion support mattered. We still had to do the certificate work, and that takes longer than anyone wants, but now the mark appears where we expect it to on our authenticated mail. It is a visible result from a project that would otherwise be completely invisible to the commercial team. 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. The logo and certificate requirements could use clearer first time guidance. Review collected by and hosted on G2.com.

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.

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.

Clients understand a logo beside their name in the inbox. They do not need a long explanation of DMARC, but they immediately understand the difference between a message that looks like it came from their brand and one that carries a visible trust signal. That gave us a much better way to start the conversation. We explain that BIMI is not just a logo upload: the domain has to be at DMARC enforcement, the logo has to be prepared in the required format, and there is a certificate step. Palisade gave us a managed path for the BIMI record and the enforcement work that comes before it. The SVG Tiny PS conversion was the part that had stalled earlier projects, especially when the artwork came from a normal brand package. Now the visible outcome makes the wider email-authentication project easier to fund. It also gives the client a reason to care about the underlying work before a spoofing incident forces the conversation. Review collected by and hosted on G2.com.

The report layout is useful, but I still edit the final client summary by hand. The logo and certificate requirements could use clearer first-time guidance. Review collected by and hosted on G2.com.

We knew we had a problem, but we did not know where to start. Procurement had a partial list of vendors, IT had another, and marketing had signed up for services neither group had recorded. Across a large organisation, a list of forty-three senders is not useful unless you can tell which ones are urgent. Palisade read the reporting data, showed us the senders that were actually producing traffic, and turned the work into tickets with severity and score impact. That made the first meeting productive: we handled the sender tied to customer mail first, then the old systems, then the policy milestones. The exact record diff also gave our change owners something concrete to review instead of a vague request from security. We did not treat the Agent as a substitute for separation of duties. It gave the right people better evidence and a proposed fix, then our own process did the approval. That is why the project finally moved forward. Review collected by and hosted on G2.com.

A few approval exports could be easier to tailor for our change board. I would also like finer control over which recommendations become email notifications. Review collected by and hosted on G2.com.

Six things, and I could have named three. The rest were tools people here had signed up for and forgotten. The view splits it into what passed, what failed and what nobody can account for, and the unknown column is the one that kept me up. It is empty now. 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. More historical comparison in the sender view would make trends easier to explain. Review collected by and hosted on G2.com.

The reason our DMARC never got done is that I don't have the registrar password and the person who does left in 2023. Palisade connected to the provider directly, scoped to just the email records, and now approved changes go in without me chasing anyone. I did have to get the account owner on a call once to authorise it. 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.

Our DNS supplier charges by the hour and usually works on a three-day turnaround. That is manageable for a website change, but not when a sender has failed authentication and we are trying to protect client mail. We delegated only the email authentication records to Palisade with CNAMEs and left the registrar, nameservers, website records, and everything else where they already were. For SPF, we use the hosted include instead of maintaining a long public record ourselves. Now the Agent can draft a change, I review the before and after diff, and an approved record is served without a new ticket to the supplier. I like that it is reversible: if we ever remove the CNAME delegation, we are back to managing the records at the provider. The big operational win is that the people who host our site are no longer the bottleneck for every email security fix, while the client still keeps control of the rest of their DNS. Review collected by and hosted on G2.com.

The language is accurate, but some screens still need translation for a non specialist. The initial delegation still depends on access to the current DNS provider. Review collected by and hosted on G2.com.

This is the most common issue I find when I inherit a client: the SPF record grew organically until it had too many DNS lookups. Every marketing service, helpdesk, and payment platform seemed harmless on its own. Three years later, the client is over the limit and their own mail is returning permerror. Trying to explain that to a small business owner is not fun, especially when they are already worried about invoices landing in spam. With Palisade, I confirm the senders that are actually in use and move them behind one hosted SPF include. The public record stays inside the lookup limit, and adding a new sender does not mean reworking the whole record by hand. I can still see which sources are active and talk a client through the decision. What I would like is a clearer portfolio view of how much headroom each client has, but as a way of keeping records within the limit, it has saved a lot of messy cleanup work. Review collected by and hosted on G2.com.

The client facing view is heavier than I need for a quick read only handoff. The include chain explanation could be more visual for non-specialists. Review collected by and hosted on G2.com.

We were an eleven-man team that was supposed to do the duties expected of a much bigger team; hence, it required me to be careful where to invest my time. I tackled the tickets based on how severe they were and whether they impacted our score or not instead of just going by the order in the list. Review collected by and hosted on G2.com.

The first report gave me the ability to dismiss a warning quite fast, but I did need to return to the report after support provided an explanation for what it meant. It would also be beneficial if I could have more options in deciding what recommendations to receive via email. Review collected by and hosted on G2.com.

There are six of us managing forty client domains, and none of us is the designated email-authentication specialist. Before Palisade, that meant difficult issues waited for the one person who had enough patience to read the reports. The Agent changed the first step. It reads the reporting data, identifies the senders that need attention, and opens prioritised tickets with the recommended remediation attached. When a client asks why a campaign is failing, we can start with the sender and the evidence rather than trying to decode XML from scratch. A teammate can pick up a ticket, review the suggested record change, and ask the right client contact to confirm whether the sender belongs there. The actual approval is still deliberate, especially for DNS changes, but the investigation is no longer blocked on one person. For an agency our size, that is the difference between having a process and having a calendar reminder we keep ignoring. Review collected by and hosted on G2.com.

The report layout is useful, but I still edit the final client summary by hand. I would also like finer control over which recommendations become email notifications. Review collected by and hosted on G2.com.