Splunk TA-DMARC add-on alternative
Splunk TA-DMARC add-on vs Palisade in 2026
Splunk TA-DMARC is an archived MIT add-on that ingests DMARC aggregate reports into a Splunk deployment. Palisade is agent-first: its agent investigates senders, drafts SPF and DKIM fixes, and proposes each policy step toward p=reject for your approval.
Our verdict: Pick Splunk TA-DMARC if you want an open-source, self-hosted input layer that brings DMARC XML reports into Splunk and maps them to the Authentication data model, and you have a Splunk operator who owns the surrounding workflow. Pick Palisade if you want a hosted DMARC service whose agent investigates senders, drafts authentication changes, and carries domains toward p=reject with your approval at each step.
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
Free for one domain, up to 1,000 emails a month. Paid plans are sized by email volume, with a 15-day trial and no credit card.
Which one is right for you?
Best for Teams already operating Splunk and owning the workflow
Best for MSPs and IT teams responsible for multiple domains
- You already operate Splunk Enterprise or Splunk Cloud and want DMARC aggregate events inside the same search and security environment.
- You want to own the mailbox or directory input, Splunk deployment, storage, dashboards, and downstream searches yourself.
- You can accept an archived project with no vendor support commitment, no published DMARC add-on price, and no advertised MSP control plane.
- You want an AI agent to investigate every sender, draft SPF and DKIM fixes, and propose each policy step toward p=reject instead of stopping at report ingestion.
- You want hosted SPF, DKIM, DMARC, BIMI, and MTA-STS records on redundant managed DNS, with Smart DNS Deployment through your DNS provider.
- You manage internal or client domains and want multi-tenant operations, native ConnectWise, HaloPSA, or Autotask integrations, and pricing that matches your domain portfolio.
Free for one domain, up to 1,000 emails a month. Paid plans are sized by email volume, with a 15-day trial and no credit card.
Where the day-to-day work actually differs
| Feature | Splunk TA-DMARC add-on | Palisade |
|---|---|---|
| Report collection and analysis | ||
| DMARC aggregate report ingestion and monitoringWhether DMARC aggregate reports are collected and available for review.The repository describes TA-dmarc as an add-on for ingesting DMARC XML aggregate reports into Splunk, while the Splunkbase listing repeats the IMAP, POP3, and local-directory collection model (checked 2026-08-26). Source (2026-08-26) Source 2 (2026-08-26) | IMAP, POP3, or folder | Agent analyzes reports |
| Source, receiver, policy, SPF, DKIM, and disposition fieldsWhether reports retain the fields needed to diagnose authentication results.The README documents fields mapped from DMARC XML, including source IP, destination, header-from domain, published policy, disposition, SPF result, and DKIM result (checked 2026-08-26). Source (2026-08-26) | Mapped XML fields | Agent analyzes results |
| IMAP, POP3, and local-directory inputsWhether reports can be collected through mail protocols or local folders.TA-dmarc documents IMAP inputs with basic or OAuth2 authentication, POP inputs with basic authentication, and directory inputs for offline environments (checked 2026-08-26). Source (2026-08-26) | Three input methods | Not offered |
| Structured JSON output with legacy key=value compatibilityWhether parsed reports support structured JSON and a legacy output format.The README says JSON is the default output for structured aggregate reports and that key=value remains available for compatibility, with some newer validation enhancements unavailable in that format (checked 2026-08-26). Source (2026-08-26) | JSON with legacy output | Not offered |
| Splunk ecosystem | ||
| CIM Authentication mapping for Splunk Enterprise Security searchesWhether DMARC events map to Splunk's Authentication data model.TA-dmarc maps relevant aggregate-report fields to the Splunk CIM Authentication data model and documents use in Splunk Enterprise Security dashboards and tstats searches (checked 2026-08-26). Source (2026-08-26) Source 2 (2026-08-26) | CIM Authentication mapping | Not offered |
| Enforcement and DNS | ||
| AI agent that investigates senders, drafts authentication fixes, and proposes policy steps toward p=rejectWhether sender fixes and DMARC policy steps are prepared for review.TA-dmarc describes data collection, parsing, enrichment, and CIM mapping, but does not advertise an AI enforcement agent or a workflow that drafts SPF/DKIM changes (checked 2026-08-26). Source (2026-08-26) | Not advertised | Agent drafts and proposes |
| Hosted DMARC, SPF, DKIM, BIMI, and MTA-STS recordsWhether authentication and transport records are hosted for the domain.The add-on documentation describes collecting reports from a mailbox or directory and sending events into Splunk; hosted authentication or transport records are not advertised (checked 2026-08-26). Source (2026-08-26) Source 2 (2026-08-26) | Not advertised | Hosted managed DNS |
| SPF flattening and lookup-limit managementWhether SPF includes are consolidated to stay within DNS lookup limits.The public TA-dmarc materials describe SPF result fields and DKIM validation, but do not advertise SPF flattening or lookup-limit management (checked 2026-08-26). Source (2026-08-26) | Not advertised | Hosted SPF flattening |
| MSP operations | ||
| Native ConnectWise, HaloPSA, and Autotask integrationsWhether tickets and client work can connect to PSA systems.The public project documents Splunk deployment roles, mailbox and directory inputs, and CIM mapping, but does not advertise ConnectWise, HaloPSA, or Autotask integrations (checked 2026-08-26). Source (2026-08-26) Source 2 (2026-08-26) | Not advertised | Native PSA integrations |
| Portfolio-oriented multi-tenant client management and white-label reportingWhether one team can manage separate client domains and branded reports.The public materials describe one Splunk add-on and its input and search-time roles, but do not advertise client workspaces, tenant isolation, white-label reporting, or an MSP operating workflow (checked 2026-08-26). Source (2026-08-26) Source 2 (2026-08-26) | Not advertised | Client workspaces and reports |
| Service model and lifecycle | ||
| Vendor-managed report retention and hosted storageWhether the vendor stores DMARC reports for a defined retention period.The README describes Splunk KVstore checkpointing and event indexing but does not publish a vendor-managed report-retention period or hosted storage tier (checked 2026-08-26). Source (2026-08-26) | Not advertised | 14 days or unlimited |
| Published commercial subscription, support plan, or SLA for the add-onWhether a commercial plan states its support terms and service commitment.Splunkbase lists the add-on under an MIT license and marks support as Not Supported; the maintainer's README says the open-source project provides no support and does not advertise a subscription, paid support plan, or SLA (checked 2026-08-26). Source (2026-08-26) Source 2 (2026-08-26) | No published plan | Published plans and SLA |
| AI and automation access | ||
| Documented REST API for Splunk search dataWhether a customer can build against a published REST API to query Splunk data.Splunk documents REST endpoints for search jobs and results, including API-driven export. This is a Splunk platform API rather than a TA-DMARC-specific API. For Splunk Cloud, REST access must be enabled and is unavailable on free trial accounts (checked 2026-08-27). Source (2026-08-27) Source 2 (2026-08-27) | REST API documented | REST API published |
| MCP server for connecting AI assistants to Splunk dataWhether an AI assistant can reach the platform data that the add-on feeds into.Splunk publishes a generally available MCP Server that connects AI assistants, agents, and other intelligent systems to Splunk data. Its setup requires REST API access and token authentication, and the server is installed on a Splunk Search Head or Search Head Cluster (checked 2026-08-27). Source (2026-08-27) Source 2 (2026-08-27) | MCP server published | MCP server published |
| Advertised AI assistance for searching and investigating Splunk dataWhether the vendor advertises AI work inside the platform that hosts the add-on.Splunk advertises its AI Assistant as a generative app that finds data in a tenant, writes and optimizes SPL, validates results by running searches, and troubleshoots ingestion and configuration issues. The documentation does not advertise it as a TA-DMARC-specific sender or DNS-remediation workflow (checked 2026-08-27). Source (2026-08-27) | AI Assistant published | Agent drafts fixes |
| Search-data export and forwarding outside dashboardsWhether data can leave the platform through documented programmatic or scheduled methods.Splunk documents data forwarding plus CLI, SDK, and REST export methods. Its export guidance says SDK and REST options suit higher-volume scheduled exports and lists raw events, CSV, JSON, and XML as output formats (checked 2026-08-27). Source (2026-08-27) Source 2 (2026-08-27) | API and SDK exports | REST API published |
Report ingestion vs enforcement
TA-DMARC's report pipeline stops at Splunk events
TA-DMARC is a data-ingestion layer for a Splunk deployment. Its README describes a modular input that reads DMARC XML aggregate reports, parses the structured data, adds fields such as DNS resolution and XSD validation results, and sends the resulting events into Splunk. The project says its design leaves the data intact and leaves aggregation and visualization to other Splunk apps. That is real parity for collecting and searching DMARC evidence. Source (2026-08-26) Source 2 (2026-08-26)
The next operational step remains outside the add-on. The public materials do not advertise sender investigation, SPF or DKIM record drafting, or a policy workflow that prepares a domain for p=reject. Palisade starts with the same report evidence and carries that work further: its agent investigates every sender, drafts authentication fixes, and proposes each policy step, with approval required before anything ships. Source (2026-08-26)
- Not advertised
- Not advertised
- Not advertised
- Agent drafts and proposes
- Hosted managed DNS
- Hosted SPF flattening
- 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.
Input flexibility vs operator ownership
IMAP, POP3, or a folder: three inputs, one operator-owned mailbox
The add-on gives a Splunk operator several ways to bring reports in. IMAP supports basic or OAuth2 authentication, POP3 supports basic authentication, and a directory input handles offline environments where another process deposits the report attachments. The configuration also covers polling intervals, Splunk indexes, mailbox folders, XML validation, DKIM validation, IP resolution, and JSON or key=value output. TA-DMARC does not modify, move, or delete messages on the IMAP server. It records processed messages in Splunk KVstore instead. Source (2026-08-26)
That flexibility suits a team that already has mailbox administration and Splunk ownership in place. It also means the team owns the credentials, network path, polling health, index capacity, checkpoint state, and response when ingestion stops. Palisade shifts the work to a hosted domain workflow, where the agent can use the report evidence to identify legitimate senders and prepare the authentication changes that an operator reviews. Source (2026-08-26)
- IMAP, POP3, or folder
- Mapped XML fields
- Three input methods
- Agent analyzes reports
- Agent analyzes results
- Not offered
Security context vs DNS remediation
CIM mapping gives Splunk Enterprise Security context, not DNS remediation
TA-DMARC's strongest Splunk-specific feature is normalization. Its README maps aggregate-report fields into the CIM Authentication data model, including the source IP, destination domain, header-from domain, policy disposition, SPF and DKIM results, and a DMARC application value. The project says that mapping lets the results appear in relevant Splunk Enterprise Security dashboards and supports accelerated tstats searches. If your SOC already works in Splunk, keeping the DMARC evidence in that search environment is a genuine reason to consider the add-on. Source (2026-08-26) Source 2 (2026-08-26)
CIM context is not the same as an authentication control plane. The documentation describes event fields, searches, and dashboards, but does not advertise hosted DNS, SPF flattening, PSA ticket flow, or client-domain management. Palisade evaluates the same sender and alignment evidence, then drafts the next SPF or DKIM change and proposes the next policy step. The person still approves the change, but the agent carries more of the investigation and preparation than a Splunk dashboard does. Source (2026-08-26)
- CIM Authentication mapping
- Not offered
- 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.
Self-managed code vs vendor support
An archived MIT add-on changes the maintenance calculation
The license and lifecycle are central to this choice. Splunkbase lists TA-DMARC as MIT-licensed, identifies version 4.1.1 as the latest version dated October 21, 2022, and marks the app archived with support listed as Not Supported. The maintainer's README also calls it an open-source project without warranty and says no support is provided, while pointing users to the public repository and issue tracker. Those facts make the add-on inspectable and usable as code, but they do not create a current vendor support contract. Source (2026-08-26) Source 2 (2026-08-26)
For a single Splunk team with the right engineering skills, that tradeoff may be acceptable. An MSP operating many customer domains should count the work that sits around it: separate report routing, domain inventory, client reporting, ticket creation, DNS changes, upgrades, and incident ownership. Palisade packages that operating layer as a hosted service, with portfolio-based MSP pricing and an agent that prepares reviewed authentication work. The practical decision is whether your team wants to extend Splunk around the add-on or use a purpose-built service for domain enforcement operations. Source (2026-08-26) Source 2 (2026-08-26)
- Not advertised
- No published plan
- 14 days or unlimited
- Published plans and SLA
Dashboard access vs programmatic access
TA-DMARC can use Splunk's REST API and MCP Server, not a TA-DMARC-specific control plane
TA-DMARC is an archived Splunk add-on that ingests DMARC aggregate reports into the Splunk platform, so its current programmatic-access story is at the platform layer rather than through a separate add-on API. Splunk documents REST endpoints for running searches and exporting their results. On Splunk Cloud, a customer must enable REST access and free trial accounts cannot use it. Splunk also publishes a generally available MCP Server that lets AI assistants and agents access Splunk data resources and run searches. Its documented setup requires REST API access and token authentication. Source (2026-08-27) Source 2 (2026-08-27) Source 3 (2026-08-27) Source 4 (2026-08-27) Source 5 (2026-08-27)
Splunk also advertises an AI Assistant that can find tenant data, write and optimize SPL, validate results by running searches, and troubleshoot ingestion and configuration issues. Palisade publishes an MCP server and a REST API too. 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
- REST API documented
- MCP server published
- AI Assistant published
- REST API published
- MCP server published
- Agent drafts fixes
Splunk TA-DMARC pricing: the add-on is free under MIT, but Splunk is still your platform
Splunk TA-DMARC is published as an archived MIT add-on, not as a hosted DMARC subscription. The Splunkbase listing identifies the license and download path, while the maintainer's README explains the self-hosted installation and configuration. Neither publishes a TA-DMARC plan, trial, per-domain fee, or message-volume rate. Splunk's separate platform pricing page describes quote-based Splunk Cloud and Enterprise models, but it does not publish a TA-DMARC-specific price.
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
MIT covers the self-hosted add-on only
2 set-up domains, up to 100K emails a month
MIT covers the self-hosted add-on only
10 set-up domains, up to 1M emails a month
MIT covers the self-hosted add-on only
20 set-up domains, up to 2.5M emails a month
MIT covers the self-hosted add-on only
Client domains under management, any volume
MIT covers the self-hosted add-on only
Palisade’s figures are derived from its published tiers. Splunk TA-DMARC add-on figures read from their pricing page on 2026-08-28. Plans and prices may have changed since.
How Splunk TA-DMARC add-on prices
- Splunkbase lists the add-on as MIT-licensed, archived, and Not Supported. It does not publish a paid add-on tier, support rate, trial, domain allowance, message allowance, or SLA (checked 2026-08-26).
- Splunk's general pricing page says Splunk Cloud Platform and Splunk Enterprise use activity-based, ingest, or workload pricing and directs buyers to request a quote. Those are Splunk platform terms, not a published price for TA-DMARC itself (checked 2026-08-26).
- The add-on's license line is not the same as a $0 operating cost. The team still supplies a Splunk deployment, a report mailbox or directory, storage, credentials, monitoring, backups, and the people who maintain the input and act on findings.
- The Splunkbase listing shows version 4.1.1 dated October 21, 2022 and marks the app archived. That is a published lifecycle signal, not proof that a particular deployment cannot run (checked 2026-08-26).
How Palisade prices
- Palisade publishes a Free plan for one domain and up to 1,000 emails/month, plus flat monthly IT-team plans sized by email volume from $19/month. Paid IT tiers cap set-up domains at 2, 3, 6, 10, or 20 by tier; adding domains is free and unlimited.
- Palisade's MSP model is quoted per client domain, with a rate that improves as your portfolio grows. Client email volume is not metered, and your own MSP domain is included as a free Not-For-Resale license.
- Palisade is hosted, so the service covers the report and DNS surface instead of asking your team to assemble Splunk inputs, indexes, searches, dashboards, and maintenance. Its agent investigates senders, drafts fixes, and proposes policy steps while your team approves each change.
- Palisade offers a 15-day full-product trial without a credit card. The free plan keeps 14 days of report history, while paid plans have unlimited retention.
Splunk TA-DMARC add-on pricing read from their public pricing page on 2026-08-26.Plans and prices may have changed since.
1 domain free up to 1,000 emails/month
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.
Splunk TA-DMARC is an archived MIT add-on for Splunk deployments that ingests DMARC XML aggregate reports, parses and enriches their data, and sends resulting events to Splunk. It serves teams already operating Splunk Enterprise or Splunk Cloud that want DMARC evidence in their existing search and security environment rather than a separate hosted DMARC subscription.
The add-on is built for operators who can configure the report mailbox or directory, Splunk roles, indexes, searches, dashboards, storage, and maintenance. It supports IMAP, POP3, and directory inputs, maps aggregate-report fields to the CIM Authentication data model, and leaves aggregation and visualization to other Splunk apps.
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.
- Collects DMARC aggregate reports through IMAP, POP3, or a local folder
- Maps source, receiver, policy, SPF, DKIM, and disposition fields from DMARC XML
- Provides structured JSON output with legacy key=value compatibility
- Maps events to the CIM Authentication data model for Splunk Enterprise Security searches
- Runs on Splunk, which publishes a REST API for search data
- 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 AI agent that investigates senders, drafts authentication fixes, and proposes policy steps toward p=reject
- Does not advertise hosted DMARC, SPF, DKIM, BIMI, or MTA-STS records
- Does not advertise SPF flattening or lookup-limit management
- Does not advertise native ConnectWise, HaloPSA, or Autotask integrations
- Does not advertise portfolio-oriented multi-tenant client management or white-label reporting
- 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
- License fee
- $0 published under MIT
- Hosting model
- Self-hosted
- Support status
- Not Supported
- Latest version
- 4.1.1 (October 21, 2022)
- Domain allowance
- Not published
- 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.
- Splunkbase TA-dmarc add-on listing, license, version, and support status
Checked 2026-08-26
- TA-dmarc maintainer repository
Checked 2026-08-26
- TA-dmarc README and configuration documentation
Checked 2026-08-26
- Splunk public pricing page
Checked 2026-08-26
- Splunk supported add-ons and CIM documentation
Checked 2026-08-26
- TA-dmarc add-on listing, AI and automation access review
Checked 2026-08-27
- Splunk REST API export documentation
Checked 2026-08-27
- Splunk Cloud REST API access requirements
Checked 2026-08-27
- Splunk MCP Server documentation
Checked 2026-08-27
- Splunk MCP Server setup documentation
Checked 2026-08-27
- Splunk AI Assistant documentation
Checked 2026-08-27
- Splunk search-result export methods
Checked 2026-08-27
- Splunk REST API search endpoint reference
Checked 2026-08-27
- Splunk MCP Server app listing
Checked 2026-08-27
- Splunk AI Assistant app listing
Checked 2026-08-27
- Splunk AI Assistant installation documentation
Checked 2026-08-27
- Splunk Enterprise AI capabilities
Checked 2026-08-27
- Splunk AI Assistant in Security product page
Checked 2026-08-27
- Splunk Enterprise Security AI Assistant overview
Checked 2026-08-27
Palisade vs Splunk TA-DMARC add-on: FAQ
What is Splunk TA-DMARC?
Splunk TA-DMARC is an add-on for ingesting DMARC XML aggregate reports into Splunk. The project documents IMAP, POP3, and local-directory inputs, report parsing, enrichment, JSON output, and mapping to the Splunk CIM Authentication data model. Splunkbase currently lists it as an archived MIT add-on.
Does Splunk TA-DMARC enforce DMARC or change DNS?
No. Its public documentation describes collecting and parsing reports, adding fields, and sending events into Splunk. It does not advertise hosted DNS records, an AI enforcement agent, or a workflow that drafts SPF and DKIM changes. Those actions remain part of your own operational process.
How much does Splunk TA-DMARC cost?
The add-on is listed under the MIT license, and no TA-DMARC subscription or add-on price is published. Splunk's platform still has its own commercial pricing, which Splunk describes through quote-based Cloud and Enterprise models. Budget separately for the Splunk platform, storage, report mailbox, maintenance, and operator time.
Does Splunk TA-DMARC support Splunk Enterprise Security?
Yes, its README says DMARC aggregate fields are mapped to the Splunk CIM Authentication data model so the results can be used in relevant Splunk Enterprise Security dashboards and tstats searches. Confirm the add-on and CIM versions against your deployment because the public add-on is archived.
Can an MSP use Splunk TA-DMARC for multiple clients?
The public materials document Splunk deployment roles, mailbox and directory inputs, report fields, and CIM mapping. They do not advertise client workspaces, tenant isolation, white-label reporting, PSA integrations, or per-client billing. An MSP could build those layers around Splunk, but they are not published as part of this add-on.
Is Splunk TA-DMARC still supported?
Splunkbase marks the app archived and lists support as Not Supported. It shows version 4.1.1 dated October 21, 2022, while the maintainer's README says the open-source project provides no support. A fork or internal maintenance program could have a different status, so verify the exact code and deployment you plan to operate.
Can I run Splunk TA-DMARC and Palisade at the same time?
Yes. DMARC reporting supports multiple reporting destinations, so you can compare both workflows during an overlap period. Keep DNS policy changes coordinated, compare sender and alignment findings, and retire the old input only after you have validated the new process for the domains you intend to manage.
Switching from Splunk TA-DMARC add-on takes three steps
- 1
Inventory the Splunk inputs and checkpoints
List the report mailbox or directory inputs, Splunk indexes, CIM dependencies, and domains currently represented before you change the reporting destination.
- 2
Route aggregate reports to both workflows
Use the same DMARC reporting window to compare the add-on's Splunk events with Palisade's domain and sender findings before retiring the existing input.
- 3
Move approved DNS work deliberately
Keep the responsible DNS owner in the approval loop, then validate SPF, DKIM, and DMARC results in delivered mail and aggregate reports before decommissioning the old Splunk workflow.
1 domain free up to 1,000 emails/month
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.
Still deciding between Splunk TA-DMARC add-on 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.”