Security & Configuration

Authenticate Domain Email with SPF, DKIM and DMARC

Configure email-domain authentication records and interpret alignment and reporting without creating conflicting DNS policies.

SPF, DKIM and DMARC help receiving mail systems evaluate whether a message is authorized to use a domain. They improve domain protection and deliverability, but they do not guarantee inbox placement. Configuration must reflect every legitimate sending service.

Publish one SPF policy

SPF identifies hosts authorized to send mail for a domain. A domain should have a single SPF TXT policy; multiple SPF records can cause evaluation errors. Inventory website mail, hosting mail servers, newsletters and third-party providers before publishing the policy. Stay within SPF's DNS lookup limit.

Enable DKIM signing

DKIM adds a cryptographic signature to outgoing messages. The sending system signs selected headers and message content using a private key; receivers retrieve the public key from DNS. Keep private signing keys protected and rotate them according to the provider's process.

Introduce DMARC gradually

DMARC tells receivers how to handle messages that fail alignment checks and can provide aggregate reports. Start with monitoring to discover legitimate senders, then move toward quarantine or reject when the sending inventory is complete. Configure a reporting address that is monitored and able to handle report volume.

Verify alignment

SPF or DKIM passing is not sufficient by itself for DMARC; the authenticated domain must align with the visible From domain under the selected alignment mode. Test messages from every legitimate sending path and inspect authentication results.

Checklist

  • Inventory every legitimate sender.
  • Publish one valid SPF record.
  • Enable DKIM for each sending platform.
  • Start DMARC in monitoring mode and review reports.
  • Increase enforcement only after alignment is verified.
Share this page Help other developers discover this resource.