All specs
RFC 6376RFCMust KnowBack Office2011

DomainKeys Identified Mail

Email·RFC Editor
WHY YOU NEED THIS

DKIM is required to pass DMARC. Without it, your email won't be trusted by major providers. Set up alongside SPF as part of any serious email configuration.

What It Defines

DKIM adds a cryptographic signature to outgoing email. The sending domain publishes its public key as a DNS TXT record; receiving MTAs verify the DKIM-Signature header to confirm message integrity.

Canonical (Normative)

Convenient (Practical)

dkimemaildeliverabilitycryptodns
Standards Body
RFC Editor

The canonical publication point for finalized RFCs. If a protocol is standardized as an RFC, the RFC Editor text is the normative final reference. Published by the IETF, IRTF, IAB, and independent stream.

Visit

Related Specs

RFC 7208RFCMust Know

SPF

Without a correct SPF record, your domain's email will fail or be deferred by major receivers (Gmail, Outlook). Set correctly as part of basic email deliverability.

Back OfficeEmail
Details
RFC 7489RFCMust Know

DMARC

DMARC is the final layer of email authentication. Without it, your domain can be spoofed in phishing. Google and Yahoo require DMARC for bulk senders.

Back OfficeEmail
Details
RFC 1035RFCMust Know

DNS Implementation

The record types (A, MX, TXT, CNAME) you configure in every DNS panel live in this spec. Know what you're setting.

Back OfficeProductNaming & Addressing
Details
RFC 5322RFCMust Know

IMF

The structure of every email header you've ever seen is defined here. Essential for email deliverability debugging and understanding DKIM header signing.

Back OfficeEmail
Details