RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
In plain English — editorial summary, not part of the RFC
DomainKeys Identified Mail (DKIM) permits a person, role, or organization that owns the signing domain to claim some responsibility for a message by associating the domain with the message. This can be an author's organization, an operational relay, or one of their agents. DKIM separates the question of the identity of the Signer of the message from the purported author of the message. Assertion of responsibility is validated through a cryptographic signature and by querying the Signer's domain directly to retrieve the appropriate public key. Message transit from author to recipient is through relays that typically make no substantive change to the message content and thus preserve the DKIM signature. This memo obsoletes RFC 4871 and RFC 5672. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6376
- Published
- September 2011
- Authors
- D. Crocker; T. Hansen; M. Kucherawy
- Status
- INTERNET STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 76
- Also known as
- STD76
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 4870 (2007)
- RFC 4871 (2007)
- RFC 5672 (2009)
- RFC 6376 (2011)
Read the full history of DomainKeys Identified Mail (DKIM) Signatures →
Referenced by
4 later RFCs formally update or obsolete part of this document.
- RFC 8301Cryptographic Algorithm and Key Usage Update to DomainKeys Identified Mail (DKIM)Current
January 2018
- RFC 8463A New Cryptographic Signature Method for DomainKeys Identified Mail (DKIM)Current
September 2018
- RFC 8553DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node NamesCurrent
March 2019
- RFC 8616Email Authentication for Internationalized MailCurrent
June 2019
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6377DomainKeys Identified Mail (DKIM) and Mailing ListsCurrent
September 2011
- RFC 5617DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)Updated
August 2009
- RFC 5598Internet Mail ArchitectureCurrent
July 2009
- RFC 9057Email Author Header FieldCurrent
June 2021
- RFC 5322Internet Message FormatUpdated
October 2008
- RFC 5068Email Submission Operations: Access and Accountability RequirementsUpdated
November 2007
- RFC 1544The Content-MD5 Header FieldObsoleted
November 1993
- RFC 6647Email Greylisting: An Applicability Statement for SMTPCurrent
June 2012
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?