UpdatedINTERNET STANDARDIETF streamSTD76

RFC 6376: DomainKeys Identified Mail (DKIM) Signatures

Still current, but amended. Parts of this document are changed or extended by RFC 8301, RFC 8463, RFC 8553, RFC 8616. Read both.

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC6376
Published
September 2011
Authors
D. Crocker; T. Hansen; M. Kucherawy
Status
INTERNET STANDARD
Stream
IETF
Area
art
Pages
76
Also known as
STD76
Obsoletes:
RFC 4871, RFC 5672

Topics

Standards lineage

This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.

  1. RFC 4870 (2007)
  2. RFC 4871 (2007)
  3. RFC 5672 (2009)
  4. RFC 6376 (2011)

Read the full history of DomainKeys Identified Mail (DKIM) Signatures

Referenced by

4 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/6376-domainkeys-identified-mail-dkim-signatures