All guides

SPF, DKIM and DMARC before your first customer email

Understand the different roles of email DNS records and prepare a safe domain-authentication checklist.

Keep receiving and sending separate

MX records direct incoming email. Changing them is not a routine step for every outbound API integration. Confirm whether you are setting up a business inbox, sending application messages, or both, then apply the records that setup requires.

Review existing SPF before adding a sender

SPF describes which servers may send for a domain. If your domain already uses an email provider, review its existing configuration before adding another service. Do not simply add a second SPF policy. Ask your DNS administrator to reconcile the providers' instructions so existing mail keeps working.

Publish DKIM exactly as supplied

DKIM attaches a signature to outgoing messages that a receiver can check against a DNS key. Copy the names and values shown in your account without changing them. DNS interfaces may append the domain automatically; verify the final hostname and then run the platform's verification check.

Roll out DMARC with visibility

DMARC checks alignment with the visible From domain and tells receivers how to handle failures. Review legitimate senders and available reports before enforcing a restrictive policy. Authentication helps receivers evaluate messages but does not guarantee inbox placement. Test actual messages after any DNS change.

Continue learning