DomainKeys Identified Mail (DKIM) Signatures
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 76
- 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]
- Publication Date
- 2011-09-01
- Status Note
- Internet Standard
- DOI
10.17487/RFC6376- Link
- https://doi.org/10.17487/RFC6376
- Author(s)
- Dave CrockerTony HansenMurray Kucherawy
- Keyword(s)
- Email, Architecture, Verification, Media Identity, Integrity, Phishing
Latest version of IETF RFC 6376
Document Versions — IETF RFC 6376
-
▶ IETF RFC 6376 (2011-09-01)THIS DOC [ACTIVE] [LATEST VERSION]
Amended by:
- IETF RFC 8301 [Active*]
- IETF RFC 8463 [Active*]
- IETF RFC 8553 [Active*]
- IETF RFC 8616 [Active*]
Normative Reference(s)
- NIST FIPS 180-3 [Withdrawn]
- "Information Technology - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)", 1997. EXTERNAL
- IETF RFC 1034 [Active*]
- IETF RFC 2045 [Active*]
- IETF RFC 2049 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 3447 [Superseded*]
- IETF RFC 5234 [Active, Amended*]
- IETF RFC 5321 [Active*]
- IETF RFC 5322 [Active, Amended*]
- IETF RFC 5598 [Active*]
- IETF RFC 5890 [Active*]
Bibliographic Reference(s)
- "Remote Timing Attacks are Practical", Proceedings 12th USENIX Security Symposium, 2003. EXTERNAL
- IETF RFC 2047 [Active*]
- IETF RFC 3629 [Active*]
- IETF RFC 3766 [Active*]
- IETF RFC 3833 [Active*]
- IETF RFC 3864 [Active*]
- IETF RFC 4033 [Active*]
- IETF RFC 4409 [Superseded*]
- IETF RFC 4686 [Active*]
- IETF RFC 4732 [Active*]
- IETF RFC 4870 [Superseded*]
- IETF RFC 4871 [Superseded*]
- IETF RFC 4880 [Superseded*]
- IETF RFC 5226 [Superseded*]
- RFC5451 — RFC5451 EXTERNAL
- RFC5585 — RFC5585 EXTERNAL
- IETF RFC 5672 [Superseded*]
- IETF RFC 5751 [Superseded*]
- RFC5863 — RFC5863 EXTERNAL
- RFC6377 — RFC6377 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6376.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 6376, DomainKeys Identified Mail (DKIM) Signatures. Available at https://doi.org/10.17487/RFC6376
Snippet:
IETF RFC 6376, DomainKeys Identified Mail (DKIM) Signatures. Available at https://doi.org/10.17487/RFC6376
HTML (ISO 690 compliant)
Preview:
IETF RFC 6376, DomainKeys Identified Mail (DKIM) Signatures. Available at https://doi.org/10.17487/RFC6376
Snippet:
<span class="citation"><cite>IETF RFC 6376</cite>, DomainKeys Identified Mail (DKIM) Signatures. Available at <a href="https://doi.org/10.17487/RFC6376" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6376</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6376, DomainKeys Identified Mail (DKIM) Signatures
doi: 10.17487/RFC6376
url: https://doi.org/10.17487/RFC6376
doi: 10.17487/RFC6376
url: https://doi.org/10.17487/RFC6376
Snippet:
<li> <cite id="bib-rfc6376">IETF RFC 6376</cite>, DomainKeys Identified Mail (DKIM) Signatures <span class="doi">10.17487/RFC6376</span> </li>
Referenced By
- IETF RFC 6409 [Active*]
- IETF RFC 6698 [Active*]
- IETF RFC 7372 [Active*]
- IETF RFC 7909 [Active*]
- IETF RFC 8301 [Active*]
- IETF RFC 8463 [Active*]
- IETF RFC 8553 [Active*]
- IETF RFC 8616 [Active*]
- IETF RFC 9051 [Active*]
- IETF RFC 9788 [Active*]