DKIM (DomainKeys Identified Mail) adds a tiny cryptographic signature to each message as it leaves your server. Receivers compare that signature with a public key stored in your DNS.
Once configured, the process is automatic. No one reads your traffic—we simply help your systems prove that each message was really written by you and stayed untouched in transit.
How it works
Think of DKIM as sealing wax on a letter—except the stamp is math, not melted wax.
We create a selector such as mail._domainkey and publish the public key in DNS. Only you control it.
Outgoing emails are signed with the matching private key. It happens inside your mail platform—no forwarding, no external gateway.
Providers like Google and Microsoft fetch the public key, validate the signature, and confirm the message stayed intact.
We coordinate with your IT or provider, generate 2048-bit keys, and make sure every mail stream uses the new selector before we remove older keys.
Mail might deliver, but receivers can’t prove the content wasn’t changed en route.
We add selectors, rotate any weak 1024-bit keys, and guide your platform admins through enabling signing.
DKIM runs quietly. We monitor signatures via DMARC reports and remind you when a rotation is due.
Privacy promises
A DKIM signature is a hash of selected headers. Even if someone intercepted it, they could not rebuild the email body. DMARCFlow only helps you publish keys and confirm they validate.
We never need IMAP, SMTP, or mailbox access.
Private keys remain on your server or provider. We never store them—only the public half in DNS.
All work happens in DNS and your sending platform’s admin console.
Emails keep traveling directly from your infrastructure to recipients—nothing is routed through DMARCFlow.
We document selectors, expiry dates, and alert you before a key needs replacing.
Next step
Let us generate selectors, guide the platform changes, and verify everything without ever peeking into your inbox.