DMARC Report recognised Microsoft 365 and Google Workspace in the first aggregate cycles, then grouped SendGrid and Mailchimp once DKIM results and return-path patterns stabilised. The parked domain was easy to watch because non-compliant traffic stayed isolated, and the unauthorized spoof sample stood out in the failure view. The unknown sender had enough IP, domain, and vendor evidence for investigation, but assigning an internal owner and writing the fix note still took manual work. The SPF pass with visible From mismatch was clearly shown as a domain-match problem, which helped us avoid treating it as a normal SPF pass.

EmailAuth.io read like a broader authentication and investigation program, especially around DMARC, SPF, DKIM, BIMI, SOAR, API, STIX/TAXII, and managed-service reporting. In our test notes, Microsoft 365 and Google Workspace were straightforward to classify, while SendGrid and Mailchimp needed more deliberate service mapping before the owners were obvious. The unknown sender workflow benefited from DNS, Whois, and spam listing context, and the DKIM pass on a subdomain was easier to treat as an investigation case than a simple pass or fail. The tradeoff was packaging clarity: we could not tell which feature boundaries were self-service, managed-service, or enterprise-only before quote scoping.

In DMARC Report, we added the corporate domain, marketing subdomain, and parked domain with direct DNS instructions, then saw reports populate without a support handoff. The unknown sender was findable through the non-compliant sender view, and the spoof sample was easy to separate from Microsoft 365 and Google Workspace traffic. The forwarded mail case was accurate at the data level, but explaining why SPF failed after forwarding still required a technical note outside the product.

EmailAuth.io looked better for buyers who expect onboarding support, dashboard training, and periodic review instead of a purely self-service setup. The unknown sender had useful investigation context, including DNS and reputation signals, which made classification easier once we knew where to look. The forwarded SPF failure was easier to discuss as part of a managed review, but the self-service path for a new operator was less obvious than in DMARC Report.

DMARC Report's support model fit a self-service team with a technical owner. DNS handoff was concrete enough to pass to an administrator, and public plan notes made it clear that email support, alerts, advanced support, and dedicated engineering help sit on higher tiers. For our Microsoft 365, Google Workspace, SendGrid, Mailchimp, and support desk setup, we could document each DNS step ourselves, but enterprise onboarding depth depended on the chosen tier.

EmailAuth.io's managed-service material matched the support-heavy scenario better. It described onboarding, dashboard training, alerts, proactive recommendations, periodic DMARC meetings, analysed reports, and 24x7 phone and email support. That is useful when DNS ownership is split across IT, marketing, and support operations, but it also means the buyer needs a scoped quote to know escalation paths, response expectations, and which authentication fixes are included.

DMARC Report fit the SMB and agency side of our test best. Group and permission controls helped keep the corporate domain, marketing subdomain, and parked domain understandable, and the public MSP discount made multi-client use easier to budget. Recurring reports and exports were useful for client updates, but the handoff notes still had to be written by the operator when the unknown sender or forwarded SPF failure needed explanation.

EmailAuth.io fit enterprise and security-led buying better than small self-service work. The managed-service path, periodic reports, and on-premise option matched environments where IT, security, and compliance teams want a formal review rhythm. For MSPs, the open question is account separation: we did not see enough public detail to treat client grouping, recurring reports, and delegated handoff as a clear self-service package.