RedScore.ai
All posts
Email Security

DMARC, SPF, and DKIM explained for founders

DMARC, SPF, and DKIM are the three DNS records that stop email spoofing on your domain. Here is what each one does and how to check them.

2 min read · 2026-06-14 · RedScore Research Team

Quick answer

SPF lists which servers may send mail for your domain. DKIM signs outgoing mail so receivers can verify it. DMARC tells receivers what to do when SPF or DKIM fail. Together they stop most email spoofing. RedScore checks all three from the outside in about 60 seconds.

What are DMARC, SPF, and DKIM?

They are three DNS records that work together to stop email spoofing on your domain. Without them, anyone can send mail that looks like it came from your company.

SPF (Sender Policy Framework) is a DNS TXT record that lists which mail servers are allowed to send email for your domain. When a receiver gets mail claiming to be from you, it checks whether the sending server is on your SPF list.

DKIM (DomainKeys Identified Mail) adds a digital signature to outgoing mail. The receiver looks up your public key in DNS and verifies the signature. If it matches, the mail was not tampered with in transit.

DMARC (Domain-based Message Authentication, Reporting, and Conformance) tells receivers what to do when SPF or DKIM fail. It also sends you reports about mail sent using your domain.

Why should founders care?

Buyers and partners check email auth before they trust your domain. A spoofed invoice or password reset from your domain name can damage trust faster than a weak TLS config.

Most founders set up Google Workspace or a transactional mail provider and assume email auth is handled. Often it is not fully enforced. DMARC sits at p=none forever, or SPF includes every provider under the sun.

Run a quick outside-in check before you send your first customer email or pitch deck.

How do I check my email auth records?

Go to /lookup and enter the domain in your From address. RedScore reads your public SPF, DKIM, and DMARC records and flags gaps.

For detail on each check, see the SPF checker, DKIM checker, and DMARC checker pages.

What does a good setup look like?

  1. SPF lists only your real mail providers. No +all. No stale entries from old services.
  2. DKIM is enabled with your mail provider and the public key is published in DNS.
  3. DMARC starts at p=none while you monitor reports, then moves to p=quarantine or p=reject.

Most mail providers (Google Workspace, Microsoft 365, SendGrid, Postmark) have setup guides for all three. Follow theirs, then verify with a scan.

What should I do if my records are missing or weak?

  1. Enable SPF and DKIM through your mail provider first.
  2. Add a DMARC record at p=none to start collecting reports.
  3. Review reports for a week or two to catch legitimate mail that fails.
  4. Move DMARC to p=quarantine, then p=reject.
  5. Rescan from /lookup to confirm the grade improved.

This is a one-time setup for most startups. The scan takes 60 seconds. Fixing DNS takes longer, but you only do it once.

Frequently asked questions

Do I need all three records?

Yes, for strong protection. SPF and DKIM prove mail is legitimate. DMARC tells receivers what to do when those checks fail.

Which record should I set up first?

SPF and DKIM first, through your mail provider. Then add DMARC starting with p=none for monitoring before moving to quarantine or reject.

Can I check these without DNS access?

You can see whether they exist and whether they look correct from the outside. Fixing them requires DNS changes in your registrar or provider.

Does email auth affect my website security score?

Yes. Email authentication is one category in a RedScore scan. Weak email auth lowers your overall grade.

Run a free outside-in scan on your domain in about 60 seconds.

Scan domain