Skip to content
send.io
All posts
Deliverability

SPF, DKIM, and DMARC in plain language

Understand what each authentication mechanism checks, and why setting up a sending domain takes more than one DNS record.

SPF, DKIM, and DMARC in plain language — illustrated Sendio guide
On this page

Three checks with different jobs

SPF identifies servers authorized to send for an envelope-sender domain. DKIM adds a signature that a receiving server can verify using a published public key. DMARC connects authentication to the domain in the visible From address through alignment.

A DMARC pass requires an aligned SPF pass or an aligned DKIM pass. Its policy and reporting settings help domain owners understand and handle messages that fail those checks. These mechanisms complement each other rather than serving as interchangeable badges.

Set up the actual sending path

Use the DNS values supplied by the service sending your mail. Review existing records before editing them: an organization may already use several legitimate senders. A domain change should account for account emails, support messages, billing systems, and any other active mail streams.

Keep a short inventory of who owns the domain, which services send from it, and who can update DNS. This saves time when a provider is replaced or a signing key needs attention. Treat that inventory as operational documentation, not a one-time setup note.

Verify with a real message

Send a test through the same path the application will use and inspect the authentication results in the received message. A green setup screen is useful, but the received headers show what happened on that actual send.

Authentication does not guarantee inbox placement. Gmail publishes additional sender requirements, with stricter rules for bulk senders. Review the current guidance for your audience and sending volume, and monitor outcomes after every configuration change.

Further reading

Google: Email sender guidelines