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

推荐订阅源

The GitHub Blog
The GitHub Blog
雷峰网
雷峰网
小众软件
小众软件
博客园 - 【当耐特】
J
Java Code Geeks
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Hugging Face - Blog
Hugging Face - Blog
腾讯CDC
Engineering at Meta
Engineering at Meta
aimingoo的专栏
aimingoo的专栏
A
About on SuperTechFans
H
Help Net Security
博客园_首页
P
Proofpoint News Feed
GbyAI
GbyAI
大猫的无限游戏
大猫的无限游戏
N
Netflix TechBlog - Medium
爱范儿
爱范儿
MyScale Blog
MyScale Blog
Blog — PlanetScale
Blog — PlanetScale
The Cloudflare Blog
MongoDB | Blog
MongoDB | Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
Google DeepMind News
Google DeepMind News

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