Information on RFC 5863 » RFC Editor (original) (raw)
File formats:
Status:
INFORMATIONAL
Authors:
T. Hansen
E. Siegel
P. Hallam-Baker
D. Crocker
Stream:
Source:
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC5863
Discuss this RFC: Send questions or comments to the mailing list ietf-dkim@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 5863
Abstract
DomainKeys Identified Mail (DKIM) allows an organization to claim responsibility for transmitting a message, in a way that can be validated by a recipient. The organization can be the author's, the originating sending site, an intermediary, or one of their agents. A message can contain multiple signatures, from the same or different organizations involved with the message. DKIM defines a domain-level digital signature authentication framework for email, using public key cryptography and using the domain name service as its key server technology. This permits verification of a responsible organization, as well as the integrity of the message content. DKIM will also provide a mechanism that permits potential email signers to publish information about their email signing practices; this will permit email receivers to make additional assessments about messages. DKIM's authentication of email identity can assist in the global control of "spam" and "phishing". This document provides implementation, deployment, operational, and migration considerations for DKIM. This document is not an Internet Standards Track specification; it is published for informational purposes.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.