Where is DMARC heading in 2026 and beyond?
The future of DMARC is enforcement by default. As of November 2026, DMARC is a Standards Track protocol (RFC 9989, 9990 and 9991, May 2026), Gmail, Yahoo and Outlook.com reject or filter unauthenticated bulk mail, and governments expect p=reject. The open questions are about adoption speed and adjacent standards, not about DMARC itself.
This article is a dated status check, written on 15 November 2026. It separates three things that are often blurred: what is already true (verifiable on a primary source today), what is likely (our assessment, labelled as such) and what is unknown. DMARC (Domain-based Message Authentication, Reporting and Conformance) sits on top of SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail), so the DMARC guide is the place to start if those terms are new.
Key takeaways
- Already true: DMARCbis is published. RFC 9989 removed the
pct,rfandritags, addednp,psdandt, and replaced the Public Suffix List with a DNS Tree Walk. - Already true: Gmail (from February 2024), Yahoo (from February 2024) and Outlook.com (from May 2025) require SPF, DKIM and at least
p=nonefrom bulk or high-volume senders. Outlook.com rejects non-compliant mail with550 5.7.515. - Already true: BIMI is still an individual Internet-Draft, and ARC (RFC 8617) is still Experimental.
- Likely: more pressure toward
p=quarantineandp=reject, not new protocols replacing DMARC. - Unknown: when large receivers will implement the DNS Tree Walk and the
ttag, and whether any provider will require an enforcing policy rather thanp=none.
What is already true in November 2026?
Seven developments are settled facts with primary sources behind them. The table lists each one with its date and status, so you can tell a published rule from a forecast. Everything in this section was checked on the source linked in the following subsections in November 2026.
| Development | Date | Status today | Primary source |
|---|---|---|---|
| DMARCbis (RFC 9989, 9990, 9991) | May 2026 | Standards Track, obsoletes RFC 7489 | rfc-editor.org |
| Gmail sender guidelines | 1 February 2024 | In force; enforcement increased from November 2025 | support.google.com |
| Yahoo sender requirements | February 2024 | In force | senders.yahooinc.com |
| Outlook.com high-volume sender rules | 5 May 2025 | In force; non-compliant mail rejected with 5.7.515 | techcommunity.microsoft.com |
| BIMI | Draft revision 15, 31 October 2026 | Individual Internet-Draft, not an RFC | datatracker.ietf.org |
| ARC (RFC 8617) | July 2019 | Experimental | rfc-editor.org |
| MTA-STS (RFC 8461) and TLS-RPT (RFC 8460) | September 2018 | Standards Track | rfc-editor.org |
What did DMARCbis change?
DMARCbis is the update that replaced RFC 7489. RFC 9989 defines the core protocol, RFC 9990 aggregate reporting and RFC 9991 failure reporting. All three were published in May 2026 on the Standards Track; RFC 7489 was Informational.
The headline changes, from RFC 9989 Appendix C:
- Removed:
pct(percentage sampling),rf(failure report format) andri(aggregate report interval). - Added:
np(policy for non-existent subdomains, imported from RFC 9091),psd(public suffix domain flag) andt(testing flag, described as a "replacement for some" of the oldpctfunctionality). - Discovery: "reliance on a PSL has been replaced by a technique called a 'DNS Tree Walk'". The walk makes at most eight DNS queries.
With t=y, a receiver applies the policy one level lower: quarantine is treated like none, and reject like quarantine. Rollout is still p=none, then p=quarantine, then p=reject. We keep the full change table, with section numbers, in DMARCbis explained, and the new tags in np, psd and t explained.
One nuance matters for the future of enforcement. RFC 9989 Section 7.4 says that domains whose users might post to mailing lists "SHOULD NOT publish" p=reject, and that "Mail Receivers MUST NOT reject incoming messages solely on the basis of a 'p=reject' policy". DMARC enforcement after RFC 9989 covers what that means in practice.
What do Gmail, Yahoo and Outlook.com already enforce?
All three large consumer mailbox providers require SPF, DKIM and DMARC from bulk or high-volume senders; Gmail and Outlook.com set the line at more than 5,000 messages a day. The minimum DMARC policy is p=none everywhere, so none of them currently requires enforcement for ordinary sending.
| Provider | In force since | Threshold | DMARC requirement | What happens to non-compliant mail |
|---|---|---|---|---|
| Gmail | 1 February 2024 | More than 5,000 a day to personal Gmail accounts | SPF and DKIM, DMARC at least p=none, From domain aligned with SPF or DKIM |
Spam folder or rejection; "Starting November 2025, Gmail is ramping up its enforcement" with temporary and permanent rejections |
| Yahoo | February 2024 (phased) | Bulk senders | SPF and DKIM, DMARC at least p=none, "DMARC must pass", relaxed alignment acceptable |
Gradual enforcement through the first half of 2024 |
| Outlook.com | 5 May 2025 | More than 5,000 a day to Outlook.com, Hotmail.com and Live.com | SPF and DKIM pass, DMARC at least p=none, aligned with SPF or DKIM |
Rejected: 550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level. |
Sources: Google email sender guidelines and its FAQ, Yahoo sender best practices, and Microsoft's Outlook high-volume sender announcement. Microsoft first planned to send non-compliant mail to Junk, then changed this to rejection in an update on 29 April 2025.
Both Google and Yahoo also require all senders, not only bulk senders, to have SPF or DKIM, valid forward and reverse DNS, and a spam rate below 0.3%. The side-by-side detail is in Google, Yahoo and Microsoft sender requirements compared, and the bounce codes in Microsoft 550 5.7.515.
What do governments already require?
Government baselines already go further than mailbox providers: the UK and US target quarantine or reject, not monitoring. The EU sets outcomes rather than protocols. None of these has been rewritten for DMARCbis yet, which is worth knowing before you quote them.
- UK central government: the GOV.UK guidance on securing government email (last updated 4 March 2024) requires TLS 1.2 or later, MTA-STS, SPF, DKIM and DMARC "starting at p=none rising to p=quarantine or reject", and recommends TLS-RPT.
- UK, all organisations: the NCSC's email security and anti-spoofing guidance sets out a staged plan from
p=noneto rejecting spoofed mail. The NCSC retired Mail Check on 31 March 2026 and recommends commercial tooling instead. Our summary is in what the NCSC recommends for DMARC. - US federal: CISA's Binding Operational Directive (BOD) 18-01, issued in October 2017, required federal executive agencies to reach
p=rejectwithin one year. See DMARC for government domains. - EU: the NIS2 Directive (EU) 2022/2555 requires in-scope entities to take appropriate cybersecurity risk-management measures. It does not name DMARC. How that plays out in practice is in NIS2 and DMARC.
Where do BIMI and its certificates stand?
BIMI (Brand Indicators for Message Identification) is deployed by several large mailbox providers but is still not an internet standard. The IETF Datatracker lists draft revision 15 (31 October 2026) as an "Active Internet-Draft (individual)" with no formal standing. Provider rules, not an RFC, decide when a logo appears.
What each provider documents today:
- Gmail accepts a VMC (Verified Mark Certificate, which requires a registered trademark) or a CMC (Common Mark Certificate, which does not). It shows a checkmark for VMC senders and requires
p=quarantineorp=reject(Google Workspace BIMI setup). The BIMI Group announced CMCs on 26 September 2024. - Yahoo says it does "not require VMCs" for logos to appear, but needs a DMARC policy of quarantine or reject (Yahoo BIMI).
- Apple Mail (macOS Ventura 13, iOS 16 and later) shows logos only when the mail provider has verified a BIMI evidence document, "for example, a VMC" (Apple BIMI support).
The common thread is DMARC at enforcement. That makes BIMI a reason to finish a DMARC project, not a separate project. See the BIMI guide and what is a BIMI record.
What is the status of ARC?
ARC (Authenticated Received Chain) is still an Experimental protocol, defined in RFC 8617 in July 2019. It lets intermediaries such as mailing lists and forwarders record the authentication results they saw, so a later receiver can choose to trust them. Experimental means it is not on the Standards Track.
RFC 9989 is candid about it. Section 7.4 names ARC as "a prominent example" of work on the mailing list problem, then says: "as of this document's publication, none of the methods have become widely used." Some receivers do use ARC as an input to local policy, but no receiver promises to override a DMARC failure because of it. ARC explained and DMARC and email forwarding go deeper.
What about MTA-STS and TLS-RPT?
MTA-STS (Mail Transfer Agent Strict Transport Security, RFC 8461) and TLS-RPT (SMTP TLS Reporting, RFC 8460) have both been Standards Track since September 2018. They protect mail in transit rather than the sender's identity. The GOV.UK standard already requires MTA-STS for government domains and recommends TLS-RPT.
A minimal pair of records looks like this:
_mta-sts.example.co.uk. 3600 IN TXT "v=STSv1; id=20261115"
_smtp._tls.example.co.uk. 3600 IN TXT "v=TLSRPTv1; rua=mailto:tls-reports@example.co.uk"
The policy file itself is served over HTTPS at https://mta-sts.example.co.uk/.well-known/mta-sts.txt. Start in mode: testing, read TLS-RPT reports, then move to mode: enforce. MTA-STS vs TLS-RPT explains the split.
What is likely to happen next?
This section is our assessment, not a published rule. It extrapolates from the facts above. The most likely direction is steady tightening of existing requirements, rather than a new protocol that replaces DMARC. Treat each point as a planning assumption to revisit, not a deadline.
- Receivers adopt DMARCbis gradually. Standards Track status removes an old objection, but receiver software changes on its own schedule. Expect the DNS Tree Walk,
npandtto appear in receiver behaviour and in aggregate reports over months to years. - Mailbox providers keep tightening. The pattern since 2024 is announce, then enforce, then escalate: Gmail moved from spam-foldering to rejections in November 2025, and Microsoft moved from Junk to rejection before its rules started. Further steps along that line are more likely than a reversal.
- Enforcement becomes the normal end state for owned domains. BIMI already requires quarantine or reject, and government baselines target it. Most advice now treats
p=noneas a starting point, not a destination. - Government guidance gets updated for RFC 9989. Several mandates still describe the removed
pcttag and older reporting arrangements, so revisions are probable. We have no announced dates. - Transport security moves up the checklist. MTA-STS is already required in UK central government, so it is likely to appear in more audits and supplier questionnaires.
What is still unknown?
Several important questions have no public answer in November 2026. Saying so plainly is more useful than guessing, because each one affects how an MSP sets client expectations. These are the gaps we would watch, with the reason each one matters.
| Open question | Why it matters | What to do meanwhile |
|---|---|---|
When will Gmail, Yahoo and Microsoft implement the DNS Tree Walk, np and t? |
Until they do, receivers may still treat a record as RFC 7489 did | Publish records that behave sensibly under both: valid p, explicit sp where needed, no reliance on t alone |
Will any mailbox provider require p=quarantine or p=reject for bulk senders? |
It would turn many monitoring projects into deadlines | Move owned domains toward enforcement on your own schedule |
| Will lower volume thresholds than 5,000 a day be introduced? | It would pull more small senders into scope | Apply the bulk sender checklist to every client anyway |
| Will BIMI become an RFC, and will CMC acceptance spread beyond Gmail? | It decides whether BIMI is a niche or a default | Treat BIMI as optional and certificate costs as per-client decisions |
| Will ARC, or a successor, become something receivers rely on? | It decides whether p=reject stays risky for mailing list users |
Follow RFC 9989 Section 7.4 and keep DKIM signing robust |
| What reporting addresses should UK public sector bodies use after Mail Check? | The GOV.UK page still shows NCSC reporting addresses | Confirm with the NCSC before copying them into new records |
Provider help pages also lag the standard. Google's BIMI setup page, for example, still describes a percentage value from RFC 7489. Where a provider page and RFC 9989 disagree, record both and follow the provider for that provider's mailboxes.
How should MSPs change their service offering now?
Change three things now: audit every client record against RFC 9989, sell enforcement as the default outcome rather than monitoring, and put a dated review of provider and government rules into the service. None of that waits on the unknowns above. How MSPs should update their DMARC service offering covers packaging in detail.
What should the portfolio audit look for?
The audit looks for retired tags (pct, rf, ri), missing sp or np policies, and domains still at p=none with no plan to move. Start by pulling every client's _dmarc record. A quick pass from a shell:
for d in example.com example.co.uk example.org; do
printf '%s: ' "$d"; dig +short TXT "_dmarc.$d"
done
On Windows, Resolve-DnsName -Type TXT _dmarc.example.com returns the same record. Flag any record that still contains pct, rf or ri. A typical clean-up for a client at quarantine:
Before: v=DMARC1; p=quarantine; rf=afrf; ri=3600; rua=mailto:dmarc@example.com
After: v=DMARC1; p=quarantine; np=reject; rua=mailto:dmarc@example.com
A record that still carries a percentage value needs the same treatment: delete the pct tag and choose the policy level you actually want. Receivers ignore unknown tags, so old records do not break, but they no longer do what the client thinks. The DMARCbis readiness checklist has the full list.
What should change in the service menu?
The service menu should shift from monitoring as the product to enforcement as the product, with transport security and BIMI as add-ons and a dated rules review built in. In practice:
- Default to enforcement. Scope every engagement to end at
p=quarantineorp=reject, withnp=rejecton domains that should have no undefined subdomains. - Add transport security. Offer MTA-STS and TLS-RPT as a line item, starting with UK public sector and regulated clients.
- Treat BIMI as an add-on. Only for clients already at enforcement, with certificate choice (VMC or CMC) explained per provider.
- Add a quarterly rules review. Check the Google, Yahoo, Microsoft, NCSC and GOV.UK pages each quarter and record the date you checked.
- Update client language. Replace "DMARC is a recommendation" with "DMARC is a Standards Track protocol". How the new standard affects client conversations has wording.
FAQ
Is DMARC being replaced by something else?
No. In May 2026 DMARC moved from an Informational RFC to the Standards Track with RFC 9989, 9990 and 9991. BIMI builds on DMARC enforcement, and ARC tries to patch its forwarding gap. Nothing published or in active IETF work proposes to replace DMARC as the domain-level authentication policy.
Do Gmail, Yahoo or Microsoft require p=reject?
Not for ordinary sending in November 2026. All three require at least p=none with SPF and DKIM from bulk senders, which Gmail and Outlook.com define as more than 5,000 messages a day. BIMI logos are different: Gmail and Yahoo require p=quarantine or p=reject before a logo can appear. Whether bulk rules will ever require enforcement is unknown.
Has anything changed for existing DMARC records under DMARCbis?
Records still work, because receivers ignore unknown or retired tags. But pct, rf and ri no longer have any defined effect, and organisational domain discovery now uses a DNS Tree Walk. Audit records, remove retired tags, and consider np and t where they help.
Will BIMI become mandatory?
There is no sign of that. BIMI is an individual Internet-Draft, not an RFC, and each mailbox provider sets its own display rules. Yahoo does not require a certificate; Gmail requires a VMC or CMC. BIMI remains an optional brand feature that depends on DMARC enforcement being in place first.
Next steps
Check where a client stands today with the DMARC checker or scan a whole portfolio with the domain DMARC scanner. For the standard itself, read DMARCbis explained; for wider protection, see email protection.
DMARC AI is multi-tenant DMARC monitoring built for MSPs. It processes aggregate (RUA) reports across client domains and uses AI assistance to highlight failing sources and alignment problems, which is the work that moves a portfolio from monitoring to enforcement.