RFC 1544: The Content-MD5 Header Field
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1864.
Current version: RFC 1864 — The Content-MD5 Header Field
In plain English — editorial summary, not part of the RFC
This memo defines the use of an optional header field, Content-MD5, which may be used as a message integrity check (MIC), to verify that the decoded data are the same data that were initially sent. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1544
- Published
- November 1993
- Authors
- M. Rose
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 3
- Also known as
- —
- Obsoleted by:
- RFC 1864
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5068Email Submission Operations: Access and Accountability RequirementsUpdated
November 2007
- RFC 5403RPCSEC_GSS Version 2Updated
February 2009
- RFC 5598Internet Mail ArchitectureCurrent
July 2009
- RFC 6376DomainKeys Identified Mail (DKIM) SignaturesUpdated
September 2011
- RFC 6377DomainKeys Identified Mail (DKIM) and Mailing ListsCurrent
September 2011
- RFC 8255Multiple Language Content TypeCurrent
October 2017
- RFC 9078Reaction: Indicating Summary Reaction to a MessageCurrent
August 2021
- RFC 9787Guidance on End-to-End Email SecurityCurrent
August 2025
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?