Search RFCs

RFC Editor

File formats:

Status:

INTERNET STANDARD (changed from DRAFT STANDARD)

Obsoletes:

RFC 4871,RFC 5672

Updated by:

RFC 8301,RFC 8463,RFC 8553,RFC 8616

Authors:

D. Crocker, Ed.
T. Hansen, Ed.
M. Kucherawy, Ed.

Stream:

IETF

Source:

dkim (sec)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6376

Discuss this RFC: Send questions or comments to the mailing listietf-dkim@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6376

Abstract

DomainKeys Identified Mail (DKIM) permits a person, role, ororganization that owns the signing domain to claim someresponsibility for a message by associating the domain with themessage. This can be an author's organization, an operational relay,or one of their agents. DKIM separates the question of the identityof the Signer of the message from the purported author of themessage. Assertion of responsibility is validated through acryptographic signature and by querying the Signer's domain directlyto retrieve the appropriate public key. Message transit from authorto recipient is through relays that typically make no substantivechange to the message content and thus preserve the DKIM signature.

This memo obsoletes RFC 4871 and RFC 5672. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.