RFC 8463: A New Cryptographic Signature Method for DomainKeys Identified Mail (DKIM)
In plain English — editorial summary, not part of the RFC
This document adds a new signing algorithm, Ed25519-SHA256, to "DomainKeys Identified Mail (DKIM) Signatures" (RFC 6376). DKIM verifiers are required to implement this algorithm.
Document record
- Document ID
- RFC8463
- Published
- September 2018
- Authors
- J. Levine
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 6376
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8601Message Header Field for Indicating Message Authentication StatusCurrent
May 2019
- RFC 8617The Authenticated Received Chain (ARC) ProtocolCurrent
July 2019
- RFC 7960Interoperability Issues between Domain-based Message Authentication, Reporting, and Conformance (DMARC) and Indirect Email FlowsCurrent
September 2016
- RFC 7601Message Header Field for Indicating Message Authentication StatusObsoleted
August 2015
- RFC 7001Message Header Field for Indicating Message Authentication StatusObsoleted
September 2013
- RFC 9991Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Failure ReportingCurrent
May 2026
- RFC 5672RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- UpdateObsoleted
August 2009
- RFC 5617DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)Updated
August 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?