Definition
Email authentication is the practice of publishing records in a domain's DNS, and signing outgoing messages, so that mailbox providers can verify who sent a message. It answers a narrow question, whether this message really comes from the domain it names, and it is one of the first things a provider checks before deciding where a message lands. Google's email sender guidelines document authentication with SPF or DKIM as a requirement for all senders to its mailboxes, and SPF, DKIM and a DMARC policy together for bulk senders, along with alignment of the From domain. The email fundamentals section accordingly places an authenticated sending domain among the foundations of a programme, beside consent and list building, rather than treating it as a technical extra.
SPF, DKIM and DMARC in one paragraph each
SPF (Sender Policy Framework) is a DNS record listing the servers allowed to send mail for a domain. The receiving server compares the server that connected with that list, using the domain in the envelope sender, the technical return address, rather than the one shown to the reader. It commonly fails when a new sending platform is not added to the record.
DKIM (DomainKeys Identified Mail) signs each message with a private key; the matching public key is published in DNS. The receiver checks the signature, which shows the message was not altered on the way and that the signing domain takes responsibility for it. It commonly fails when a platform signs with its own domain rather than the sender's, or a key is rotated without updating DNS.
DMARC (Domain-based Message Authentication, Reporting and Conformance) is a DNS record that builds on the other two. As dmarc.org describes it, it adds alignment and policy: a message passes only if SPF or DKIM passes for a domain that matches the visible From domain, and the published policy tells receivers whether to do nothing, treat failures as suspicious or refuse them. It also asks receivers to send reports showing who is sending as the domain.
Alignment with the visible From domain
Alignment is the part most often misunderstood. A message can pass SPF for the email platform's own domain and pass DKIM with the platform's signature while showing the brand's address in the From line. Each check passes, but neither proves anything about the brand's domain, because neither matches it. DMARC treats that message as failing. The fix is for each sending system to sign with a DKIM key published on the sender's own domain, or to use a return path on that domain, so that at least one passing check lines up with what the reader sees.
In practice: publishing records and reading DMARC reports
Setting up authentication is a DNS task done once per sending domain and repeated for each new platform. The email sending domain setup checklist lists the records, alignment checks and verification steps to tick before a new domain or platform sends its first campaign.
The order dmarc.org recommends is gradual. Publish DMARC with a monitoring-only policy first, read the aggregate reports until every legitimate source is authenticated and aligned, then move to quarantine and finally to reject. Those reports usually reveal forgotten senders: a CRM, a support desk, a billing system or an events tool that mails as the domain without being set up. Each must be added to SPF and signing with DKIM, or a stricter policy will start blocking its mail. Many teams also send marketing from a subdomain, which keeps its reputation apart from the main domain's correspondence and simplifies alignment. The email deliverability guide covers each record's common failures and how the reports feed monitoring.
A tea merchant finds its new platform signing for itself
Kettlecombe Tea Merchants added a second email platform for its subscription reminders while keeping its existing one for newsletters. Within three weeks, newsletter clicks fell by about a third, and test sends to personal accounts were landing in spam. Its DMARC aggregate reports, which it had been receiving but not reading, showed roughly 9,000 messages a week from the new platform passing DKIM for the platform's own domain, not the merchant's, and so failing DMARC. Because the merchant's policy had already been moved to quarantine, receivers were treating that mail as suspicious, and the domain's reputation suffered with it. The team published a DKIM key for its own domain in the new platform's settings and added the platform to SPF. The next fortnight's reports showed the platform passing and aligned, and inbox placement recovered.
Related terms
Authentication is the identity layer of DeliverabilityWhether sent email reaches the inbox rather than spam or rejection, decided by sender reputation.; reputation, list quality and engagement make up the rest, and a sender with perfect records can still land in spam if recipients complain. That is why providers watch Spam Complaint RateShare of delivered emails that recipients marked as spam. beside authentication results. Transactional EmailAn email triggered by a person's own action or account, such as a receipt, password reset or shipping notice, rather than a marketing send. is the stream that most needs protecting: the guide to promotional versus transactional email recommends sending it from its own authenticated subdomain. And Double Opt-InA sign-up process in which the subscriber confirms through a link sent to the address given. works on the other side of the problem, making sure the addresses being mailed asked to be there.
Common confusions
- Authentication does not guarantee the inbox. It proves who sent the mail, not that anyone wanted it. The email programme audit scores authentication as a gate precisely because passing it is necessary, not sufficient.
- Passing SPF and DKIM is not passing DMARC. Without alignment to the From domain, both can pass while DMARC fails.
- A reject policy on day one is not best practice. Enforcing before every sender is aligned blocks legitimate mail.
- It is not a one-time job. Each new tool that sends as the domain needs adding, which is why reports have to be read.
- Small senders benefit too. A monitoring-only DMARC record costs nothing and shows who is sending as the domain. The newsletter growth loop case study puts authentication first for exactly that reason: growth multiplies whatever the sending set-up already is.
