metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 4871: DomainKeys Identified Mail (DKIM) Signatures

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6376.

Current document in this lineage: RFC 6376 — DomainKeys Identified Mail (DKIM) Signatures

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

DomainKeys Identified Mail (DKIM) defines a domain-level authentication framework for email using public-key cryptography and key server technology to permit verification of the source and contents of messages by either Mail Transfer Agents (MTAs) or Mail User Agents (MUAs). The ultimate goal of this framework is to permit a signing domain to assert responsibility for a message, thus protecting message signer identity and the integrity of the messages they convey while retaining the functionality of Internet email as it is known today. Protection of email identity may assist in the global control of "spam" and "phishing". [STANDARDS-TRACK]

Document record

Document ID
RFC4871
Published
May 2007
Authors
E. Allman; J. Callas; M. Delany; M. Libbey; J. Fenton; M. Thomas
Status
PROPOSED STANDARD
Stream
IETF
Area
art
Pages
71
Also known as
—
Obsoletes:
RFC 4870
Obsoleted by:
RFC 6376
Updated by:
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

2 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/4871-domainkeys-identified-mail-dkim-signatures