Read a sample: 1. Why Email Authentication Matters
An employee receives an email that appears to come from [email protected]. It asks for an overdue invoice to be paid using new bank details. The message looks plausible: the company name is familiar, the subject line fits an ongoing transaction, and the sender’s address appears to belong to the expected domain.
None of those details, by itself, proves that Northstar sent the message.
The address displayed in an email is an identity claim. Depending on how a message was sent and what the receiving system checks, an attacker may be able to put someone else’s domain in that claim. Email authentication gives receiving systems ways to examine certain claims against information published by the domain owner. It does not make email deception impossible, but it provides evidence that would otherwise be missing.
Now consider the problem from the other direction. Northstar has recently hired an outside service to send invoices. The service sends a real invoice on Northstar’s behalf, but its messages are not properly authenticated for the domain shown to customers. Some recipients place the messages in junk folders or decline to accept them. The invoice is genuine, yet the evidence presented by the sending system does not match the organization’s intended identity.
These two situations—an impostor claiming a domain and a legitimate sender failing to demonstrate its connection to that domain—are closely related. Both show why email authentication belongs to security operations and service delivery. A useful program reduces opportunities for domain impersonation while helping authorized mail present consistent, verifiable identities.
People often judge an email by the name and address shown in their mail application. Those details are useful, but the email system carries several identities, and the one a person sees is not the whole story.
A message might display [email protected] in its From field, travel through a server operated by an invoice provider, and carry a digital signature associated with a domain belonging to that provider. These details are not necessarily suspicious. Organizations routinely use outside services to send newsletters, account notices, support updates, and other legitimate messages.
The challenge is that the visible address can also be used in a false claim. A malicious sender may create a message that appears to come from a trusted organization and use it to request credentials, redirect a payment, distribute a harmful attachment, or start a deceptive conversation.
This book focuses primarily on domain authentication: checking claims associated with a domain such as northstar.example. That is narrower than proving the identity or intentions of a person. Even when a message authenticates for a domain, authentication alone does not establish that the named employee wrote it, that the employee’s account is uncompromised, or that the request in the message is appropriate.
It is also important to distinguish exact-domain impersonation from a look-alike domain. An attacker who sends from northstar-support.example instead of northstar.example is making a different domain claim. That look-alike domain might be properly authenticated for itself. Authentication can help a receiver evaluate the domain that appears in a message; it does not automatically decide whether a similar-looking domain is trustworthy.
Email authentication involves at least two operational perspectives: the organization whose domain is used to send mail, and the system receiving that mail.
The sending organization identifies its legitimate mail sources and arranges the necessary configuration. That work may involve its own administrators, an email platform, application owners, and outside providers. The organization also publishes authentication-related information in the Domain Name System, or DNS, and keeps that information current as its services change.
The receiving mail system accepts or declines connections and messages according to its own configuration. It can look up published DNS information, evaluate authentication evidence, and combine the results with other signals when deciding what to do. A receiver may deliver a message to an inbox, place it in a junk folder, decline it, or apply another local action.
These roles are distinct. A sending organization can publish a policy and configure its systems carefully, but it does not control every recipient’s filtering decisions. A receiving system can evaluate a message, but it may not know every business relationship behind it. Good troubleshooting starts by asking which side controls the setting being examined.
For example, Northstar can work with its invoice provider to configure an appropriate sending identity. It cannot force a customer’s mail system to put every authenticated invoice in the inbox. If a customer does not receive an invoice, the investigation may require information from both sides: what Northstar’s service sent, what authentication evidence accompanied it, and what the recipient’s system reported.
The core technologies in this book are SPF, DKIM, and DMARC. They complement one another, but they do not answer the same question.
Sender Policy Framework (SPF) allows a domain to publish rules that receiving systems can use to evaluate whether a sending source is authorized for an identity used during mail transport. In practical terms, a receiver checks the source of the connection against the applicable SPF policy. The identity checked by SPF is not necessarily the address a person sees in the From field.
DomainKeys Identified Mail (DKIM) uses a digital signature. A sending system signs selected parts of a message, and a receiving system can use a public key published in DNS to verify that signature. A valid signature provides evidence that the signed material has not changed in a way that breaks verification since it was…