K2MailerAdministrators and DNS managers

Add and verify a sending domain

Generate the DNS records used for sender authentication and tracking.

In the app→Setup → Sending Domains

Domain setup

  1. 1

    Add the base domain without a protocol or path.

  2. 2

    Open its verification details and publish the generated DKIM key, SPF, and tracking records in DNS.

  3. 3

    Wait for DNS propagation, then run Verify DNS entries or the individual verification actions.

  4. 4

    Use Download Keys only when you need a local copy of the generated signing material.

  5. 5

    Select the verified domain when creating the From address and tracking domain for a sending server.

Verification status

The grid shows separate key, SPF, and tracking verification states. A provider can still impose additional sender-verification rules, so also confirm the domain in the selected delivery provider.

Why DNS verification matters

DKIM and SPF records let receiving mail servers confirm that a message genuinely came from your domain and was not altered in transit. Without both records correctly published and verified, a growing share of inbox providers will route your campaigns to spam or reject them outright.

The tracking domain record lets link clicks and opens resolve through your own domain instead of a shared one, which keeps your click and open data accurate and further reinforces sender reputation.

Frequently asked questions

How long does DNS propagation take after adding the records?
It varies by DNS host, typically from a few minutes up to 24-48 hours; if verification fails immediately after publishing the records, wait and re-run Verify DNS entries rather than assuming the records are wrong.
Do I need a separate sending domain for each sending server?
No. A single verified sending domain can be reused as the From address and tracking domain across multiple sending servers.
What should I do if key, SPF, or tracking verification fails?
Recheck that the exact generated record values were published without extra characters or duplicate entries, then re-run verification; if it still fails, confirm the domain separately in your delivery provider, since some providers apply additional sender-verification rules.

Was this guide enough?

Contact support if your screen or result is different.

Contact support