It creates a public and private key pair plus the DNS record you need to sign email. The public key goes in your DNS, the private key goes in your mail server, and together they let providers verify your messages.
Use 2048-bit. It is the current standard and stronger than 1024-bit. Most providers support it, so choose 2048 unless your DNS host has a length limit that forces a shorter key.
Yes, the DKIM Generator tool is completely free to use.
After adding the keys, use a DKIM checker. Enter your domain and selector, and it confirms the record is live and the key is valid, so you know signing is active before you send.
The private key stays on your mail server and signs outgoing email. The public key goes in your DNS so providers can verify that signature. They are a matched pair, and both are needed for DKIM to work.
Rotating keys periodically, such as once or twice a year, limits the damage if a private key is ever exposed. Generate a new pair, publish the new public key, switch signing to the new private key, then remove the old record.
DKIM, SPF, and DMARC are complementary protocols that together form a robust email authentication framework. DKIM verifies that the email content hasn’t been altered and is sent from an authorized source by using cryptographic signatures. SPF (Sender Policy Framework) specifies which mail servers are allowed to send emails on behalf of your domain. DMARC (Domain-based Message Authentication, Reporting, and Conformance) ties these protocols together by enforcing alignment between SPF and DKIM and allowing domain owners to specify how unauthenticated emails should be handled.
It is better to generate a separate key pair for each domain. Reusing one key across domains weakens your setup and complicates rotation. Generate a fresh pair per domain and selector.
![Custom Tracking Domain: What is it and How to setup? [in 5 min]](https://cdn.prod.website-files.com/6436c3ac9f9fd0594d00b9fc/682f16538b1f34d40ffb7ad7_Duplicate-me-open-graph.avif)

