Suped

DKIM2 explained: what changes and what stays the same

Published 9 Jul 2026
Updated 10 Nov 2026
12 min read
Summarize with
DKIM2 explained with an envelope, key, and email signature symbols.
Updated on 10 Nov 2026: We updated the DKIM2 draft references and clarified how to prepare while keeping current DKIM reliable.
DKIM2 (DomainKeys Identified Mail v2) has not made current DKIM obsolete. It is an active IETF working-group draft, while current DKIM records, selectors, public keys, private keys, DKIM-Signature headers, and DMARC alignment still matter for real email delivery. Do not remove, replace, or invent DNS records because DKIM2 exists in draft form.
The practical move is simple: keep current DKIM healthy, make sure DKIM passes for every legitimate sender, and use DMARC reporting to spot sources that fail authentication. DKIM2 is worth tracking because it tries to improve how email systems prove the path a message took, especially when message changes, forwarding, mailing lists, DKIM replay, and delayed delivery status notifications (DSNs) get involved.
  1. Keep your existing DKIM TXT records because receiving mail systems still use them.
  2. Do not publish data copied from Internet-Draft examples unless your provider supports an intentional DKIM2 test.
  3. Use DMARC aggregate data to find senders that fail DKIM.
  4. Maintain current authentication so future standards are easier to adopt.

What DKIM2 is

DKIM2 is active IETF work on a new email accountability mechanism. It builds on lessons from DKIM, ARC, forwarding behavior, mailing-list changes, replay abuse, and delivery failure handling. The aim goes beyond proving that one domain signed one version of a message. The design asks participating systems to document each transfer in a chain of custody.
An early IETF motivation draft described stronger authentication for the delivery path and an asynchronous return channel. The current working-group specification turns that goal into Message-Instance and DKIM2-Signature header fields. Receivers and intermediaries would get better evidence about who handled the message, where it was sent next, what changed, and where a delivery failure should travel.
Work in progress
Treat DKIM2 as standards work, not as a deployment checklist for ordinary domains. Internet-Drafts can change, expire, or be replaced before any final RFC exists. A domain owner should not create draft-based records or headers unless a controlled interoperability test and the mail provider's documentation require them.
That distinction matters because current DKIM is already deployed across real mail infrastructure. If your sender has bad selectors, stale public keys, missing private keys, or unsigned mail, DKIM2 will not fix that today. Make current DKIM reliable before planning around draft header formats.

What problem DKIM2 tries to solve

DKIM survives ordinary forwarding when the signed content remains intact. Harder cases appear when a mailing list or security gateway alters signed content. Replay is another limitation because a captured message can retain a valid signature when it is sent to new recipients. Current DKIM tells the receiver whether a signature verifies, but it gives less help when the message path itself needs accountability.
A normal reply that quotes an earlier email is a new message and gets its own DKIM signature when the replying sender's service signs it. It does not need to preserve the original message's DKIM signature. DKIM canonicalization also tolerates defined formatting changes: relaxed mode ignores some whitespace changes, while substantive edits to signed content invalidate the signature. These rules are defined in RFC 6376.
ARC remains deployed for intermediary authentication evidence, and RFC 8617 is still classified as Experimental. DKIM2 uses lessons from ARC but takes a different approach: each participating transfer adds to a verifiable chain, and a system that changes content can record how to reconstruct the earlier message state.
DKIM2 path accountability across the origin, forwarder, message changes, return path, and final verification.
DKIM2 path accountability across the origin, forwarder, message changes, return path, and final verification.
The main shift is path accountability. The current DKIM2 design asks each participating hop to sign the message state and handling context, declare where it is sending the message next, and preserve information that lets later systems assess changes. That differs from relying on a single origin signature that fails after a mailing list changes signed content. A verified chain records handling accountability; receivers still assess message content and reputation.
  1. DKIM2 records message modifications so earlier message states and signatures can be checked.
  2. Timestamps, nonces, recipient addresses, and next-domain context make copied signed mail easier to detect.
  3. Delivery failures can travel back through the authenticated path instead of reaching an unrelated address.
  4. A participating system can request feedback through the authenticated handling chain.
  5. Message-Instance hashes cover the body and header fields, apart from a defined set of fields with local or transit meaning.

How the current DKIM2 draft works

The IETF working-group specification is draft-ietf-dkim-dkim2-spec-09, published on 1 November 2026. It remains an active Internet-Draft. The separate header draft has been folded into the main specification. The companion DNS draft, revision 03, was published on 2 November 2026 and proposes a shared key-record specification for DKIM1 and DKIM2. Neither draft creates a production requirement for domain owners.
The design uses two new header fields. Message-Instance carries hashes of the message body and header fields. If a reviser changes signed content, the next Message-Instance can include a base64-encoded JSON Recipe that lets a verifier reconstruct the prior message state. DKIM2-Signature signs the Message-Instance chain and earlier DKIM2 signatures, along with handling data that binds each transfer to its path.
  1. Message-Instance hashes record the current body and header-field state.
  2. Recipes describe changes so a verifier can reconstruct and check an earlier message state.
  3. DKIM2-Signature headers add an ordered sequence, nonce, timestamp, SMTP envelope data, next-domain data, and cryptographic signatures.
  4. The current draft retains selectors and the selector._domainkey.domain DNS namespace used by DKIM.
The DNS draft retains v=DKIM1 in public-key records, including keys used for DKIM2. It also proposes a separate domain policy TXT record at _domainkey.example.com to control whether subdomains can authenticate the parent domain's From address. This remains draft behavior; keep provider-issued production records rather than changing their version to v=DKIM2.
A selector literally named "dkim2" or "selector2" is only a selector label. It does not mean the IETF DKIM2 protocol is active. Keep provider-issued selector records in place, but do not infer protocol support from the label.

What stays the same for domain owners

Current DKIM remains widely deployed. A receiving server reads the DKIM-Signature header, takes the selector and signing domain, looks up the public key in DNS, verifies the cryptographic signature, and reports pass or fail in Authentication-Results. DMARC then checks whether that passing DKIM domain is aligned with the visible From domain.
DKIM today
  1. Receivers find the sender's public key under the selector.
  2. The sending service signs mail and keeps the private key secret.
  3. A DKIM pass helps DMARC only when domain alignment is right.
  4. Every legitimate sender still needs correct signing.
DKIM2 direction
  1. Each participating step signs context about the transfer.
  2. Intermediaries document changes so earlier message states can be checked.
  3. Delivery failures and feedback can follow the authenticated handling path.
  4. DKIM2 requires mail-server support as well as DNS configuration.
For a current operational check, use a DKIM checker to confirm that your selector resolves to a valid public-key record. That work affects deliverability now.

Area

DKIM today

DKIM2 direction

Action

Status
Deployed
Active IETF draft
Track
DNS
TXT public key
Same key namespace; draft domain policy record
Do not improvise
Selector
s= tag
Selector remains
Keep rotating
DMARC
Uses aligned pass
Not defined as an input by RFC 9989
Monitor
Current DKIM compared with the active DKIM2 draft.

How DKIM and DKIM2 coexist

DKIM2 deployment is expected to include a period of dual signing. The working-group best-practices draft recommends that participating senders retain ordinary DKIM signatures alongside DKIM2 signatures while support spreads. This is draft guidance for implementers; domain owners should follow their provider's supported configuration.
Mixed paths need care. When a relay does not support DKIM2, a receiver cannot assume that the chain documents every transfer. Missing signatures or undeclared content changes limit what the receiver can verify. An ordinary DKIM signature or ARC evidence does not supply a missing DKIM2 signature, and final acceptance remains a receiver policy decision.
Ask providers which draft revision they implement and how they handle forwarding through systems without DKIM2 support. Keep current DKIM and DMARC checks in place during any controlled test. These drafts establish no universal cutover date or requirement to remove existing DKIM signatures.

Selectors, keys, and signatures

A DKIM selector is a label that lets one domain publish more than one public key. If the DKIM-Signature header says the selector is selector1 and the signing domain is example.com, the receiver queries selector1._domainkey.example.com. The public key is in a DNS TXT record; a provider-issued CNAME can delegate the lookup to a provider-managed TXT record. The sending system uses the matching private key to create the signature.
Current DKIM TXT record shape (truncated key)DNS
selector1._domainkey.example.com. 3600 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A..."
The private key never belongs in DNS. It belongs in the sender's email platform or MTA. For routine rotation, publish a new key under a new selector, let DNS caches refresh, switch signing, and keep the old public key until queued messages have cleared. If a private key is compromised, revoke the affected key promptly and switch to a fresh key. DKIM2 retains the need for selector ownership and private-key protection. Use rsa-sha256 with RSA keys of at least 2048 bits where supported, consistent with RFC 8301's recommendation.
Current DKIM-Signature header shapetext
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=example.com; s=selector1; t=1783555200; h=from:to:subject:date:mime-version; bh=base64-body-hash; b=base64-signature
Do not publish draft fields
Draft DKIM2 field names are not a DNS recipe. Publishing made-up DKIM2 data will not make receivers trust your mail. At best it gets ignored. At worst it adds confusion during troubleshooting and gives teams a false sense that future authentication is already handled.
The useful lesson from DKIM2 is to tighten the current system: give every sender its own selector where possible, document which service owns each private key, remove abandoned selectors, and keep DKIM signing tied to the domain that DMARC expects.

DMARC alignment still decides policy results

DMARC does not pass just because a message has any valid DKIM signature. The passing DKIM signing domain needs alignment with the visible From domain, called the Author Domain in RFC 9989, unless SPF passes with alignment instead. Many teams get tripped up when an email platform signs with its own domain, DKIM passes, and DMARC still fails.
Review DKIM alignment before treating DKIM2 as an action item. RFC 9989 defines the core DMARC protocol: at least one SPF or DKIM authentication result must pass with alignment to the Author Domain. It does not define DKIM2 as a DMARC authentication mechanism.
DMARC monitoring example with strict alignmentDNS
_dmarc.example.com. 3600 IN TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com; adkim=s; aspf=s"
In this example, adkim=s and aspf=s require exact domain matches. Relaxed alignment is the default when those tags are omitted; it permits the same organizational domain. p=none requests monitoring without quarantine or rejection based on the DMARC policy. These settings are defined in RFC 9989.
For live domains, DMARC monitoring helps identify which sources authenticate correctly and which pass only SPF. Use the reports to investigate DKIM failures and unfamiliar sources claiming your domain; the data alone does not establish whether a source is legitimate.
Practical best practice
  1. List every system that sends mail using your domain.
  2. Map each selector to the service and team that owns it.
  3. Move DMARC policy only after legitimate mail is passing.
  4. Investigate DKIM failures before blaming new standards work.

What to check now

Before spending time on DKIM2 planning, check the basics that affect mail now. Confirm that each sender signs mail, the selector resolves, the public key is valid, the signing domain matches your DMARC expectations, and the message survives any forwarding or gateway path your organization actually uses.
A broader domain health check is useful for reviewing SPF and DMARC alongside DKIM. Check SPF lookup limits and confirm that DMARC reporting is enabled.
?

What's your domain score?

Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.

Send a real test message through each important system, then inspect the received headers. Check Authentication-Results for dkim=pass and dmarc=pass, and compare the DKIM-Signature d= and s= values with the expected signing domain and selector. DNS can look correct while the sender still signs with the wrong domain, uses a stale selector, or skips DKIM on one message stream.
If you use double signing or multiple signatures, document why each signature exists and evaluate each result separately. For DMARC, one passing DKIM signature with the required domain alignment is enough, even when another DKIM signature fails.

Where Suped fits

Suped is our DMARC reporting and email authentication platform. Its role here is operational: build a sending-source inventory, find current DKIM and alignment failures, and stage DMARC policy changes without treating a draft protocol as a production control.
In Suped's product, DMARC reports group authentication results by source so a team can locate broken DKIM or alignment and confirm the result after a DNS or platform change. Alerts bring new failures into that workflow without requiring the team to decode raw aggregate XML.
While DKIM2 develops, use Suped for evidence about the deployed authentication system. Suped does not verify a DKIM2 chain or indicate that a provider supports the draft protocol. Check provider documentation and interoperability test results separately to establish which draft behavior is supported.
DMARC record detail view showing SPF, DKIM, DMARC, rDNS diagnostics, and DNS records
The screenshot workflow matters because DKIM2 will not remove the need for clear diagnostics. If a selector is missing, a public key is malformed, or a sender is failing DMARC alignment, the immediate task is to find the broken source and repair the current configuration.

How to prepare for DKIM2 deployment

Continue current DKIM and DMARC work while tracking DKIM2 implementation support. Current DKIM helps receivers associate mail with a signing domain and contributes to DMARC policy results.
DKIM2 preparation priorities
Use these categories to prioritize current authentication work and standards tracking.
Do now
Operational
Fix current DKIM failures and DMARC alignment issues.
Watch
Standards
Track working-group drafts and provider announcements.
Avoid
Risk
Do not create unofficial DKIM2 DNS records or custom headers.
Plan
Process
Keep selector ownership and key rotation records easy to audit.
For technical teams that run MTAs, DKIM2 deployment will require mail-server support for signing, header verification, recipes, and feedback handling. This work extends beyond a DNS update. The deployment profile draft describes an individual Informational proposal for milter integration. MTA operators should check which draft revision an implementation supports and how its behavior compares with the working-group specification.
For domain owners and marketers, preparation is less technical: know who sends mail, keep DKIM pass rates high, enforce DMARC gradually, and require vendors to use aligned DKIM. That work also supports controlled DKIM2 interoperability tests when your provider offers them.
  1. Audit every sending source now and confirm aligned DKIM for legitimate mail.
  2. Rotate weak or exposed keys, remove abandoned selectors after queued mail has cleared, and document key ownership.
  3. Before enforcement, use DMARC reporting to verify that real mail survives policy tightening.
  4. While DKIM2 evolves, follow provider guidance and avoid custom draft-based DNS changes.

Frequently asked questions

No. DKIM2 remains an active Internet-Draft, while current DKIM is the deployed mechanism receivers use today. Keep your existing DKIM records, selectors, and signing configuration in place.

No, not for ordinary production mail. Keep provider-issued DKIM records, and change them only when your provider gives deployment instructions for a supported implementation or controlled test. Do not copy draft examples into DNS.

RFC 9989 still evaluates SPF and DKIM with domain alignment. It does not define DKIM2 as an authentication input, so a DKIM2 test does not replace your existing DMARC configuration.

No. DKIM selectors are labels chosen by a provider or domain owner. A selector named dkim2 or selector2 can still point to an ordinary DKIM public key.

Keep every sending platform authenticated with aligned DKIM, review DMARC reports, and ask vendors which selectors and signing domains they use.

Document selector ownership, protect private keys, rotate keys safely, monitor DKIM failures, and follow provider documentation for any controlled DKIM2 test.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing