DKIM2: What It Changes for Email Authentication and Deliverability

DKIM2: What It Changes for Email Authentication and Deliverability
Image

Estimated reading time: 15 minutes

DKIM has been a core part of email authentication for almost two decades. It allows receiving servers to verify that a message was signed by a particular domain and that the signed content hasn’t been altered. However, it has limitations, particularly when emails are forwarded, modified, or resent by unauthorized parties.

DKIM2 is being developed to address these gaps. Instead of relying on a single signature, it creates a verifiable record of the systems that handled a message, the recipients involved, and any changes made along the way.

For email senders, these changes could eventually improve how mailbox providers distinguish legitimate traffic from abuse. They also introduce new considerations for email authentication, sender reputation, and deliverability monitoring.

Key Takeaways

  • DKIM2 introduces a signed chain of custody. It records how an email moves between servers and documents changes made during transmission.
  • Replay attacks become easier to identify. DKIM2 helps receivers distinguish legitimate forwarding from unauthorized redistribution of signed messages.
  • Email forwarding could become more reliable. Mailing lists and gateways can document modifications instead of simply invalidating the original signature.
  • DKIM2 doesn’t guarantee inbox placement. Authentication remains one part of a broader deliverability assessment that includes sender reputation and recipient engagement.
  • The transition will be gradual. DKIM2 is still an IETF Internet-Draft, and existing DKIM authentication will continue to matter.
  • Senders should focus on their current authentication setup. Monitoring SPF, DKIM, DMARC, and inbox placement provides a useful baseline before adoption begins.

What DKIM Was Never Built to Prove

DKIM, first standardized in 2007 and updated through RFC 6376 in 2011, was designed to prove that a domain took responsibility for an email’s content.

However, a valid DKIM signature doesn’t establish the complete delivery history of a message.

There are three important limitations.

  • Who the message was intended for. DKIM signs selected headers and the message body, but not the SMTP recipient. A valid signature can remain attached when the message is sent to someone else.
  • Where delivery failures should be reported. The SMTP return path isn’t cryptographically tied to the DKIM signature. Attackers can exploit this weakness to direct bounce messages toward unrelated domains.
  • What changed during transmission. If a mailing list or forwarding service modifies signed content, DKIM verification may fail. The receiving server cannot determine from the failed signature alone whether the modification was harmless.

The first limitation is particularly relevant to sender reputation.

The Problem With DKIM Replay Attacks

In a DKIM replay attack, someone obtains a legitimately signed email and redistributes copies to additional recipients.

The signature may remain valid even though the original sender never authorized that distribution.

For example, an attacker could submit a message containing malicious content to a service that signs outgoing mail. After obtaining a valid signature, the attacker could redistribute the signed message at scale.

The receiving mailbox provider sees a message with a valid DKIM signature. However, that signature doesn’t prove that the signer authorized delivery to every recipient.

This creates a difficult situation for mailbox providers. They must distinguish suspicious redistribution from legitimate forwarding, often using behavioral and reputation signals.

Why it matters for deliverability: Abuse involving legitimately signed messages can damage trust in a sending domain. DKIM2 is intended to give receivers more reliable information about whether a message followed an authorized delivery path.

How DKIM2 Works: A Signed Chain of Custody

DKIM2 extends email authentication beyond the original signature.

Each participating system that handles a message can add a numbered signature recording its involvement. When the system modifies the message, it also documents the changes.

The November 2026 IETF working draft defines two important header fields.

Message-Instance

The Message-Instance header records cryptographic hashes representing the email headers and body at a particular point in the delivery process.

If an intermediary changes the message, it creates another instance.

For example, imagine a mailing list that receives an email and adds a footer:

You’re receiving this email because you subscribed to our mailing list.

Under traditional DKIM, adding this text can invalidate the original signature.

Under DKIM2, the mailing list can document the modification using a recipe: a base64-encoded JSON structure that explains how to reconstruct the earlier message.

The receiving server can then verify the previous version instead of treating the modification as unexplained.

DKIM2-Signature

The DKIM2-Signature header records the signing domain, signature sequence, and relevant SMTP transmission details.

Each new signature also protects the preceding chain, allowing the receiver to check whether the message followed a consistent path.

TagWhat it recordsWhy it matters
i=Signature sequence numberIdentifies each signing step
m=Highest Message-Instance coveredConnects a signature to the corresponding message version
mf=SMTP MAIL FROMHelps verify the sending path and return address
rt=SMTP RCPT TOLinks the message to its intended SMTP recipients
nd=Domain expected to sign nextSupports certain forwarding arrangements
t=Signing timestampHelps limit how long a signature remains acceptable
d=Signing domainIdentifies the domain responsible for the signature
s=Signature values, selectors, and algorithmsAllows receivers to verify the cryptographic signature
f=Flags such as exploded, feedback, and feedhereIndicates redistribution or requests delivery feedback
Key DKIM2 Signature Tags and Their Functions

A receiver checks the newest signature against the SMTP transaction and then validates the earlier signatures and message instances.

The draft also introduces additional requirements, including checks that the visible From address is authentic relative to the relevant signing domain.

Three Details Worth Understanding

1. DKIM2 can identify suspicious message redistribution.

A mailbox provider can compare instances of a message that arrived through intermediaries.

If multiple copies appear without an appropriate indication that the message was distributed to multiple recipients, that can become a replay signal.

2. Successful authentication doesn’t mean the content is trustworthy.

A DKIM2 verification result can establish that the recorded delivery path and message modifications are consistent.

It doesn’t prove that the email is safe, relevant, or wanted.

Mailbox providers still need to evaluate content and sender reputation before making delivery decisions.

3. DKIM2 builds on existing DNS infrastructure.

DKIM2 is designed to use the existing selector-based DKIM public-key infrastructure. This reduces the need to establish a completely separate system for publishing cryptographic keys.

However, software and service providers will still need to implement DKIM2 signing and verification.

How DKIM2 Could Affect Email Deliverability

The main purpose of DKIM2 is to strengthen email authentication. Its impact on deliverability is less direct.

Mailbox providers already combine authentication results with other signals when deciding whether to accept, reject, or filter a message.

DKIM2 could improve the accuracy of those decisions by providing more information about the message’s origin and transmission history.

More Reliable Authentication for Forwarded Emails

Forwarding has long complicated email authentication.

When a message is forwarded, SPF often fails because the forwarding server isn’t authorized in the original sender’s SPF record.

DKIM can preserve authentication if the message remains unchanged. However, mailing lists and security gateways frequently modify messages by adding footers or rewriting content.

Those modifications can invalidate DKIM signatures, potentially contributing to DMARC failures.

DKIM2 addresses this problem by allowing intermediaries to document legitimate changes.

Instead of seeing only a broken signature, the receiver could verify the original message and identify the system responsible for the modification.

This may reduce authentication-related delivery problems for legitimate forwarded mail as DKIM2 adoption expands.

For a closer look at the existing problem, see our guide to email forwarding and DMARC.

Better Protection Against Reputation Abuse

DKIM replay attacks can exploit the reputation of legitimate signing domains.

DKIM2 makes these attacks more difficult by associating signatures with the message’s delivery path and intended recipients.

Receivers could use this information to distinguish authorized distribution from suspicious forwarding.

For legitimate senders, this could reduce the risk of unauthorized redistribution being mistaken for their normal sending activity.

However, DKIM2 won’t eliminate reputation problems caused by the sender’s own practices.

High spam complaint rates, unwanted messages, and poor engagement can still affect inbox placement even when authentication succeeds.

More Precise Troubleshooting

One of the most useful long-term effects of DKIM2 could be improved authentication diagnostics.

Under DKIM1, a failed signature may tell the sender that the signed message changed, but not which intermediary caused the problem.

DKIM2 provides additional information that could help identify where the verification chain failed.

For example, an administrator could distinguish between:

  • An email modified by a mailing list that correctly documented the change.
  • A security gateway that altered the message without supplying the required information.
  • A forwarding service that introduced an inconsistent delivery path.
  • A genuine signature or message-integrity failure.

These distinctions could make authentication troubleshooting more precise once receiving systems and diagnostic tools support DKIM2 results.

Six Operational Changes Senders Should Understand

DKIM2’s benefits go beyond replay protection and forwarding. Its introduction could also affect how organizations configure email infrastructure.

1. Forwarding Setups May Require Additional Key Management.

If a message arrives at one domain and leaves from another, the signing chain needs to account for that transition.

The DKIM2 draft describes ways to handle these situations, including an additional signature or the nd= tag.

In some configurations, a forwarding provider may need access to a signing key associated with the receiving domain, often through DNS-based key delegation.

This is relevant to organizations that use:

  • Email aliases across multiple domains.
  • Forwarding between parent companies and acquired brands.
  • External email routing or forwarding providers.

These arrangements will require coordination between domain owners and service providers.

2. Security Gateways Will Need to Document Modifications.

Corporate email gateways routinely modify incoming messages.

They may add external sender warnings, rewrite links for security scanning, or insert disclaimers.

Under DKIM2, systems that modify protected message content must document the changes if they want the earlier signatures to remain verifiable.

The draft also identifies transport-level conversions as a potential source of verification problems.

For organizations using several security layers, this creates an important implementation question: Will every intermediary support the required DKIM2 processing?

Until that support becomes consistent, some legitimate delivery paths may produce verification failures.

3. Bounce Messages Could Become More Trustworthy.

Traditional SMTP delivery status notifications can be abused through forged return paths.

This can cause backscatter, where delivery failure messages are sent to people who never sent the original email.

DKIM2 is designed to reduce this problem.

The newest signature ties the SMTP sending information to the domain responsible for the transmission.

A receiver can provisionally verify the relevant information before accepting a message. If verification fails, it can reject the email during the SMTP session rather than generating a later bounce to an untrusted address.

This could make delivery failure information more reliable.

However, senders shouldn’t assume that DKIM2 will automatically increase or decrease their bounce rates. Actual reporting behavior will depend on implementation and receiver policies.

4. From Address Authentication Becomes Part of Verification.

The newer DKIM2 drafts introduce requirements for the visible From address to be authentic relative to the relevant signing domain.

This is an important distinction because the From address is the identity recipients actually see.

The November 2026 draft also includes a Domain Policy Record mechanism allowing domain owners to restrict certain subdomain-based signing arrangements.

These changes could give domain owners more control over how their identities are used.

For organizations operating multiple domains and subdomains, they reinforce the need to maintain an accurate inventory of authorized sending systems.

5. Message Modification Records Introduce Privacy Considerations.

DKIM2 recipes can contain information needed to reconstruct an earlier version of a message.

That creates a potential privacy concern.

If a security gateway removes sensitive information from an email, some of that information could remain present in the recipe used to document the modification.

The specification accommodates situations where an earlier message body cannot be fully reconstructed, but this reduces the receiver’s ability to verify the complete history.

Organizations processing sensitive communications will need to consider how their gateways handle modification records.

6. DKIM2 Will Coexist With Existing Authentication Protocols.

DKIM2 is not an immediate replacement for SPF, DKIM1, or DMARC.

During the transition, email systems may support traditional DKIM signatures alongside DKIM2 signatures.

ARC, which helps receivers evaluate authentication information across forwarding paths, is also being reconsidered within the IETF. However, existing ARC implementations won’t disappear automatically.

DMARC will remain important for evaluating whether email claiming to come from a domain passes the relevant authentication and alignment checks.

The updated DMARC specification, RFC 9989, and its aggregate reporting companion, RFC 9990, were published in May 2026.

Importantly, current DMARC aggregate reports should not be confused with DKIM2 chain verification reports. They provide information about existing authentication mechanisms, but do not automatically expose the detailed DKIM2 delivery history described in the draft.

The DKIM2 Transition: What Happens to DKIM1?

DKIM2 won’t be introduced across the entire email ecosystem simultaneously.

Email service providers, sending platforms, forwarding services, and mailbox providers will need to implement support.

As of November 2026, DKIM2 remains an active IETF working-group draft. The latest specification is draft-ietf-dkim-dkim2-spec-09, published on November 1, 2026.

The protocol is still under development, so implementations and requirements may change before standardization.

During the transition, senders could encounter different combinations of traditional DKIM and DKIM2 verification results.

DKIM1DKIM2Possible explanationWhat to investigate
PassPassBoth authentication mechanisms verified successfullyCheck inbox placement and reputation separately
PassNoneDKIM2 isn’t present or supported for this messageConfirm whether the sending service supports DKIM2
PassFailTraditional DKIM passes, but the DKIM2 chain has a problemCheck envelope data, forwarding paths, and intermediary signatures
FailPassA message was modified in a way that broke DKIM1 but was correctly documented under DKIM2Review forwarding and modification records
FailNoneTraditional authentication failed and DKIM2 wasn’t availableTroubleshoot the existing DKIM setup
How to Interpret DKIM1 and DKIM2 Results During the Transition
These are illustrative combinations rather than guaranteed provider classifications. Actual reporting will depend on DKIM2 adoption and implementation.

The fourth combination is particularly interesting.

Today, a forwarded message with a broken DKIM signature may be difficult to distinguish from an email that was modified unexpectedly.

With DKIM2, a legitimate modification could be documented and verified.

Conversely, an email that passes traditional DKIM but fails DKIM2 could reveal a delivery-path problem that existing DKIM verification wouldn’t detect.

This introduces a new layer of information that deliverability teams may eventually need to analyze.

How to Prepare Your Email Infrastructure for DKIM2

There is no need for most senders to deploy DKIM2 immediately.

The protocol is still evolving, and much of the implementation will depend on ESPs, mail servers, and forwarding providers.

However, organizations can prepare by identifying how messages are currently authenticated and delivered.

1. Establish a Baseline of Your Current Authentication Results.

Start with SPF, DKIM, and DMARC.

Before adopting a new authentication mechanism, you should know which sources currently send email on behalf of your domain and whether their messages pass existing checks.

Review:

  • SPF authentication results for authorized sending infrastructure.
  • DKIM signature validity and alignment with the From domain.
  • DMARC compliance across legitimate sending sources.
  • Unexpected sending IP addresses or authentication failures.

GlockApps DMARC Analytics helps domain owners monitor authentication results and identify sending sources through aggregate reports.

This gives teams a clearer picture of their current configuration and helps them recognize changes as email authentication evolves.

It is important to remember that these are current SPF, DKIM, and DMARC results, not DKIM2 verification results.

2. Inventory Every Sender and DKIM Selector.

Organizations often send email through several systems:

  • Marketing email platforms.
  • CRM and sales automation tools.
  • Customer support platforms.
  • Transactional email services.
  • Internal applications and SMTP servers.

Each may use different DKIM selectors or signing arrangements.

Create a list of every authorized source and identify which domains and selectors it uses.

Review unused selectors and clarify which provider manages each key.

Because DKIM2 builds on the existing DKIM key infrastructure, maintaining accurate records will simplify future implementation.

You can also review our email authentication guide for more information about DKIM configuration and alignment.

3. Identify Your Email Forwarding Paths.

Forwarding is one of the main areas DKIM2 is intended to improve.

Review the services that forward messages using your domains.

Pay particular attention to mail forwarded through mailing lists, corporate gateways, and cross-domain aliases.

In current DMARC reporting, forwarding can sometimes appear as traffic from an unexpected IP address. SPF may fail while DKIM still passes.

However, this combination isn’t definitive proof of forwarding. Compare the findings with your actual infrastructure before classifying the source.

4. Identify Systems That Modify Emails.

Review which intermediaries change messages during transmission.

Examples include security gateways that insert warnings, mailing lists that append footers, and filtering systems that rewrite links.

These systems may eventually need to create DKIM2 modification records.

Ask your providers whether they plan to support DKIM2 and how they intend to handle message changes.

5. Keep Monitoring Authentication and Reputation.

DKIM2 will not replace the need for regular deliverability monitoring.

Even with successful authentication, a message can still be rejected or placed in spam because of poor sender reputation or other filtering signals.

Monitor sudden increases in authentication failures, changes in sending infrastructure, and unexpected variations in inbox placement.

These patterns are useful today and may provide context when new authentication mechanisms become available.

6. Test Inbox Placement Instead of Relying Only on Authentication Results.

A successful authentication check doesn’t tell you whether your message reaches the inbox.

Mailbox providers evaluate more than DKIM signatures. They also consider sender reputation, sending behavior, spam complaints, and message characteristics.

For that reason, senders should test actual email placement instead of assuming authentication success guarantees delivery.

GlockApps Inbox Insight allows you to test messages across mailbox providers, including Gmail, Outlook, and Yahoo.

 

The reports show where test emails land and provide information about existing authentication results, sender reputation, and potential deliverability problems.

Regular testing is especially useful when changing ESPs, modifying email infrastructure, or troubleshooting unexpected spam placement.

For more information, read Why You Should Test Your Email Deliverability.

Conclusion

DKIM2 introduces a significant change to email authentication. Instead of verifying only the original signature, it aims to establish a verifiable record of the systems that handled a message and the modifications made during transmission.

This could help mailbox providers identify replay attacks, evaluate forwarded email more accurately, and distinguish legitimate message modifications from suspicious activity.

However, stronger authentication doesn’t automatically translate into better inbox placement.

Sender reputation and other filtering signals will continue to influence how mailbox providers handle incoming messages.

For now, the most useful preparation is to understand your existing email infrastructure. Make sure your sending sources are authorized, investigate authentication failures, and monitor actual inbox placement.

That work will remain relevant regardless of how quickly DKIM2 becomes widely adopted.

FAQ

What is DKIM2?

DKIM2 is a proposed email authentication protocol that extends traditional DKIM by recording a verifiable chain of custody for an email.
It allows participating systems to document the message’s delivery path and modifications made during transmission.

Is DKIM2 an official email authentication standard yet?

No. As of November 2026, DKIM2 remains an active Internet-Draft within the IETF DKIM working group.
The latest working-group specification is version -09, published on November 1, 2026. Its requirements may change before the protocol becomes a finalized standard.

Will DKIM2 replace traditional DKIM?

Not immediately. DKIM1 and DKIM2 are expected to coexist during adoption.
Organizations should continue maintaining their existing DKIM configuration while monitoring DKIM2 developments.

Will DKIM2 improve email deliverability?

Potentially. DKIM2 could help receivers distinguish legitimate forwarding from unauthorized redistribution and better understand message modifications.
However, it doesn’t guarantee inbox placement. Sender reputation and other filtering signals will still affect delivery decisions.

Related Posts

Email Authentication: the Ultimate Guide

Email authentication is becoming a big deal. Authentication allows the mailbox provider to confirm that the sender is the one Read more

Email Forwarding and DMARC

Email forwarding is a common practice in both personal and professional settings. Whether you're consolidating inboxes or routing customer messages Read more

Email Deliverability Rules

Email deliverability is one of those things that looks simple until it doesn’t. You can have a strong copy, a Read more

Why You Should Test Your Email Deliverability

Sending an email does not automatically mean it will reach the recipient’s inbox. Your message may land in spam, get Read more

AUTHOR BIO

Tanya Tarasenko
Technical Content Writer

The author has several years of experience creating high-quality content, with a strong focus on clear structure, readability, and truly meaningful insights.

She specializes in topics related to email deliverability, marketing technology, and digital communication. Her work is centered on making complex technical subjects accessible, practical, and genuinely useful for readers.