Glossary · Authentication
What is email authentication?
The short answer
Email authentication is the set of checks a mail server runs to confirm that an email really comes from the domain it claims to come from. The three main checks are SPF, DKIM and DMARC. Email that passes is trusted more. Email that fails is often sent to spam or blocked.
Also called: email authentication methods, SPF, DKIM and DMARC, sender authentication
By Ali Tahir Sajjad · Updated · 3 min read
Email authentication: what to remember
- Email authentication proves an email is really from you and not from someone pretending to be you.
- It has three parts: SPF (who may send), DKIM (a signature on the email) and DMARC (what to do if the checks fail).
- All three are set up with records in your domain's DNS. Nothing changes in how you write or send email.
- Without email authentication, cold email goes to spam, and Gmail and Yahoo may refuse it.
What does email authentication mean?
Email authentication means proving that an email is really from who it says it is from.
Email was invented without any ID checks. Anyone can write ceo@yourcompany.com in the From line and press send. Email authentication was added later to close that hole.
Think of airport security. Your ticket has a name on it, but the staff do not just believe the ticket. They check your passport too. Email authentication is the passport check for email: the receiving mail server does not just believe the From line. It checks.
The three parts of email authentication
Email authentication is made of three checks. Each one does a different job.
| Check | The question it answers | Simple picture |
|---|---|---|
| SPF | Was this email sent from a server the domain allows? | A guest list at the door |
| DKIM | Is the email genuine, and unchanged since it was sent? | A seal on the letter |
| DMARC | Do the checks match the From address, and what if they fail? | Instructions for the doorman |
All three live in the same place: your domain’s DNS, the public list of settings for your domain. Only the owner of a domain can change its DNS, which is exactly why these records can be trusted.
How email authentication works, step by step
Say you send an email from maria@example.com.
- Your mail server signs the email with DKIM and sends it.
- The receiving server sees which server delivered the email. It looks up the SPF record of
example.comto check that server is on the list. - It reads the DKIM signature, fetches your public key from DNS and checks the signature.
- It runs the DMARC check: did SPF or DKIM pass, using the same domain as the From address?
- It writes all three results into the email and decides where the email goes: inbox, spam, or nowhere.
This takes a fraction of a second, and it happens to every email you send.
An email authentication example
You can see the result of email authentication on any email you receive. It is written in the email header, in a line like this:
Authentication-Results: mx.example.org;
spf=pass dkim=pass dmarc=pass
Three passes mean the email is fully authenticated. If you see fail, softfail, none or permerror next to any of them, that part of your email authentication needs attention.
Why email authentication matters for cold email
Inbox providers are careful with email from strangers, and cold email is exactly that. Before Gmail or Outlook looks at what you wrote, it looks at whether you are who you say you are.
- With email authentication, your email gets a fair chance. The provider can connect it to your domain and judge it on your own record.
- Without it, your email looks like it could be forged. It is filtered, and in some cases refused before anyone sees it.
Email authentication is the first layer of your cold email infrastructure. Domains, inboxes and warmup all come after it, and none of them help if this layer is missing.
Getting three records right on one domain is easy. Getting them right on twenty domains, with no typos, is where most people slip. PureMail’s team writes all of them for you on every domain when it sets up your Google Workspace inboxes or Microsoft 365 inboxes.
How to set up email authentication
- SPF: add one TXT record that lists who may send for your domain.
- DKIM: create a key in your email provider’s admin panel, add it to DNS and switch signing on.
- DMARC: add one TXT record named
_dmarc, starting with the policyp=none. - Test: send yourself an email and check for three passes.
Common email authentication mistakes
- Two SPF records on one domain. A domain can only have one. Two cause an SPF permerror, which counts as a failure.
- DKIM created but not switched on. The record is in DNS, but nothing is being signed.
- Stopping at SPF and DKIM. Without DMARC, receivers do not know what you want done with failures.
- Forgetting the extra domains. Every sending domain needs its own three records.
- Testing only once. Check again after any DNS change, because one edit can break a record that used to pass.