When will I need to set up DKIM2?

Updated on 11 Nov 2026: We clarified DKIM2 setup timing, selector names, and the draft DNS guidance, including what still needs to work for DMARC.
Most domain owners do not need to migrate to DKIM2 (DomainKeys Identified Mail v2) yet. Act when the service signing your mail or your mail server vendor documents a supported rollout and specifies any required signing or DNS changes. A provider request for an ordinary DKIM selector named "dkim2" is a separate setup task, explained below.
DKIM2 remains active IETF work, not a finished RFC or general production requirement. The IETF working-group documents list active drafts for the core signature format, DNS key records, and best practices. Draft revisions still make supported provider documentation the trigger for production changes.
Do not pre-stage experimental DKIM2 DNS
Do not publish experimental DKIM2 DNS records on a production domain before your provider documents the exact record format. Use only the hostnames and values issued by the service that signs your mail. This precaution does not delay an ordinary DKIM setup request that happens to use a selector named "dkim2".
A selector named dkim2 does not mean DKIM2
A DKIM selector is a label used to locate a public key, not a protocol version. A provider can use dkim1 and dkim2 as selector names for ordinary DKIM, including during key rotation. If its supported setup instructions request dkim2._domainkey.example.com, follow those instructions now. RFC 6376 defines how selectors locate DKIM keys.
To check which protocol a message uses, open its raw headers. In an ordinary DKIM-Signature header, v=1 identifies the signature version, s= identifies the selector, and d= identifies the signing domain. A selector value of s=dkim2 does not turn that signature into DKIM2. The proposed protocol uses a separate DKIM2-Signature header.
If the request is unclear, ask whether it concerns an existing DKIM selector or a DKIM2 protocol pilot. Do not rename a working selector or change a DNS version tag based on its name.
When DKIM2 becomes your job
DKIM2 becomes a domain-owner task when it moves out of general standards discussion and into a supported sender workflow. Look for a documented migration path you can test. Check receiver support for your own mail streams; a controlled pilot does not require every major mailbox provider to adopt DKIM2 first.
If you run your own outbound MTAs, that line arrives earlier. If you use a hosted mailbox, CRM, email service provider, or ticketing platform, that line arrives when the provider updates its sender authentication documentation and its support team can troubleshoot DKIM2.
- Provider support: Your outbound platform says DKIM2 signing is supported for your account type, not only in a lab or closed pilot.
- Receiver use: The receivers in your pilot document whether they verify DKIM2 and how the result affects message handling.
- DNS instructions: The sender specifies whether DNS changes are needed and, if so, gives you the exact selector and record values, plus the rotation process.
- Reporting signal: Supported Authentication-Results headers or provider logs show DKIM2 outcomes separately from normal DKIM. Ordinary DMARC reports alone do not establish DKIM2 support.

DKIM2 rollout checks for provider support, receiver use, DNS instructions, and safe deployment.
Brand senders mostly wait for supported provider workflows. Email service providers, mailbox providers, MTA vendors, and self-hosted operators have engineering work before brand senders see a stable setup path.
DKIM2 timing: not yet, watching, time to act
Use three timing buckets for DKIM2. They keep teams from doing DNS work too early, but they also stop the topic from being ignored until a mailbox provider deadline appears.
DKIM2 readiness stages
A practical timing model for domain owners and mail operators.
Not yet
Read and prepare
Draft specifications and early code exist, but your sender has no supported setup path.
Watching
Track signals
Your provider, MTA vendor, or major receivers announce tests or pilot support.
Time to act
Roll out
Provider documentation specifies required changes, testing, monitoring, and rollback.
Use your provider's documented support to decide your stage. Teams that own MTA code, sign mail for customers, forward mail at scale, or run inbound filtering systems need to follow the drafts, test libraries, and plan for dual signing before customers ask for it.
Provider signals that justify a DKIM2 rollout
The strongest DKIM2 signal is operational documentation that states what your account supports and explains validation and rollback. Confirm the provider's required signing changes and whether it needs any DNS changes before scheduling production work.
|
|
|
|---|---|---|
Sender docs | Setup steps | Roadmap notes |
Mailbox use | Header results | Private rumors |
DNS setup | Exact record or confirmation none is needed | Sample only |
Support path | Troubleshooting | No owner |
Look for specific evidence before changing production DNS.
Another useful sign is support language that names failure behavior. Check what happens when DKIM2 verification fails but normal DKIM passes, how the provider exposes that result, and whether support can separate DNS errors from signing errors.
For hosted senders, watch the provider's normal DKIM setup documentation, admin notices, and release notes. A documented DKIM2 setup flow is a stronger signal than general industry coverage.
A vendor announcement still needs details
- Selector naming: Ask whether the provider will reuse existing keys and selectors or issue new ones. Selector names alone do not identify the protocol.
- Key handling: You need key length, key type, rotation timing, and private-key ownership.
- Rollback: You need a way to disable DKIM2 signing without breaking normal DKIM.
- Result visibility: You need verification states, error details, and logs that separate DKIM2 from normal DKIM.
Why there is no universal DKIM2 deadline
The IETF drafts do not set a mandatory date for domain owners to migrate to DKIM2. A draft's expiration date concerns the document's validity as work in progress; it is not a date when existing DKIM stops working.
Treat draft publication, pilot code, and interoperability results as readiness evidence. A provider can set its own rollout schedule, so check whether its notice concerns a pilot or a production requirement and what action your account needs.
Draft DNS details are not deployment instructions
The November DNS draft keeps public keys under selector._domainkey.<signing-domain> and retains v=DKIM1 for key records used by DKIM2. It also proposes a separate domain policy TXT record at _domainkey.<domain>. A DNS version tag alone therefore does not identify the signing protocol. These draft formats can change; do not invent v=DKIM2 records or add a policy record without a documented deployment requirement.
What to do while waiting
The best DKIM2 preparation is routine DKIM maintenance. A domain with broken selectors, weak keys, mismatched signing domains, or unknown senders has to fix those problems before DKIM2 adds value.
Start with a focused DKIM checker pass across your active selectors. Then compare the result with real DMARC aggregate data so you know which services actually send mail for the domain.
DKIM checker
Check selector records and public key configuration.
?/7tests passed
Check two different things: DNS validity and message-level signing behavior. DNS can be perfect while a sender still fails to sign outbound mail. A sender can sign mail while using a domain that does not satisfy DMARC alignment. RFC 9989 bases a DMARC pass on successful DKIM or SPF authentication with DMARC alignment, so a DKIM2 pass alone does not establish a DMARC pass.
- Keep DKIM valid: Every active sender should sign with a public key that resolves cleanly in DNS.
- Use strong keys: Prefer 2048-bit RSA where supported, and replace shorter RSA keys through your provider's rotation process. Revoke compromised keys promptly.
- Verify selectors: Record which selectors belong to each sender, use distinct selectors for independently managed keys, and avoid conflicting public-key records at the same hostname.
- Track DMARC alignment: Compare the DKIM d= signing domain with the visible From domain. Strict alignment requires an exact match; relaxed alignment uses the same organizational domain.
- Avoid early changes: Do not add invented DKIM2 selectors, TXT records, or CNAMEs before your sender documents them.
During routine key rotation, publish the new selector before switching signing and retain the old public key while previously signed mail is still being delivered. RFC 6376 describes this overlap.
Illustrative DKIM DNS pattern, not a usable keyDNS
selector1._domainkey.example.com. TXT "v=DKIM1; k=rsa; p=MIIB...AQAB"
Migration paths to expect
DKIM2 setup depends on who operates the signing system. A hosted mailbox customer follows the provider's rollout instructions, including any DNS changes. A self-hosted MTA operator tests signing code. An ESP prepares dual signing, inbound bounce handling, customer reporting, and support guidance.
The DKIM2 best-practice draft recommends signing with both DKIM1 and DKIM2 during migration. Verify how participating receivers handle both results before a pilot. If you need the protocol detail first, read DKIM2 changes before changing records.
Hosted sender
- Setup owner: The provider controls signing code and tells you whether DNS changes are required.
- Main risk: Premature DNS edits create records the provider does not use.
- Best action: Wait for supported docs, then test one sending source at a time.
Self-hosted or ESP
- Setup owner: Your mail engineering team owns signing, verification, and logging.
- Main risk: Partial support creates headers your downstream systems cannot explain.
- Best action: Pilot in a controlled stream and keep DKIM1 as the stable baseline.
Keep current DKIM records during a DKIM2 pilot unless your signing provider explicitly documents a replacement. Keep a change log for selectors, DNS owners, signing vendors, and the business systems that depend on each sender.
A useful rollout checklist
- Inventory senders: List every service that signs mail for the domain or a subdomain.
- Map selectors: Document each selector, DNS zone owner, and private-key owner.
- Test one stream: Start with low-risk transactional or internal mail before broad marketing sends.
- Compare results: Check normal DKIM, DKIM2 headers, DMARC results, and receiver behavior together.
If your question is mainly whether to edit current DKIM records, use DKIM2 record changes to check the decision. For background, the first best-practices draft announcement explains the early operational guidance; use the current IETF draft linked above for ongoing implementation work.
Monitor current DKIM and DMARC with Suped
Suped is our DMARC reporting and email authentication platform. Use it to review current DKIM and SPF results by sending source and investigate authentication failures before planning DKIM2 changes. DKIM2 does not remove the need to know who sends mail for your domain today.
For most teams, the practical workflow is to run DMARC monitoring continuously, verify sources, and keep a clean sender list. Use those results as the current authentication baseline. Confirm DKIM2 verification through supported receiver headers or provider logs rather than assuming standard DMARC aggregate reports include it.
DMARC record detail view showing SPF, DKIM, DMARC, rDNS diagnostics, and DNS records
A periodic domain health check is also useful when teams have many domains, parked domains, and third-party senders. Use it to investigate current DNS issues before introducing signing changes.
What to track now
Track current DKIM pass rates and investigate unverified sources or DMARC failures. Keep selector creation dates and ownership in a separate inventory because those details are not reliably available in DMARC aggregate reports. Watch provider notices for supported DKIM2 deployment instructions.
Frequently asked questions
There is no universal DKIM2 protocol migration deadline. Follow supported instructions for your own sender, including any required DNS or signing changes. A request to configure an ordinary DKIM selector named "dkim2" is separate and should follow the provider's normal setup process.
No. The selector in an ordinary DKIM-Signature header can be s=dkim2 while the signature version remains v=1. The proposed DKIM2 protocol uses a separate DKIM2-Signature header. Follow your provider's instructions for existing selector records.
Do not assume replacement. Current draft migration guidance keeps normal DKIM in place while DKIM2 is tested or introduced in parallel.
Ask whether DKIM2 is supported, whether it is a pilot or production feature, which selectors it uses, how keys rotate, and how failures are reported.
The biggest mistake is publishing invented DKIM2 records before your sender supports them. Fix current DKIM and DMARC first.
Schedule production work when your signing service documents a supported rollout, required changes, and rollback, and you can test receiver behavior for your mail streams. Infrastructure operators can begin controlled testing earlier.

