RFC6376 — DomainKeys Identified Mail (DKIM) Signatures
RFC6376: DomainKeys Identified Mail (DKIM) Signatures
IETF Request for Comments
| Status | INTERNET STANDARD |
| Publication status | DRAFT STANDARD |
| Published | September 2011 |
| Stream | IETF |
| Obsoletes | RFC4871, RFC5672 |
| Obsoleted by | — |
| Updated by | RFC8301, RFC8463, RFC8553, RFC8616 |
Abstract
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]
Official sources
- Info page: https://www.rfc-editor.org/info/rfc6376
- Full text: https://www.rfc-editor.org/rfc/rfc6376.txt
- HTML: https://www.rfc-editor.org/rfc/rfc6376.html
Abstract and metadata are reproduced from the public RFC index; the full text is linked, not copied.