DMARC is now an IETF Proposed Standard: what's new in RFCs 9989–9991
The DMARC protocol has been updated and is now an IETF Proposed Standard as of May 2026. This update includes significant changes aimed at improving email security and addressing limitations of the original protocol. The new specification is published as three separate RFCs, which provide clearer guidelines and better support for domain owners.
- ▪DMARC is now published as RFC 9989, RFC 9990, and RFC 9991, replacing the previous RFC 7489 from 2015.
- ▪The updated specification includes a restructuring for better readability and practical guidance.
- ▪New tags have been added to the DMARC policy record, while some existing tags have been removed.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DMARCwise |
| Canonical URL | https://dmarcwise.io/blog/new-dmarc-2026 |
| Publication time | Wed, 20 May 2026 10:49:11 +0000 |
| Retrieval time | 2026-05-20T11:05:02.097Z |
| Last seen | 2026-05-20T11:05:02.097Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | vNHFRjYY0afX |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
← Blog Last updated May 20, 2026 DMARC is now an IETF Proposed Standard: what's new in RFCs 9989–9991 Matteo 18 min. read The DMARC protocol (Domain-based Message Authentication, Reporting, and Conformance) was updated in May 2026 and is now an IETF Proposed Standard. It is published as RFC 9989, RFC 9990, RFC 9991, replacing the Informational RFC 7489 from 2015. While the new DMARC isn’t a revolution, it contains some important changes. This article aims to be a comprehensive list of the most relevant changes in the new RFCs. Introduction DMARC is an email security protocol that helps protect your domain from being impersonated by scammers and phishers, an attack known as spoofing. DMARC builds upon two other foundational protocols of email, SPF and DKIM.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DMARCwise.
Discussion
0 commentsMore from DMARCwise
