DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 51
- 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.
- Publication Date
- 2010-05-01
- Status Note
- Informational
- DOI
10.17487/RFC5863- Link
- https://doi.org/10.17487/RFC5863
- Author(s)
- Tony HansenEllen SiegelPhillip Hallam-BakerDave Crocker
- Keyword(s)
Latest version of IETF RFC 5863
Document Versions — IETF RFC 5863
-
▶ IETF RFC 5863 (2010-05-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 4871 [Superseded*]
- IETF RFC 5322 [Active, Amended*]
- IETF RFC 5451 [Superseded*]
- IETF RFC 5585 [Active*]
- IETF RFC 5617 [Active*]
- IETF RFC 5672 [Superseded*]
Bibliographic Reference(s)
- IETF RFC 4034 [Active*]
- IETF RFC 4870 [Superseded*]
- IETF RFC 5155 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5863.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5863, DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations. Available at https://doi.org/10.17487/RFC5863
Snippet:
IETF RFC 5863, DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations. Available at https://doi.org/10.17487/RFC5863
HTML (ISO 690 compliant)
Preview:
IETF RFC 5863, DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations. Available at https://doi.org/10.17487/RFC5863
Snippet:
<span class="citation"><cite>IETF RFC 5863</cite>, DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations. Available at <a href="https://doi.org/10.17487/RFC5863" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5863</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5863, DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations
doi: 10.17487/RFC5863
url: https://doi.org/10.17487/RFC5863
doi: 10.17487/RFC5863
url: https://doi.org/10.17487/RFC5863
Snippet:
<li> <cite id="bib-rfc5863">IETF RFC 5863</cite>, DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations <span class="doi">10.17487/RFC5863</span> </li>
Referenced By
- IETF RFC 6376 [Active*]
- IETF RFC 6377 [Active*]
- IETF RFC 6530 [Active*]
- IETF RFC 7489 [Superseded*]