惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园_首页
Microsoft Azure Blog
Microsoft Azure Blog
aimingoo的专栏
aimingoo的专栏
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
阮一峰的网络日志
阮一峰的网络日志
Martin Fowler
Martin Fowler
B
Blog
The GitHub Blog
The GitHub Blog
T
Tailwind CSS Blog
Stack Overflow Blog
Stack Overflow Blog
L
LangChain Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
D
DataBreaches.Net
月光博客
月光博客
人人都是产品经理
人人都是产品经理
IT之家
IT之家
GbyAI
GbyAI
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
WordPress大学
WordPress大学
博客园 - Franky
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
The Cloudflare Blog
C
Check Point Blog
罗磊的独立博客

dmarc.org

Updated DMARC Statistics Published – dmarc.org Summary of Changes in DMARCbis – dmarc.org DMARC.org at 8th JPAAWG General Meeting – dmarc.org DMARC.org at 7th JPAAWG General Meeting – dmarc.org New Authentication Protocol: DKIM2 – dmarc.org DMARC.org at Sixth JPAAWG General Meeting – dmarc.org M3AAWG Calls for Coalition to Support Public Suffix List – dmarc.org Microsoft Allows 365 Admins To Accept ARC Forwarders – dmarc.org DMARC.org at Fifth JPAAWG General Meeting – dmarc.org Most DKIM Keys Seen in 2021 Were 2K RSA – dmarc.org
IETF Publishes Updated DMARC Specification – dmarc.org
Steve Jones · 2026-05-28 · via dmarc.org

On May 20th, 2026 the IETF’s RFC Editor published three documents that update the DMARC protocol, making the changes and enhancements previously referred to as “DMARCbis” official, and moving the updated DMARC protocol to the IETF’s Standards Track. This represents many years of work by the IETF’s DMARC Working Group, as development began in earnest shortly after the ARC protocol was finalized in 2019.

The new documents are:

Highlights of the changes include:

  • Public Suffix List replaced by DNS Tree Walk and Public Suffix Domains (PSD)
  • Several tags deprecated: pct=, rf=, ri=
  • np= tag added for non-existent subdomain policy
  • psd= tag brought in from RFC 9091 (obsoleted)
  • Report size limit notation removed from rua=
  • DMARC SPF only uses the MAIL FROM: address, no fallback to the HELO identifier
  • Much more guidance about PII/NPI risks in reporting