Skip to main content

DomainKeys Identified Mail (DKIM) Signatures
RFC 6376 also known as STD 76

Revision differences

Document history

Date By Action
2023-12-12
(System) Imported membership of rfc6376 in std76 via sync to the rfc-index
2023-12-12
(System) No history of STD76 is currently available in the datatracker before this point
2020-01-21
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'DomainKeys Identified Mail (DKIM) permits a person, role, or organization that owns the signing domain to …
Received changes through RFC Editor sync (changed abstract to '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]')
2015-10-14
(System) Notify list changed from dkim-chairs@ietf.org, draft-ietf-dkim-rfc4871bis@ietf.org to (None)
2013-06-04
Amy Vezza New status of Internet Standard approved by the IESG
http://datatracker.ietf.org/doc/status-change-dkim-to-internetstandard/
2011-09-26
Amy Vezza State changed to RFC Published from RFC Ed Queue.
2011-09-26
(System) Posted related IPR disclosure: Yahoo! Inc.'s Statement about IPR related to RFC 6376
2011-09-21
(System) RFC published