Email Authentication

Email & Security
Technical standards and protocols used to verify that an email genuinely comes from the claimed sender.
← Back to Glossary

What is Email Authentication?

Email authentication is a collection of technical standards and protocols designed to verify that an email message genuinely originates from the domain it claims to be from. These mechanisms help prevent email spoofing, phishing, and spam by allowing receiving mail servers to validate sender identity through DNS records and cryptographic signatures.

The Three Pillars of Email Authentication

SPF (Sender Policy Framework)

Specifies which servers are authorized to send email for your domain.

How SPF Works:

1. Domain publishes SPF record in DNS

2. Receiving server checks sender's IP

3. IP compared against authorized list

4. Pass, fail, or soft-fail result

SPF Record Example:
v=spf1 ip4:192.168.1.0/24 include:_spf.google.com -all

DKIM (DomainKeys Identified Mail)

Cryptographically signs emails to verify integrity and authenticity.

How DKIM Works:

1. Sending server signs message with private key

2. Public key published in DNS

3. Receiving server retrieves public key

4. Signature verified against message

DKIM DNS Record:
selector._domainkey.example.com. TXT "v=DKIM1; k=rsa; p=MIGfMA0..."

DMARC (Domain-based Message Authentication)

Policy layer that tells receivers what to do with authentication failures.

DMARC Record Example:
_dmarc.example.com. TXT "v=DMARC1; p=reject; rua=mailto:reports@example.com"

Authentication Flow

Email Sent → SPF Check → DKIM Check → DMARC Policy

↓ ↓ ↓

Pass/Fail Pass/Fail Deliver/Quarantine/Reject

Authentication Results

ResultSPFDKIMDMARC
passIP authorizedSignature validAligned + passed
failIP not authorizedInvalid signaturePolicy violation
softfailIP questionable--
noneNo recordNo signatureNo policy

Why Authentication Matters

For Senders

For Recipients

Implementation Best Practices

SPF

1. Start with include statements for email providers

2. Add specific IPs for your mail servers

3. Use ~all during testing, -all when confident

4. Keep record under 10 DNS lookups

DKIM

1. Generate 2048-bit keys minimum

2. Rotate keys periodically

3. Use unique selectors per service

4. Monitor signing failures

DMARC

1. Start with p=none for monitoring

2. Review reports to identify issues

3. Gradually move to p=quarantine

4. Implement p=reject when confident

Common Authentication Issues

ProblemCauseSolution
SPF failureWrong IP sendingUpdate SPF record
DKIM failureKey mismatchRegenerate keys
DMARC failureAlignment issuesCheck From/envelope alignment

Email authentication is essential for protecting your domain's reputation and ensuring your emails reach recipients' inboxes.

Put This Knowledge to Work

Use DomScan's API to check domain availability, health, and more.