The DMARC protocol (Domain-based Message Authentication, Reporting, and Conformance), first published in 2015 as RFC 7489, is changing.

The IETF (Internet Engineering Task Force) has been working on an updated specification, internally referred to as DMARCbis, for a few years and the process was completed in May 2026. The updated specification is now official with the publishing of RFC 9989, RFC 9990, and RFC 9991. You can lean more about the details in our dedicated post.

DMARCwise is gradually adding support for DMARCbis. When you see a “DMARCbis” badge in the user interface, it means that that particular attribute or concept was introduced or changed by DMARCbis.

The current support status of DMARCbis in DMARCwise is:

  • ✅ DMARCbis-specific data contained in DMARC reports is correctly processed and shown in the dashboard for reports received on or after 28 November 2025.
  • ✅ DMARCbis-specific tags contained in DMARC records are recognized, extracted, validated and shown in the dashboard as of 29 November 2025, even for previously discovered records.
  • ❌ Hosted DMARC does not allow configuring DMARCbis-specific tags.
  • ❌ The diagnostics feature does not use the new tree walk algorithm for DMARC policy discovery and instead relies on the “old” PSL-based method.

Learn more about DMARCbis in our detailed article: