DKIM2 signature options draft-ietf-dkim-dkim2-spec-08
Apply to both cards below. See the DKIM2 specification (-08) for the details.
exploded must not be set on the first signature (i=1). It is added
automatically when a later signature is sent to more than one recipient
(§12.5).
The envelope fields below are ignored. A message whose most recent signature
carries nd= is not a Fully Verified DKIM2 Message, so verifying it
fails and the next signer needs an out-of-band arrangement.
A Signer must not sign a message that already has DKIM2 header fields unless it is a Fully Verified DKIM2 Message. The message is first fully verified against the envelope it was received with, using the DNS source from Settings.
The received message is signed without being verified, as allowed by an
out-of-band arrangement (§12.3).
Chain of custody, mf=/d= and exploded checks
still apply.
Single hop
Signs the message as it is. A new message gets i=1 and a
Message-Instance with m=1; its From header field must be Authentic, so
the From domain, like the MAIL FROM domain, must be the signing domain or a
subdomain of it (§11,
§12.2,
§12.4). A message that
already carries DKIM2 header fields gets the next i=, subject to the
option above.
Forwarder / Reviser
A Forwarder re-signs a received message; a Reviser also changes it and adds a
Message-Instance whose recipe (r=) lets a Verifier recreate the
previous instance (§5,
§12.1). Lines that are not
valid UTF-8 are recorded with u steps. To keep the chain of custody, the
MAIL FROM domain must be an rt= domain of the received signature or a
subdomain of one, and the signing domain must be the MAIL FROM domain or a parent
of it (§7.1,
§12.2). Uses the key,
domain and selector from Settings.
Sign with DKIM1
Verify
Signing identity
mldsa44 is the post-quantum ML-DSA-44 algorithm (FIPS 204) defined for
DKIM2 only
(draft-ietf-dkim-dkim2-spec-08 §3.4).
Its key record uses k=mldsa44 with the raw 1312-byte public key in
p=, split into several strings because a TXT string holds at most
255 bytes. draft-ietf-dkim-dkim2-dns-02 does not define this key type yet.
Keys are generated locally and never transmitted. Demo only: do not reuse a key minted here on a real domain.
DNS source used by Verify
Offline mode answers every lookup from these records only. Names that are not listed are answered as non-existent (NXDOMAIN); the network is never used.