DKIM
DomainKeys Identified Mail — a standard that cryptographically signs outgoing email so receivers can verify it really came from the sending domain and wasn't altered.
DKIM, or DomainKeys Identified Mail, attaches a cryptographic signature to outgoing email. The receiving server looks up the sender domain's public key in DNS and verifies the signature, confirming the message genuinely came from that domain and wasn't tampered with in transit.
It's one of the three pillars of email authentication — alongside SPF and DMARC — and a big part of why a message lands in the inbox instead of spam.
Why it matters for deliverability
Mailbox providers weigh authentication heavily when deciding where to put a message. Mail that passes DKIM and SPF from a reputable domain is far more likely to reach the inbox; unauthenticated mail is treated as suspect.
For agents sending real email, correct DKIM is the difference between being read and being filtered.
How Mailgent handles it
Mailgent sends from verified senders with DKIM and SPF configured correctly, so agents don't have to manage DNS or signing keys. The agent just sends; the platform ensures the message is authenticated.
FAQ
Does DKIM encrypt the email?
No. It signs the message to prove origin and integrity; it doesn't encrypt the contents.
Do I need to set up DKIM myself?
No. Mailgent sends from verified senders with DKIM already configured.
Give your agent an inbox.
A real email address, a vault, 2FA, and an identity in one API call.