RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4871.
Current document in this lineage: RFC 6376 — DomainKeys Identified Mail (DKIM) Signatures
In plain English — editorial summary, not part of the RFC
"DomainKeys" creates a domain-level authentication framework for email by using public key technology and the DNS to prove the provenance and contents of an email. This document defines a framework for digitally signing email on a per-domain basis. The ultimate goal of this framework is to unequivocally prove and protect identity while retaining the semantics of Internet email as it is known today. Proof and protection of email identity may assist in the global control of "spam" and "phishing". This memo defines a Historic Document for the Internet community.
Document record
- Document ID
- RFC4870
- Published
- May 2007
- Authors
- M. Delany
- Status
- HISTORIC
- Stream
- IETF
- Area
- —
- Pages
- 41
- Also known as
- —
- Obsoleted by:
- RFC 4871
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 4870 (2007)
- RFC 4871 (2007)
- RFC 5672 (2009)
- RFC 6376 (2011) ✓
Read the full history of DomainKeys Identified Mail (DKIM) Signatures →
Referenced by
One later RFC formally updates or obsoletes part of this document.
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?