LetsDMARC alternative
LetsDMARC vs Palisade in 2026
LetsDMARC is Libraesva's DMARC product for reporting, guided authentication setup, hosted SPF, and policy monitoring. Palisade adds an approval-based AI-agent workflow that investigates senders, drafts fixes, and proposes each enforcement step.
Our verdict: Pick LetsDMARC if you want a Libraesva-backed DMARC console with guided configuration, hosted SPF, multi-tenant administration, and alerts that can reach email, Microsoft Teams, or Slack. Pick Palisade if you want an AI agent to do the investigation and drafting before your team approves each change.
Samuel Chenard · CEO & Co-Founder, PalisadeSource checks through 2026-08-261 domain free up to 1,000 emails/month
ChatGPT
Claude
Gemini
Perplexity
Grok
Palisade
Palisade is free for one domain, up to 1,000 emails a month. Paid IT-team plans are sized by email volume. Start a 15-day full-product trial with no credit card.
Which one is right for you?
Best for Teams that prefer an operator-led workflow
Best for MSPs and IT teams responsible for multiple domains
- You want guided DMARC, SPF, and DKIM configuration in a Libraesva product console.
- You need hosted SPF with flattening, BIMI monitoring, DNS timelines, and tenant administration.
- Your team prefers an operator-led workflow and can procure through a quote rather than a published rate card.
- You want the agent to investigate every sender, draft every fix, and propose each policy step while your team approves before anything ships.
- You want the work organized around prioritized tickets and review instead of asking operators to turn every report finding into a remediation plan.
- You need Palisade's flat IT-team pricing or portfolio-based MSP pricing, with current volume and set-up-domain limits stated up front.
Free for one domain, up to 1,000 emails a month. Paid IT-team plans are sized by email volume. Start a 15-day full-product trial with no credit card.
Where the day-to-day work actually differs
| Feature | LetsDMARC | Palisade |
|---|---|---|
| DMARC operations | ||
| AI agent that investigates senders, drafts fixes, and proposes policy stepsWhether an agent prepares sender fixes and policy steps for approval.Libraesva advertises guided configuration, explanations, and operator-led policy adjustments, but does not advertise an enforcement agent that investigates, drafts, and proposes each step (checked 2026-08-26). Source (2026-08-26) | Not advertised | Agent drafts and proposes |
| DMARC aggregate reporting and source/result analysisWhether aggregate reports show sending sources and authentication results.Source (2026-08-26) | Supported | Agent analyzes reports |
| Guided DMARC, SPF, and DKIM configurationWhether configuration guidance covers DMARC, SPF, and DKIM.Source (2026-08-26) | Supported | Agent drafts configurations |
| DNS and brand protection | ||
| Hosted SPF and SPF flatteningWhether SPF records can be hosted and flattened before publication.Source (2026-08-26) | Supported | Hosted SPF flattening |
| BIMI support and monitoringWhether BIMI records and related brand indicators are managed or monitored.Source (2026-08-26) | Supported | Hosted BIMI records |
| MSP administration | ||
| Tenant-based multi-domain administrationWhether separate tenant workspaces can manage multiple domains.Source (2026-08-26) | Supported | Multi-tenant MSP workflows |
| Operations and integrations | ||
| Alerts through email, Microsoft Teams, and SlackWhether operational alerts can reach the named notification channels.Source (2026-08-26) | Supported | Agent flags new tickets |
| Administrative API for domains, hosted DNS, and alertsWhether other systems can manage domains, hosted DNS, and alerts through an API.Source (2026-08-26) | Supported | API on every plan |
| Native ConnectWise, HaloPSA, or Autotask integrationsWhether the named PSA systems connect directly to the workflow.The Libraesva product page, pricing page, trial form, and LetsDMARC manual reviewed today do not advertise native ConnectWise, HaloPSA, or Autotask integrations; this is an absence of public advertising, not a claim that an undisclosed integration is impossible (checked 2026-08-26). Source (2026-08-26) Source 2 (2026-08-26) Source 3 (2026-08-26) | Not advertised | Native PSA integrations |
| DNS and brand protection | ||
| DNS timeline and ongoing domain monitoringWhether DNS changes and domain status are tracked over time.Source (2026-08-26) | Supported | Agent monitors records |
| AI and automation access | ||
| Public REST or GraphQL reference for customer-built automationWhether customers can build against a published REST or GraphQL endpoint reference.Libraesva's LetsDMARC release notes announce an administrative API for Domain, Hosted DNS, and Alerts management, but the public LetsDMARC manual and documentation index do not advertise a REST or GraphQL endpoint reference or API plan availability (checked 2026-08-27). Source (2026-08-27) Source 2 (2026-08-27) Source 3 (2026-08-27) | No public reference | REST API published |
| MCP server for connecting AI assistants to domain dataWhether an AI assistant can reach the product's data directly.Libraesva's public LetsDMARC documentation index and manual list product documentation and operational areas, but do not advertise an MCP server or an AI-assistant integration (checked 2026-08-27). Source (2026-08-27) Source 2 (2026-08-27) | No MCP server listed | MCP server published |
| AI-supported source-domain organization lookupWhether the vendor advertises AI work inside the product and explains what it does.LetsDMARC's release notes advertise Source Domain Organization Lookup, which identifies the organization associated with message origins using OSINT and LibraCyber AI (checked 2026-08-27). Source (2026-08-27) | AI lookup advertised | Agent drafts and proposes |
| Automated report delivery outside the dashboardWhether scheduled exports, webhooks, or a data feed can deliver report data without the product UI.Libraesva's release notes advertise CSV exports from the domain overview page and for license usage, but do not advertise scheduled exports, webhooks, or a report-data feed in the public LetsDMARC manual or release notes (checked 2026-08-27). Source (2026-08-27) Source 2 (2026-08-27) | No automated delivery listed | REST API published |
| Reporting evidence | ||
| Source and authentication-result viewsWhether operators can review aggregate reports by sending source and authentication result.LetsDMARC's manual separates DMARC reports into By Source and By Results views. Palisade's features page publishes SPF and DKIM result analysis for each sending source (checked 2026-08-28). Source (2026-08-28) Source 2 (2026-08-28) | By Source and By Results | Per-sender result analysis |
| SPF and DKIM alignment viewsWhether operators can inspect alignment by authentication method.LetsDMARC's manual documents SPF and DKIM alignment sections and scenarios, and its product page says explanations help users pinpoint and fix alignment issues. Palisade's features page publishes SPF and DKIM alignment status for sending sources plus DMARC compliance and alignment tracking (checked 2026-08-28). Source (2026-08-28) Source 2 (2026-08-28) Source 3 (2026-08-28) | Alignment sections documented | Alignment status per sender |
| Pricing transparency | ||
| Published numeric entry priceWhether a buyer can see a numeric starting price before contacting sales.Libraesva's pricing page presents a Request Pricing form and does not advertise a numeric LetsDMARC price. Palisade publishes a $0 Free plan and IT-team pricing from $19 per month (checked 2026-08-28). Source (2026-08-28) Source 2 (2026-08-28) | Quote required | $0 Free; IT from $19/mo |
| Published billing unit and plan limitsWhether the public pricing page states what is metered and the limits buyers receive.Libraesva's pricing form asks for approximate mailbox count and deployment, but does not advertise a LetsDMARC billing unit, plan-limit schedule, or overage terms. Palisade publishes its IT-team email-volume tiers and set-up-domain limits (checked 2026-08-28). Source (2026-08-28) Source 2 (2026-08-28) | Not advertised | Volume and setup limits |
| Published post-trial price and card requirementWhether a buyer can see the cost and payment requirement that follow the trial.Libraesva's trial page advertises a free trial with no commitment, but does not advertise LetsDMARC's post-trial price or credit-card requirement. Palisade publishes its post-trial plan options and says the trial does not require a card (checked 2026-08-28). Source (2026-08-28) Source 2 (2026-08-28) | Not advertised | Published; no trial card |
Want to compare the workflow yourself? Try Palisade free with one domain and up to 1,000 emails a month.
Palisade 96 vs LetsDMARC 74, and why
Both products are scored on the same eight dimensions the comparison hub uses, so the figures here are the figures there. Four are derived from vendor facts that each carry a source and a checked date. Four are editorial, marked as such below, and each states its reasoning and its source.
Each dimension is out of 10 and the total is the raw sum out of 80, rescaled to 100 — the raw figure is printed beside it so the conversion is checkable rather than a black box. Scored on what each vendor publishes, not on how the product feels in use. Editorial dimensions last reviewed 2026-08-30.
How reachable the product is from your own software and AI tools. 10 = a documented API on every plan plus a published MCP server. 6 = an API, gated to a tier or to a sales conversation. 3 = no programmatic access advertised.
LetsDMARC publishes an administrative API for domains, hosted DNS, and alerts, but Libraesva publishes no API plan coverage or MCP server (checked 2026-08-28). Source (2026-08-28)
Palisade publishes a REST API and a remote MCP server on every plan, making the same domain data and remediation workflows available to connected software. Source (2026-08-30)
How much of the report analysis is done for you. 10 = the platform turns raw report data into a prioritised, actionable queue on its own.
Source organization lookup, Domain Guardian, DNS alerts, CSV operations, multi-channel notifications, and an administrative API automate ongoing work. Source (2026-08-28)
Report data is analysed into a prioritised list of sender, SPF, DKIM and DMARC issues, so nobody reads raw XML. Source (2026-07-29)
How much of the work the vendor's own software does. 10 = it identifies the sending sources, drafts the SPF and DKIM fixes each one needs, and proposes the next policy step. 6 = it applies the records for you, but a person decides what to fix and when to advance. 3 = it reports, and every change is yours to make. A vendor whose team does the work rather than its software scores here on the software alone.
LetsDMARC hosts DMARC and SPF records, but its published workflow has a person identify authorized sources, adjust the configuration, and decide when to enforce the policy. Source (2026-08-28)
The agent investigates each sender, drafts the SPF and DKIM changes it needs, and proposes the next policy step; a human approves before deployment. Source (2026-08-30)
10 = full pricing published. 6 = some tiers published, rest quote-gated. 3 = quote only.
No complete first-party public price list or plan limits were located; commercial pricing follows a quote or channel-sales path. Source (2026-08-28)
Published: free plan, then flat monthly plans by email volume from $19/mo Source (2026-08-30)
10 = hosts the records for you. 6 = partial or add-on. 3 = you manage your own DNS.
Yes: the product publishes managed DMARC and SPF records, DKIM configuration, hosted SPF, TLS reporting, and BIMI monitoring. Source (2026-08-28)
10 = a genuine free plan. 6 = time-limited trial only. 3 = no free access.
No ongoing free service plan is published; release notes describe time-limited MSP trial domains. Source (2026-08-28)
Free plan: one domain, up to 1,000 emails/mo, 14-day report history, no credit card, plus a 15-day full-product trial Source (2026-08-30)
10 = a real MSP program with multi-tenant management. 6 = partial. 3 = none.
Yes: LetsDMARC publishes MSP tenant capabilities, child-tenant administration, SSO, trial domains, and licence controls. Source (2026-08-28)
How much work it takes to get a domain from p=none to p=reject. 10 = the platform (or the vendor's team) gets you there without manual DNS edits.
Managed DMARC and SPF, record wizards, alignment explanations, tenant controls, and continuous monitoring provide an extensive enforcement workflow. Source (2026-08-28)
The DMARC Agent detects when a domain's authentication and alignment are ready for the next policy stage and proposes the move, but a human still approves and applies it, so it is not fully hands-off. Source (2026-07-29)
Reporting clarity vs remediation planning
LetsDMARC covers the reporting and configuration foundation
LetsDMARC is a real DMARC product inside Libraesva's security portfolio, not a generic email-security label. Its product page describes instant insight into email flows, DMARC setup, domain protection, deliverability, SPF flattening, and a console for configuring DMARC, DKIM, SPF, and BIMI. The public manual is organized around DMARC reports, source and result views, reporters, alignment, domain administration, and policy stages from observation through quarantine and reject. That gives an internal IT team the evidence it needs to see which sources authenticate and where alignment needs work. Source (2026-08-26) Source 2 (2026-08-26)
The honest parity matters: both LetsDMARC and Palisade can be used to centralize DMARC report evidence, inspect authentication results, and work through SPF, DKIM, and DMARC settings. LetsDMARC also advertises hosted SPF and macros that flatten the record while hiding sending sources. This is a meaningful fit for a team whose first requirement is a guided console for authentication hygiene and policy visibility. The key comparison is what happens after the console identifies a sender or alignment issue, not whether the product has a report dashboard. Source (2026-08-26) Source 2 (2026-08-26)
- By Source and By Results
- Alignment sections documented
- Per-sender result analysis
- Alignment status per sender
- Investigates. Works out what is sending as your domain, and which of it is legitimate.
- Drafts the fix. Prepares the SPF and DKIM record changes each sender needs, rather than describing them.
- Proposes the policy step. Moves toward p=reject when the evidence supports it. You approve before anything ships.
Operator guidance vs agent preparation
The workflow difference appears at the enforcement step
Libraesva describes a guided, operator-led path: identify legitimate sources, monitor in observation mode, make adjustments, and then enforce a policy that tells receiving systems to reject or junk failing messages. Its product page says that explanations help users pinpoint and fix alignment issues and implement the policy. That is a clear workflow, and the product documentation exposes the policy stages an operator needs to understand. The public material does not describe an agent that takes the evidence, drafts the complete fix, and proposes every next policy step for approval. Source (2026-08-26) Source 2 (2026-08-26)
Palisade is built around a different division of labor. Its agent investigates every sender, drafts every fix, and proposes each policy step—you approve before anything ships. It analyzes aggregate reports, identifies senders and authentication problems, drafts SPF and DKIM changes, files prioritized tickets, detects policy readiness, and carries domains toward p=reject with approval at each step. That distinction becomes more important as a portfolio grows: a dashboard can make the work visible, while the agent prepares the work so an operator reviews a bounded change instead of starting the investigation from a raw finding. Source (2026-08-26)
- Not advertised
- Supported
- Supported
- Agent drafts and proposes
- Agent analyzes reports
- Agent drafts configurations
- Investigates. Works out what is sending as your domain, and which of it is legitimate.
- Drafts the fix. Prepares the SPF and DKIM record changes each sender needs, rather than describing them.
- Proposes the policy step. Moves toward p=reject when the evidence supports it. You approve before anything ships.
Tenant controls vs integration reach
Multi-tenant controls and alert channels are genuine parity
LetsDMARC's manual includes tenants, impersonation, users, and domains as first-class administration areas. Libraesva's release notes also describe moving domains between parent and child tenants and fixing permission behavior for subtenants. For a provider or group with separate business units, that is useful evidence that the platform has a real account hierarchy rather than only a single-domain dashboard. The same release history identifies MSP features including SSO, TLS reports, and BIMI, so LetsDMARC's multi-tenant story should be evaluated as a product surface, not dismissed as a marketing claim without operational detail. Source (2026-08-26) Source 2 (2026-08-26)
Alerting is another area where the comparison should stay honest. Libraesva documents an alert feature, and its public release notes say LetsDMARC added Microsoft Teams and Slack notification mediums. The same release notes describe an administrative API for domain, hosted-DNS, and alert management. Those are useful integration primitives for a team that already has its own routing and ticket conventions. They are not the same thing as Palisade's native PSA coverage, and the reviewed LetsDMARC pages do not advertise ConnectWise, HaloPSA, or Autotask connectors. A service provider should ask Libraesva whether an API workflow can cover the exact PSA actions it needs before assuming parity. Source (2026-08-26) Source 2 (2026-08-26) Source 3 (2026-08-26)
Native PSA integrations
Palisade imports client domains straight from these three. LetsDMARC's own coverage is stated above, from their site.
- ConnectWise PSA
- Autotask
- HaloPSA
- Supported
- Supported
- Not advertised
- Agent flags new tickets
- API on every plan
- Native PSA integrations
Quote discovery vs price clarity
Buying and deployment: quote first, then confirm the operating fit
The public Libraesva pricing journey is quote-based. Its Get Pricing page asks for an approximate mailbox count, deployment choice, product of interest, company information, and country, but it does not show a LetsDMARC plan table or numeric rate. That means a buyer cannot use the public page to model cost by domain, mailbox, email volume, retention, or overage. The fair conclusion is that pricing is not published; the quote may contain terms that the public page does not expose, so those details should be requested in writing before procurement. Source (2026-08-26)
Libraesva does publish a free 30-day trial page that lists LetsDMARC as a product of interest and describes the trial as having no commitment. The form asks for deployment and data-center information, but the public page does not state LetsDMARC's post-trial price, retention, mailbox limit, or credit-card mechanics. Palisade's public model is easier to model before a call: the Free plan covers one domain and 1,000 emails/month, paid IT plans are flat monthly prices by email volume with current set-up-domain limits, and MSP pricing is quoted per client domain by portfolio size. The decision is therefore not only feature coverage; it is whether your team wants quote discovery before it can compare economics. Source (2026-08-26) Source 2 (2026-08-26)
What each side charges
Three points on each published range: the cheapest plan, one in the middle, and the top of what the vendor publishes. Every plan on both sides is in the pricing section further down.
- LetsDMARCNot published: contact Libraesva for pricing
The public form lets a buyer select LetsDMARC and provide approximate mailboxes and deployment details; plan limits and billing units are not listed.
- Free$0
1 domain, your own, capped at 1,000 emails/mo
- IT teams: up to 500,000 emails/mo$59/mo ($47/mo billed annually)
Same product: 6 set-up domains, pick the tier that matches your sending
- Enterprise (more than 2.5M / month)Custom
Custom volume, retention, and terms
- Quote required
- Not advertised
- Not advertised
- $0 Free; IT from $19/mo
- Volume and setup limits
- Published; no trial card
Dashboard access vs programmatic access
LetsDMARC's administrative API announcement and AI source lookup, without a public MCP server
Libraesva's LetsDMARC release notes announce an administrative API for Domain, Hosted DNS, and Alerts management. The same notes advertise Source Domain Organization Lookup, which uses OSINT and LibraCyber AI to identify the organization associated with message origins. The public LetsDMARC manual lists configuration, reporting, managed DNS, alert, Domain Guardian, and BIMI documentation, but does not advertise an MCP server, AI-assistant integration, public REST or GraphQL endpoint reference, scheduled export, webhook, or data feed. The release notes list CSV exports from a domain overview page and for license usage, which are dashboard exports rather than a documented scheduled delivery. Source (2026-08-27) Source 2 (2026-08-27) Source 3 (2026-08-27)
Palisade publishes an MCP server and a REST API. Its agent investigates senders, drafts SPF and DKIM fixes, and proposes each policy step. A human approves before anything ships.
Reachable from your own AI tools
Palisade's MCP server exposes 30 tools over OAuth, so the assistant your team already uses can read domains, pull the exact records to publish and work the task queue. These are the clients the connection guide walks through.
- Claude
- ChatGPT
- Cursor
- Windsurf
- Any MCP client
- No public reference
- No MCP server listed
- AI lookup advertised
- REST API published
- MCP server published
- Agent drafts and proposes
Still deciding between LetsDMARC and Palisade? See what changes with Palisade.
1 domain free up to 1,000 emails/month
Microsoft 365
Zoho Mail
The agent does the heavy lifting
Sources identified, SPF and DKIM fixes drafted, each policy step proposed. You approve; nothing ships on its own.
Connect your AI with MCP
30 tools over MCP, so your assistant reads your domains and works the queue.
Connect your DNS manager directly
Approved records go into your own zone at your own provider, across 64. No credentials reach us.
“We evaluated many DMARC providers before choosing Palisade. The quality of their product, the responsiveness and friendliness of their team and their rapid progress on their product roadmap made it a no-brainer for us to move forward.”
LetsDMARC pricing explained (and how Palisade compares)
Libraesva does not publish a LetsDMARC rate card on its public pricing page. The page is a request-pricing form that asks for the product, approximate mailbox count, deployment, company details, and country, so a buyer needs a quote to confirm the commercial terms.
What you'd actually pay
The same five buyer sizes on every comparison, so a shape carries from one page to the next.
1 domain, up to 1,000 emails a month
2 set-up domains, up to 100K emails a month
10 set-up domains, up to 1M emails a month
20 set-up domains, up to 2.5M emails a month
Client domains under management, any volume
Palisade’s figures are derived from its published tiers. LetsDMARC figures read from their pricing page on 2026-08-28. Plans and prices may have changed since.
How LetsDMARC prices
- No public dollar, euro, or pound price was shown for LetsDMARC when the pricing page was checked on 2026-08-26.
- The pricing form requests approximate mailboxes and deployment, but does not publish a per-domain, per-mailbox, email-volume, retention, or overage schedule.
- The public trial page advertises a free 30-day trial with no commitment. It does not publish a LetsDMARC post-trial price or card requirement on the page reviewed.
How Palisade prices
- Palisade publishes a Free plan at $0 for one domain and up to 1,000 emails/month, followed by flat IT-team plans at $19, $29, $59, $99, and $249/month by email volume, with 20% off annually.
- New paid IT subscriptions include 2, 3, 6, 10, or 20 set-up domains by tier; adding domains remains free and unlimited, and only setup is metered against the tier.
- MSPs pay per client domain at a portfolio-based rate that improves as the portfolio grows. The MSP's own domain is included as a free Not-For-Resale license; Palisade does not publish the dollar rate card.
- Palisade offers a 15-day full-product trial with no credit card required. Compare this with Libraesva's published 30-day free-trial statement, then confirm the exact LetsDMARC quote before treating the trial as a budget assumption.
LetsDMARC pricing read from their public pricing page on 2026-08-26.Plans and prices may have changed since.
Try Palisade free on one domain, or start a 15-day full-product trial with no credit card.
What each one covers, and where it stops
Published facts only, read from each vendor's own material. Neither column describes a hands-on trial, because we have not run one.
LetsDMARC is Libraesva's DMARC product for reporting, guided authentication setup, hosted SPF, and policy monitoring. Its console covers DMARC, DKIM, SPF, and BIMI configuration, and its public manual covers reports, source and result views, alignment, domain administration, and policy stages. It gives internal IT teams the evidence to identify authentication sources and alignment work.
LetsDMARC follows a guided, operator-led path: teams identify legitimate sources, monitor in observation mode, make adjustments, and then enforce policy. Its manual also lists tenant, user, domain, permission, and impersonation controls, while its release notes identify MSP features. Pricing is quote-based, so buyers need a quote to confirm commercial terms.
Palisade is built around an agent that does the DMARC work rather than reporting on it. It identifies every sending source, drafts the SPF and DKIM changes each one needs, and proposes the next policy step when the evidence supports it.
The agent investigates every sender, drafts every fix, and proposes each policy step, you approve before anything ships.
- Supports DMARC aggregate reporting and source and result analysis
- Supports guided DMARC, SPF, and DKIM configuration
- Supports hosted SPF and SPF flattening
- Supports tenant-based multi-domain administration
- Supports alerts through email, Microsoft Teams, and Slack
- The agent investigates senders and drafts the fix, so the work arrives prepared rather than as a list of findings
- Hosted SPF, DKIM and DMARC on redundant managed DNS, so an approved change can be carried out rather than handed off
- Portfolio workflow for MSPs, with ConnectWise, HaloPSA and Autotask integrations and a free NFR domain
- An MCP server and a REST API, so the same data and workflow are reachable from the AI tools a team already uses
- Does not advertise an agent that investigates senders, drafts fixes, and proposes policy steps
- Does not advertise named ConnectWise, HaloPSA, or Autotask integrations
- Does not advertise a public REST or GraphQL endpoint reference
- Does not advertise an MCP server or AI-assistant integration
- Does not advertise scheduled exports, webhooks, or a report-data feed
- Every policy change waits for a human approval, by design: nothing ships on the agent's own authority
- MSP pricing is quoted per client domain rather than published as a rate card
- Plans are sized by monthly email volume, so a low-domain, high-volume sender lands on a higher tier than domain count alone suggests
- Starts at
- Not published; quote required
- Free trial
- 30 days, no commitment
- Billing unit
- Not published
- MSP model
- Not published at 25 domains
- Starts at
- Free, then $19/mo
- Free tier
- 1 domain, up to 1,000 emails/month
- Trial
- 15 days, full product, no credit card
- MSP model
- Quoted per client domain, portfolio-based
“Palisade made it so easy for us to get our blue verified checkmark and achieve our BIMI compliance”
Sources and further reading
Source checks run through 2026-08-26; every entry keeps its individual check date.
- Libraesva LetsDMARC product page
Checked 2026-08-26
- Libraesva pricing request page
Checked 2026-08-26
- Libraesva free trial page
Checked 2026-08-26
- LetsDMARC manual: reports and configuration
Checked 2026-08-26
- LetsDMARC managed DNS documentation
Checked 2026-08-26
- LetsDMARC tenants documentation
Checked 2026-08-26
- LetsDMARC alert documentation
Checked 2026-08-26
- LetsDMARC release notes
Checked 2026-08-26
- Palisade DMARC Agent
Checked 2026-08-26
- Libraesva LetsDMARC product page (rechecked)
Checked 2026-08-27
- Libraesva pricing page (rechecked)
Checked 2026-08-27
- Libraesva LetsDMARC documentation index
Checked 2026-08-27
- LetsDMARC manual (rechecked)
Checked 2026-08-27
- LetsDMARC release notes (rechecked)
Checked 2026-08-27
Palisade vs LetsDMARC: FAQ
What is LetsDMARC?
LetsDMARC is Libraesva's DMARC product. Its public product page describes DMARC setup, email-flow insights, SPF flattening, policy monitoring, BIMI support, and a console for DMARC, DKIM, SPF, and BIMI configuration. Its manual covers reports, sources, results, reporters, alignment, tenants, managed DNS, timelines, and alerts.
How much does LetsDMARC cost?
Libraesva does not publish a LetsDMARC rate card on its public pricing page. The page is a request-pricing form that asks for the product, approximate mailbox count, deployment, company, country, and contact details. Ask for the quote's billing unit, domain or mailbox limits, retention, overage terms, and renewal terms before comparing it with a self-serve plan.
Does LetsDMARC offer a free trial?
Yes. Libraesva's public trial page advertises a free 30-day trial with no commitment and lists LetsDMARC as a product of interest. The page does not publish LetsDMARC's post-trial price or card requirements, so confirm those terms with Libraesva.
Does LetsDMARC have an AI enforcement agent?
Libraesva advertises guided configuration, report insights, explanations, and operator-led policy adjustments. The public LetsDMARC product and documentation pages reviewed for this comparison do not advertise an agent that investigates every sender, drafts every fix, and proposes each policy step for approval. Palisade's agentic workflow is designed around that handoff.
Does LetsDMARC support MSP or multi-tenant operations?
LetsDMARC's public manual includes tenants, users, domains, permissions, and impersonation, and Libraesva's release notes describe parent and child tenant behavior and MSP features. The public material reviewed here does not advertise native ConnectWise, HaloPSA, or Autotask integrations, so confirm the exact service-provider workflow and API coverage before buying.
What should a team compare before switching from LetsDMARC to Palisade?
Compare reporting views, hosted SPF and DNS ownership, BIMI and alert requirements, tenant permissions, API actions, PSA workflow, the published or quoted pricing unit, and who performs sender investigation. Run both reporting destinations during the overlap, keep DNS approval with the responsible operator, and move policy only after the approved changes are verified.
Switching from LetsDMARC takes three steps
- 1
Keep LetsDMARC receiving reports during the overlap
Add Palisade as an additional DMARC reporting destination while LetsDMARC continues receiving reports. Compare source coverage and alignment evidence before changing the operating workflow.
- 2
Import domains and review the agent's plan
Bring your domains into Palisade, let the agent investigate senders and draft SPF or DKIM fixes, then have the responsible operator review each proposed change before it ships.
- 3
Move approved DNS work on your schedule
Use Palisade's approved DNS deployment or hosted-record path for the domains you are ready to move, keep the existing LetsDMARC workflow available during the transition, and retire it only after the new reports and records are confirmed.
Our onboarding team handles the technical transition with you.
Competitor information on this page was last reviewed against public sources on 2026-08-26. Spotted something out of date? Tell us and we'll fix it.