Palisade vs.
Netcraft Fraud Detection in 2026

Palisade separated Microsoft 365 and Google Workspace quickly, grouped SendGrid and Mailchimp under the marketing subdomain, and flagged the support desk as an approved but lower-volume sender. The unknown sender landed in a review queue with enough IP, header-domain, and pass or fail detail for us to label it without exporting raw XML. In the forwarded-mail case, the SPF failure was explained as expected forwarding behavior, with DKIM carrying authentication where the visible domain still matched.

Netcraft's feature set leaned toward fraud detection: the unauthorized spoof sample was enriched with hosting, URL, and brand-abuse context. It accepted DMARC reporting and showed Microsoft 365 and Google Workspace as known corporate sources, but SendGrid, Mailchimp, and support desk ownership needed more manual annotation. The SPF pass with visible-from mismatch was caught as suspicious brand use, but the screen pushed us toward investigation and countermeasure workflow rather than DMARC policy steps.

Palisade let us add the corporate domain, marketing subdomain, and parked domain with fewer setup decisions. The SPF pass with matching visible domain and DKIM pass on the marketing subdomain quickly moved into approved-source status, while the unknown sender stayed visible until we classified it. The forwarded-mail SPF failure had enough context for us to explain why it was not the same risk as the spoof sample.

Netcraft's experience felt more like opening an investigation workspace than tuning DMARC. Adding the three domains was workable, but we spent more time mapping the DMARC sources to business owners, especially the support desk sender and the unknown sender. The forwarded-mail case was visible, but the explanation was thinner than Palisade's DMARC-specific drilldown.

Palisade's support path was practical during DNS setup. The DMARC rua and policy records for the corporate domain and parked domain had copy-ready values, and the handoff notes made it clear when the DNS owner needed to publish a record versus when Palisade-managed DNS could be used on higher tiers. Escalation felt tied to DMARC engineering rather than broader abuse response.

Netcraft's support model felt enterprise and analyst-led. For the unauthorized spoof sample, escalation language was stronger and the handoff could include countermeasure steps, but routine DMARC DNS setup for the marketing subdomain needed more back-and-forth before a non-specialist could act. Onboarding clarity depends on the scoped service.

Palisade grouped the primary corporate domain, marketing subdomain, and parked domain in a way that would work for an internal security team or MSP. The MSP-facing motion had domain grouping, white label reporting, client portal access, permissions, and per-domain pricing, so recurring client handoff would be practical. The tradeoff is that the strongest fit remains DMARC operations, not broad fraud takedown.

Netcraft fit an enterprise fraud team better than a small business or MSP. Covered-brand scoping, API access, CSV exports, and progress reporting worked for enterprise investigation, but account separation and recurring client reports were not as natural in our test. SMB buyers would face more procurement and onboarding work than the DMARC reporting use case needs.