DKIM
DomainKeys Identified Mail (DKIM) lets a mail system attach a digital signature that receivers can verify to check the signing domain and the integrity of the message content covered by that signature.
A signature from a domain
The sending system signs message content with a private key. The receiver uses the corresponding public key published in DNS to verify it. The signature identifies its signing domain in the d= field and uses a selector to help the receiver find the key.
DKIM covers selected headers and body content according to the signature’s settings. A pass applies to the covered content. Some headers may be unsigned, and the normalization rules can allow formatting changes without breaking the signature.
The signing domain may belong to a mail service rather than match the visible From domain. DMARC checks that relationship. A valid DKIM signature from an unrelated domain is not enough for a DMARC pass.
Signed does not mean secret or safe
DKIM signs mail; it does not encrypt it. It also does not prove which employee wrote the message or whether its request is legitimate. Mail sent through a compromised account can still carry a valid signature.
A forwarding service can preserve a signature if it leaves the signed content intact. A mailing list or gateway that changes covered content may break it. Investigate the result in context rather than treating every failure as malicious.