Visual RFC.
ALL RFCs / RFC 6376
Read the RFC ↗
RFC 6376 / MECHANISM GUIDE

Signing domain and selector

01

The signature identifies a signing domain and a selector for its DNS public key.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 3.5 ↗
RFC 6376 · § 3.5EXAMPLE
3 / 3
Signing domain and selectorThe signature identifies a signing domain and a selector for its DNS public key.Signing domain and selectorDKIM-Signature: d=example.orgs=mail; a=rsa-sha256; b=…mail._domainkey.example.org
03
Publish verification data

The corresponding DNS public key enables receivers to check it.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 6376 original algorithm choicesRFC 8301 §3.1

The update prohibits rsa-sha1 signing and verification and requires rsa-sha256 support in that RSA design; RFC 8463 separately adds Ed25519.

Read the updated RFC section ↗
KEY POINT

d= names the signing domain; s= selects a key below _domainkey.

  • d= names the signing domain; s= selects a key below _domainkey.
  • DKIM proves a signing-domain responsibility assertion, not the author’s personal identity.
  • The signature is visible and does not encrypt the message.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Signing domain and selector
  2. Canonicalization
  3. Body hash and selected headers
  4. DNS key verification
  5. Mutation and trust limits
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗