What is email authentication?
Email authentication is how a receiving mail server checks whether the owner of a domain actually authorized a message that uses that domain. You publish rules and keys in DNS (SPF, DKIM, and DMARC), and the receiving server tests each incoming message against them. A pass tells the receiver your domain's use was authorized. It doesn't tell the receiver the message is safe, wanted, or headed for the inbox.
That last point trips people up, so it's worth holding onto as you read the rest.
Why email needs authentication at all
Anyone can type any address into the From line. SMTP, the protocol that moves mail between servers, doesn't check that by design. It makes no effort to validate that the message sender is who they claim to be.
Authentication adds the missing check. Two parties are involved:
- You, the domain owner (and the platforms that send for you), publish DNS records and configure sending systems, for example so they sign with DKIM and use a bounce address on your domain.
- The receiving server runs the checks on every message as it arrives.
Publishing a record doesn't make your mail "authenticated." Each message is evaluated on arrival, and it can still fail if it came from a server you didn't list, wasn't signed, was changed in transit, or isn't aligned with your From domain.
How SPF, DKIM, and DMARC work together
The three mechanisms check different things. They complement each other; they aren't alternatives.
| Mechanism | What it checks | Which domain it looks at |
|---|---|---|
| SPF | Is the connecting server's IP on the domain's list of allowed senders? | The envelope (MAIL FROM) domain, not the visible From |
| DKIM | Does the cryptographic signature verify against the public key in DNS? | The signing domain in d=, which doesn't have to match any visible address |
| DMARC | Did SPF or DKIM pass for a domain that matches the From address people see? | The domain in the From header |
In plain terms: SPF says which servers may send. DKIM proves a domain signed the message and the signed parts weren't changed. DMARC checks that one of those results is aligned with the From domain people see, and it tells receivers what you'd like done when it doesn't.
That matching step is called DMARC alignment: the domain that passed SPF or DKIM has to be the same as, or share an organizational domain with, your From domain. It's the idea that makes DMARC more than "SPF plus DKIM."
Here's what the three records look like for a domain like example.com:
example.com. TXT "v=spf1 include:_spf.mailvendor.example ~all"
selector1._domainkey.example.com TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkq..."
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"
The DMARC record above is in monitoring mode (p=none). It doesn't change how receivers handle your mail; it asks for aggregate reports so you can see who's sending as your domain. DMARC is now defined by the current DMARC standard (DMARCbis), which replaced the older 2015 standard in May 2026. For the definition-level overviews, see What is SPF and What is DMARC on our main site.
Record exists, message passes, message aligns
These are three different statements, and mixing them up is the most common reason people think they're "done":
- The record exists. An email authentication checker can show you that your SPF, DKIM, or DMARC record is published and well formed. Useful, but it says nothing about real messages.
- The message passes. SPF or DKIM actually passed for a specific message from a specific source.
- The message passes and aligns. The domain that passed matches your From domain, so DMARC passes.
A typical gap: you send newsletters through a marketing platform. SPF passes, but for the platform's own bounce domain. DKIM is signed with the platform's domain too. Both pass, neither aligns with example.com, and DMARC fails. Nothing looks broken until you read the reports. Envelope From vs Header From explains the two "From" addresses behind this.
What email authentication helps with
With all three in place, receivers can spot mail that uses your exact domain in the From line without your authorization, and they can build reputation for mail that verifiably comes from you. That's the real value of email spoofing protection at the domain level.
Once your DMARC policy reaches enforcement (p=quarantine or p=reject), receivers that honor it treat unauthenticated use of your domain more strictly. Policies are requests, though. The current standard leaves final handling to each receiver's local policy, and receivers may still deliver, quarantine, or reject a message whatever your policy says.
What it doesn't do
- It isn't encryption. DKIM makes no attempt to encrypt anything. Encrypting the connection between servers is a separate job (TLS). Gmail also requires TLS, separate from SPF, DKIM, and DMARC.
- It isn't an inbox guarantee. A DMARC pass does not guarantee that delivery to the recipient's inbox would be safe or desirable. Authenticated mail is less likely to be rejected or marked as spam — less likely, not never. See Why are my emails going to spam.
- It doesn't cover look-alike domains or display names. DMARC checks the domain in the From header. A message from
example-billing.examplewith the display name "Example Co" is outside its scope; display-name attacks are outside its scope. It doesn't check Reply-To either. - It isn't one-time setup. New vendors, key rotations, and DNS edits break things. That's why domain owners need to keep reading aggregate reports.
Who does the work
Usually more than one team. DNS owners publish the records, platform admins switch on DKIM and custom bounce domains inside each sending tool, and someone has to own the policy decision. Who usually owns SPF, DKIM, and DMARC covers how that split typically looks. The order you do things in matters too: see The right order: SPF, DKIM, DMARC, then BIMI.
BIMI Certifications provides DMARC reporting and visual analysis that shows which sources send as your domain and whether SPF, DKIM, and alignment pass for them. It won't change a provider's filtering, but it tells you whether authentication is the problem.
Free DMARC account
Turn raw DMARC reports into a readable dashboard
Point your rua address to our platform and read the results by sender and source instead of opening XML files.
- Results grouped by sending source
- SPF, DKIM and alignment results per sender
- The original XML reports are still there to download
FAQ
Is email authentication the same as encryption?
No. Authentication checks whether your domain's use was authorized. TLS encrypts the connection between servers. They solve different problems and you'll usually want both.
If I set up SPF, DKIM, and DMARC, will my email always reach the inbox?
No. Receivers also weigh reputation, engagement, content, and complaints. Authentication makes your mail checkable; it doesn't make it wanted.
Do I need all three?
Each covers a different identifier, so yes in practice. DMARC needs at least one of SPF or DKIM to pass and align, and both is better. Bulk senders to Gmail and Yahoo, and high-volume senders to Outlook.com, are required to run SPF and DKIM and to publish a DMARC record that passes with alignment. See Google, Yahoo, and Microsoft sender requirements.
Who checks, and who publishes?
The receiving server checks. You, as the domain owner, publish, along with the platforms that send for you.