Topic starter
25/10/2026 11:08 am
TL;DR: Ed25519 DKIM remains uneven across major mailbox providers, according to Red Sift, with Gmail, Microsoft 365 and Yahoo among the holdouts and some receivers still accepting sub-1024-bit RSA keys. DKIM operators need to treat weak-key acceptance as the immediate risk, because forgery exposure comes before any algorithm migration can help.
Editorial analysis by NHI Mgmt Group, based on content published by Red Sift: “How widely supported are Ed25519 DKIM keys and how many providers still accept weak keys?”.
By the numbers:
- Only 9 out of 19 providers successfully validate Ed25519 DKIM signatures.
- Gmail, Microsoft 365, and Yahoo collectively handle the majority of global email traffic.
- The security algorithm provides approximately 128 bits of security, comparable to RSA-3072.
Key questions
Q: Why does Ed25519 DKIM create delivery risk in the current mailbox ecosystem?
A: Because DKIM validation is only useful when receiving providers recognise the algorithm consistently.
Q: What breaks when mailbox providers accept weak DKIM signatures?
A: Authentication breaks because a forged message can inherit the appearance of a valid domain signature.
Q: What should email teams do first when DKIM keys are still below 1024 bits?
A: Rotate weak DKIM keys immediately and verify that every sending domain uses at least RSA-2048 before any algorithm migration.
Practitioner guidance
- Audit DKIM key lengths across all sending domains Identify every selector still using sub-1024-bit RSA and rotate it to at least RSA-2048 before any broader authentication change.
- Test Ed25519 support by mailbox provider Send controlled test mail through the providers that matter most to your user base and record whether each one returns pass, neutral, perm_fail, or malformed results.
- Treat DMARC as a multi-provider control Review how SPF and DKIM alignment behave when one provider supports the algorithm and another rejects it, then set your rollout sequence from those results.
Bottom line: Ed25519 DKIM support is not yet universal enough for broad production rollout, especially where major mailbox providers still fail validation.
Glossary terms: DKIM, Ed25519, DMARC, Authentication-Results Header
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 7 days ago by NHI Mgmt Group
27/10/2026 7:14 pm
Ed25519 support is now a receiver-governance problem, not a cryptography problem. The key question is no longer whether the algorithm is sound, but whether the mailbox ecosystem can validate it consistently enough for enterprise use. When three dominant providers still fail to support a modern standard, senders cannot treat deployment as a unilateral choice. Practitioners should manage DKIM as a multi-party trust dependency, not a purely internal control.
A question worth separating out:
Q: Should organisations prioritise Ed25519 adoption or weak-key remediation first?
A: Weak-key remediation should come first. Ed25519 improves cryptographic efficiency, but it does not solve the immediate problem of broken RSA acceptance or provider inconsistency. Organisations get more security value by removing trivially forgeable keys before introducing a new signing algorithm that some major receivers still do not support.
👉 Read our full editorial: Ed25519 DKIM adoption is blocked by major mailbox providers
This post was modified 7 days ago by NHI Mgmt Group