For the first time in nearly two decades, the Internet Engineering Task Force (IETF) is undertaking a major redesign of one of email's foundational authentication standards.
The proposed specification, known as DKIM2, is designed to address long-standing challenges with forwarded and modified messages, strengthen protection against replay attacks, and create a clearer record of how an email travels from sender to recipient.
DKIM2 is the next generation of DomainKeys Identified Mail (DKIM). It builds on the original standard by improving how authenticated messages are handled as they pass through intermediaries such as forwarding services and mailing lists, while introducing stronger cryptographic options and better protection against abuse. Although the specification is still under development, it is designed to remain compatible with existing DKIM deployments, making the transition much easier than many organizations might expect.
The specification remains under development, so for most senders there is no immediate action required. But understanding where DKIM2 is headed will help organizations prepare for the future of email authentication.
What is DKIM?
DomainKeys Identified Mail (DKIM) is one of the core email authentication protocols used to verify that an email message was authorized by the sending domain and has not been altered during transit.
When an email is sent, the sending server digitally signs selected parts of the email using a private cryptographic key. Receiving mail systems retrieve the corresponding public key from DNS and verify that signature. If the signature validates, the receiver can be confident the message is authentic and unchanged.
Alongside SPF and DMARC, DKIM forms a critical part of modern email authentication. It helps mailbox providers distinguish legitimate mail from messages that may be spoofed or manipulated.
Despite being standardized nearly 20 years ago, DKIM has proven remarkably durable. But email itself has evolved significantly, exposing areas where the original design could be improved.
Why is DKIM being redesigned?
The development of DKIM2 is not an indication that DKIM failed. Quite the opposite.
The challenge is that today's email ecosystem is far more complex than it was when the standard was first developed. Messages are routinely forwarded, filtered, modified by security gateways, or redistributed through mailing lists before reaching their final destination.
Many of those changes are legitimate. However, even a small alteration to signed content can cause the original DKIM signature to fail validation.
Another long-standing challenge has been the DKIM replay attack, where an attacker obtains a legitimately signed email and repeatedly resends it to many recipients. Because the original signature remains valid, recipients may initially view those messages as authentic.
The industry has developed workarounds over the years, including ARC (Authenticated Received Chain), but operational experience has shown there's room to improve the underlying standard itself rather than continuing to layer additional solutions on top.
DKIM2 represents that evolution.
What changes with DKIM2?
Rather than replacing DKIM, DKIM2 refines it based on nearly two decades of real-world operational experience.
DKIM provides evidence that a domain signed a particular version of a message. DKIM2 is designed to provide a verifiable record of how that message moved through the delivery chain.
As an email passes between systems, each participating domain can document that it handled the message. When a system modifies the email, it records information about those changes and adds a new signature.
The result is an authenticated chain of custody from the message’s origin toward its final destination.
Better handling of forwarded email
One of DKIM's biggest limitations has always been forwarded email and mailing lists. When an intermediary modifies a message, even for legitimate reasons, the original signature may no longer validate.
Under the proposed DKIM2 model, intermediaries that alter a message are expected to record what changed before applying a new signature. This creates a clearer record of how the message was handled while preserving trust in the authentication process.
This does not mean every modified message will automatically be trusted. It gives receiving systems stronger evidence to determine who handled the message, what changed, and whether the delivery chain makes sense.
Stronger protection against replay attacks
DKIM2 is designed to include more information about the transmission of a message, including details associated with its source and intended destination.
This matters because a valid message delivered to its intended recipient is different from that same message being copied and sent elsewhere.
By binding more delivery information into the authentication chain, DKIM2 can help receiving systems identify when a legitimately signed message appears to have been unexpectedly replayed.
No authentication standard can eliminate abuse entirely, but DKIM2 is intended to give receivers more context than a standalone DKIM signature provides today.
Support for modern cryptography
Today's DKIM implementations primarily rely on RSA keys, but modern email infrastructure needs greater cryptographic agility. The current DKIM2 proposal expands support for additional cryptographic algorithms, such as RSA-SHA256 and Ed25519-SHA256 giving organizations greater flexibility as security best practices continue to evolve.
Importantly, this doesn't mean organizations need to replace their existing keys immediately. Current DKIM public keys are expected to remain usable during the transition.
Clearer message accountability
One less visible, but important, change is improved accountability throughout a message's journey.
When systems modify and resend messages, DKIM2 provides a more structured way to document those changes. That additional transparency can also improve how receiving systems determine where asynchronous bounce notifications should be sent, giving senders better visibility into delivery issues.
DKIM vs DKIM2: What stays the same?
For most senders, the reassuring news is that DKIM2 is designed to be evolutionary, not disruptive.
Organizations won't need to rebuild their entire email authentication strategy overnight.
Current DKIM deployments are expected to continue working alongside DKIM2 during a transition period, allowing senders, mailbox providers, and software vendors to adopt the new standard gradually.
Many organizations will also be able to continue using their existing DNS-based public keys while deciding whether and when to adopt newer cryptographic algorithms.
For email service providers and organizations operating their own email infrastructure, implementation will largely resemble previous protocol upgrades rather than requiring a complete redesign.
What should email senders do now?
DKIM2 is still under development, and important details may change before it becomes an agreed standard. Therefore there is no need to rush implementation.
Instead, organizations should focus on understanding how the standard is evolving and ensure their email infrastructure can adapt when the time comes.
A few practical steps include:
- Continue following DKIM, SPF, and DMARC best practices.
- Monitor the progress of the IETF DKIM2 working group.
- Review how your infrastructure handles forwarded messages and asynchronous bounce processing.
- Talk with your email infrastructure provider about future DKIM2 support.
Looking ahead
Email authentication has never stood still.
Standards such as SPF, DKIM, DMARC, and ARC have continued to evolve as attackers, infrastructure, and business requirements have changed.
DKIM2 represents the next step in that evolution. Rather than replacing the authentication ecosystem organizations already rely on, it strengthens it by addressing long-standing operational challenges while maintaining compatibility with today's deployments.
The specification is still under active discussion, and widespread adoption is likely to take time. But for ESPs, mailbox providers and other organizations that depend on email as business-critical infrastructure, understanding what's coming now will make future adoption significantly easier.
Halon x DKIM2
At Halon, we closely follow emerging email standards and plan to develop early beta implementations as the DKIM2 specification matures. Participating early allows us to contribute operational experience back to the standards process while helping customers prepare for future changes.
Frequently Asked Questions
Do I need to change my DKIM DNS records for DKIM2?
Not immediately. One of the goals of DKIM2 is to remain compatible with existing DKIM deployments, allowing organizations to continue using their current public keys during the transition.
Will DKIM2 work with DMARC?
Yes. DKIM2 is intended to complement, not replace, existing email authentication protocols, including DMARC.
Will DKIM2 replace ARC?
Yes. One of the goals of DKIM2 is to replace ARC by incorporating support for authenticated forwarding and message modification directly into the new standard. While the specification is still being finalized, the IETF's direction is that DKIM2 will supersede ARC rather than operate alongside it.
Can I implement or test DKIM2 today?
Yes. While the specification is still being finalized, the IETF DKIM2 working group has published sample implementations and test cases so developers and email infrastructure providers can begin experimenting with the new standard. Widespread production support will come later as the specification stabilizes and mailbox providers begin rolling out support.
Does DKIM2 stop phishing and spoofing?
No single technology can eliminate phishing or spoofing. DKIM2 strengthens one important layer of email authentication, but it works alongside SPF, DMARC, and other security measures as part of a broader email security strategy.