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

DNS key verification

04

The receiver resolves the selector under the signing domain and verifies the signature.

Related RFCs and changes

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

DIAGRAM§ 6.1 ↗
RFC 6376 · § 6.1EXAMPLE
3 / 3
DNS key verificationThe receiver resolves the selector under the signing domain and verifies the signature.DNS key verificationVerifierDNSTXT mail._domainkey.example.orgpublic verification keyLocal body hash + signature checkIntegrity for the signing domain’s selected inputs
03
Report the result

A pass establishes signed-input integrity for that signing domain, not delivery safety.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Query mail._domainkey.example.org for the illustrated selector.

  • Query mail._domainkey.example.org for the illustrated selector.
  • Verify the body hash and signature with the published key.
  • Missing keys, altered signed content, or invalid algorithms prevent an ordinary valid signature result.
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

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗