DMARC 1018 min read · Updated Jun 2026

Multiple DKIM signatures on one email

A single email can carry more than one DKIM signature, and often should. Here is why emails get signed twice, what it means for DMARC, and how to read multiple signatures in ClearDKIM.

DKIM was designed for more than one signature

DKIM (RFC 6376) places each signature in its own DKIM-Signature header. A message may carry several of these headers, each created by a different signer, with different selectors, domains, or signing algorithms. A verifier evaluates every signature independently. The message is considered DKIM-authenticated if at least one signature validates.

This is by design. Nothing about DKIM requires a one-signature-per-message rule, and the standard explicitly anticipates multiple signatures coexisting on the same message.

Why an email ends up with two signatures

Third-party sending platforms

When you send through a service like SendGrid, Mailchimp or Amazon SES, the platform signs with its own shared domain (for example sendgrid.net) and also adds a signature using a key delegated to your domain. Two signatures, two domains, but only the one aligned with your From domain counts for DMARC. Full walkthrough

Key rotation overlap

During rotation a sender publishes the new key alongside the old one. In most setups each message is still signed once (with the active selector) and the old public key simply stays in DNS so mail already queued, in transit, or cached can keep validating. Some senders briefly dual-sign with both selectors during the switch, so you may see two published keys even though a given message usually carries one signature.

Algorithm migration

Senders adopting Ed25519 often dual-sign with RSA and Ed25519 (a=ed25519-sha256 and a=rsa-sha256). Verifiers that do not yet support Ed25519 fall back to the RSA signature, so deliverability is preserved throughout the transition. Full walkthrough

Forwarding and mailing lists

A mailing list or forwarder may add its own signature on top of the original sender’s. The original signature often breaks when the list modifies the body or subject. But the list’s own signature, combined with ARC, can still establish a trusted chain. Full walkthrough

What multiple signatures mean for DMARC

DMARC does not care how many DKIM signatures a message carries. It asks one question: does any valid signature have a signing domain (the d= tag) that aligns with the From header domain? If yes, DKIM passes for DMARC purposes.

This is why a message can show a valid signature in raw headers yet still fail DMARC: the signature that validated belonged to the platform’s domain, not yours. The fix is alignment, not adding more signatures.

Signature (d=)Valid?DMARC aligned?
sendgrid.netPassNo
yourdomain.comPassYes

Both signatures are valid, but only the aligned one satisfies DMARC. A single aligned pass is enough.

What it looks like in the headers

Here is an email that genuinely carries two signatures: one keyed to the sending platform’s domain and one to the From domain. Both validate. The verifier records a separate dkim= result for each.

From: billing@xmpl.example
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=xmpl.example; s=s1; t=1719662400;
        h=from:to:subject:date; bh=2jUSOH9NhtVG…; b=g3Lp9c…
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=amazonses.com; s=224i4yxa5…; t=1719662400;
        h=from:to:subject:date; bh=2jUSOH9NhtVG…; b=Qk7vR2…
Authentication-Results: mx.example.net;
        dkim=pass header.d=xmpl.example header.s=s1;
        dkim=pass header.d=amazonses.com header.s=224i4yxa5…;
        dmarc=pass header.from=xmpl.example (p=reject)

Both signatures pass, but only d=xmpl.example aligns with the From domain. That is the one carrying DMARC. The amazonses.com signature is valid but irrelevant to the DMARC result.

Is more than one signature a problem?

No. Multiple signatures are normal and frequently beneficial. They add redundancy across selectors, algorithms and signers. There are only two things to watch:

  • At least one must align. If every signature on a message belongs to a third-party domain, DKIM will not pass DMARC. You need an aligned key delegated to your domain.
  • Broken signatures are noise, not failures. A signature that fails to validate (often the original after forwarding) does not cause DMARC to fail as long as another aligned signature passes. ClearDKIM flags broken signatures so you can tell genuine failures from harmless ones.

How ClearDKIM presents multiple signatures

For every message sample in your reports, ClearDKIM lists each DKIM-Signature separately, showing its selector, signing domain, algorithm, validation result, and whether it aligns with the From domain. The aligned, passing signature is highlighted so you can see at a glance which one is carrying DMARC, and which are merely along for the ride.

Was this guide helpful?