Provider vs. aligned signatures
When you send through SendGrid, Amazon SES, Mailchimp or any ESP, your mail often carries two DKIM signatures: one keyed to the provider’s domain and one to yours. Only one of them satisfies DMARC, and knowing which is the difference between passing and silently failing.
Why an ESP signs twice
A sending platform signs every message with its own infrastructure key (for example d=sendgrid.net or d=amazonses.com). That signature proves the platform handled the mail. It is useful for the platform’s own reputation, but its domain is not your From domain, so it does not help your DMARC result.
To pass DMARC you also delegate a key to your domain. When you complete "domain authentication" (SendGrid), "Easy DKIM" (SES) or the equivalent, the platform publishes CNAMEs under your domain and starts adding a second signature with d=yourdomain.com. That is the signature DMARC cares about.
DMARC alignment, in one rule
DKIM passes DMARC only if at least one valid signature has a signing domain (d=) that aligns with the From-header domain. Extra valid signatures on other domains are ignored for the DMARC verdict.
The "before": only the provider signs
Before you authenticate your domain, the only DKIM signature is the platform’s. It validates perfectly. DMARC still fails, because nothing aligns with From: xmpl.example:
From: billing@xmpl.example DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sendgrid.net; s=s1; t=1719662400; h=from:to:subject:date; bh=2jUSOH9…; b=g3Lp9c… Authentication-Results: mx.example.net; dkim=pass header.d=sendgrid.net; dmarc=fail header.from=xmpl.example (p=reject)
The signature is valid, but sendgrid.net ≠ xmpl.example, so DKIM is not aligned and DMARC fails.
The "after": both signatures present
Once domain authentication is in place, the message carries both signatures. The provider’s still validates. Now an aligned one does too, and that is the one that carries DMARC:
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=2jUSOH9…; b=Lk2pQ8… DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sendgrid.net; s=s1; t=1719662400; h=from:to:subject:date; bh=2jUSOH9…; b=g3Lp9c… Authentication-Results: mx.example.net; dkim=pass header.d=xmpl.example header.s=s1; dkim=pass header.d=sendgrid.net header.s=s1; dmarc=pass header.from=xmpl.example (p=reject)
| Signature (d=) | Valid? | Aligned? |
|---|---|---|
| xmpl.example | Pass | Yes → carries DMARC |
| sendgrid.net | Pass | No → ignored |
The trap: a valid signature that doesn’t count
This is the single most common DKIM confusion. You inspect a message, see dkim=pass, and assume DMARC is fine. But the signature that passed belonged to the provider, not you. The fix is never "add more signatures". It is to authenticate your domain so an aligned signature exists. ClearDKIM flags exactly this case: a passing signature that is not aligned with your From domain.
- RFC 7489: Domain-based Message Authentication, Reporting and Conformance (DMARC), §3.1 Identifier Alignment.
- RFC 6376: DKIM Signatures, §3.5 (the
d=ands=tags). - SendGrid and Amazon SES sender documentation: domain authentication / Easy DKIM.