RFC 5863: DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC5863
- Published
- May 2010
- Authors
- T. Hansen; E. Siegel; P. Hallam-Baker; D. Crocker
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 51
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5585DomainKeys Identified Mail (DKIM) Service OverviewCurrent
July 2009
- RFC 5703Sieve Email Filtering: MIME Part Tests, Iteration, Extraction, Replacement, and EnclosureCurrent
October 2009
- RFC 5755An Internet Attribute Certificate Profile for AuthorizationCurrent
January 2010
- RFC 5322Internet Message FormatUpdated
October 2008
- RFC 3281An Internet Attribute Certificate Profile for AuthorizationObsoleted
May 2002
- RFC 5672RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- UpdateObsoleted
August 2009
- RFC 5617DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)Updated
August 2009
- RFC 6376DomainKeys Identified Mail (DKIM) SignaturesUpdated
September 2011
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?