Skip to main content
You send from domains you own and verify. Verification proves you control the domain and lets receiving servers authenticate your mail, which protects deliverability.

Verifying a domain

1

Add the domain

Add your sending domain (for example mail.yourcompany.com) in the dashboard.
2

Publish the DNS records

mailkube shows you the exact records to add at your DNS provider. Copy each Name/Host and Value exactly as displayed:
  • DKIM (TXT) is a key pair mailkube generates automatically; you publish the public key so receivers can verify your signatures.
  • DMARC (TXT) tells receivers how to handle mail that fails authentication.
  • SPF (TXT) and a bounce-routing MX are both published on a dedicated mkube-send. subdomain that mailkube provides. This subdomain is the return path your mail is actually sent from. SPF is checked there, and bounce notifications come back there. You do not add an SPF record on your main domain.
3

Wait for verification

Once the records resolve, the domain becomes active and you can send from it. When onboarding asks you to create an SMTP credential first, creating that first credential is what completes activation.
DKIM key pairs are generated for you; you never handle the private key. You only publish the public record mailkube shows you.

Domain lifecycle

A domain moves through these states: A domain also carries an onboarding step, reported as onboarding_state on the domain.status webhook: created, setup_in_progress, credentials_required, production, or retired.

Tracking settings

Four per-domain settings decide whether opens and clicks are recorded, and what each recorded event carries. All four are off by default and all four are on the domain’s settings page. The first two decide whether an event happens. The last two decide what it contains and do nothing on their own: with both tracking toggles off, no event is generated and there is nothing to add data to.
Mail clients that prefetch images, and privacy features such as Apple Mail Privacy Protection, inflate open counts. Enable open tracking deliberately, and treat opens as approximate.
Recording a recipient’s IP address or device can require that recipient’s consent, depending on where they are. You are the controller of that decision and responsible for having any permission the law requires; mailkube records the fields on your instruction and uses them for nothing of its own. See Recipient connection data for the payload shape and how absent keys behave.
  • Webhooks documents the events tracking produces and their payloads.
  • Dedicated IP covers sending active domains over dedicated addresses.
  • Quickstart walks through creating a key and sending once your domain is active.