database logo graphic

STD 76

RFC 6376

"DomainKeys Identified Mail (DKIM) Signatures", September 2011

Canonical URL:
http://www.rfc-editor.org/rfc/rfc6376.txt
This document is also available in this non-normative format: PDF.
Status:
INTERNET STANDARD (changed from DRAFT STANDARD June 2013)
Obsoletes:
RFC 4871, RFC 5672
Authors:
D. Crocker, Ed.
T. Hansen, Ed.
M. Kucherawy, Ed.
Stream:
IETF
Source:
dkim (sec)

Cite this RFC: TXT  |  XML

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

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]


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Go to the RFC Editor Homepage.