RFC 5585: DomainKeys Identified Mail (DKIM) Service Overview
In plain English — editorial summary, not part of the RFC
This document provides an overview of the DomainKeys Identified Mail (DKIM) service and describes how it can fit into a messaging service. It also describes how DKIM relates to other IETF message signature technologies. It is intended for those who are adopting, developing, or deploying DKIM. DKIM allows an organization to take responsibility for transmitting a message, in a way that can be verified 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, with the domain name service as its key server technology (RFC 4871). This permits verification of a responsible organization, as well as the integrity of the message contents. DKIM also enables 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 memo provides information for the Internet community.
Document record
- Document ID
- RFC5585
- Published
- July 2009
- Authors
- T. Hansen; D. Crocker; P. Hallam-Baker
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5863DomainKeys Identified Mail (DKIM) Development, Deployment, and OperationsCurrent
May 2010
- RFC 5703Sieve Email Filtering: MIME Part Tests, Iteration, Extraction, Replacement, and EnclosureCurrent
October 2009
- RFC 5617DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)Updated
August 2009
- RFC 5672RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- UpdateObsoleted
August 2009
- RFC 4871DomainKeys Identified Mail (DKIM) SignaturesObsoleted
May 2007
- RFC 6376DomainKeys Identified Mail (DKIM) SignaturesUpdated
September 2011
- RFC 6377DomainKeys Identified Mail (DKIM) and Mailing ListsCurrent
September 2011
- RFC 4686Analysis of Threats Motivating DomainKeys Identified Mail (DKIM)Current
September 2006
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?