Do indie domains protect their email?

82% of indie product domains publish an SPF record and 64% a DMARC record, but only 27% tell receiving servers to act on it (quarantine or reject). That leaves 73% of indie domains without a policy telling receivers to stop mail forged in their name.

November 2026 edition7,061 indie product domainsMeasured CSV
enforce DMARC
27%
enforce DMARC
n = 7,061
have any DMARC record
64%
have any DMARC record
publish SPF
82%
publish SPF
have SPF and enforced DMARC
25%
have SPF and enforced DMARC

Key findings

  • 27% of indie domains enforce DMARC (quarantine or reject); 12% go as far as p=reject.
  • 64% have a DMARC record at all, and 37% of domains stop at p=none — the setting that only reports spoofing and blocks nothing.
  • 82% publish SPF. Among them, 80% end it with the lenient ~all and 18% with the strict -all.
  • Only 25% have both SPF and an enforced DMARC policy, and 12% have neither record.
  • Microsoft 365 domains are the best protected of the mail providers with at least 30 domains: 45% have both records enforced.
On this page
  1. DMARC: published, and enforced
  2. SPF: who may send
  3. Protected, half protected, open
  4. By mail provider
  5. Are newer domains better protected?
  6. How this was measured
  7. Edition by edition
  8. Questions
  9. Cite and reuse

DMARC: published, and enforced

DMARC tells the servers that receive a mail what to do when it claims to come from a domain but fails the checks: nothing (none), the spam folder (quarantine) or the bin (reject).

DMARC policy of indie product domains
  • No DMARC record36%
  • p=none (monitor only)37%
  • p=quarantine (to spam)15%
  • p=reject (refused)12%

n = 7,061 domains, read from each domain's _dmarc TXT record.

Show the numbers
No DMARC record36%
p=none (monitor only)37%
p=quarantine (to spam)15%
p=reject (refused)12%
Embed this chart
Paste into your page
<iframe src="https://awesomeindie.com/state-of-indie/embed/email-security/0" title="DMARC policy of indie product domains" width="100%" height="326" style="border:0" loading="lazy"></iframe><p>Source: <a href="https://awesomeindie.com/state-of-indie/email-security">State of Indie: Email security</a>, Awesome Indie</p>

p=none is where every domain should start — it asks for reports without risking real mail — but a domain that stays there is as easy to impersonate as one with no record. Moving to quarantine and then reject, once the reports show every real sender passing, is what actually protects a brand from phishing in its name.

SPF: who may send

An SPF record lists the servers allowed to send mail for the domain, and ends with what to do about everyone else.

How indie SPF records end
  • Soft fail (~all)80%
  • Hard fail (-all)18%
  • Neutral (?all)1.6%
  • Delegated or no "all" rule0.4%

Share of the 5,764 domains that publish SPF.

Show the numbers
Soft fail (~all)80%
Hard fail (-all)18%
Neutral (?all)1.6%
Delegated or no "all" rule0.4%
Embed this chart
Paste into your page
<iframe src="https://awesomeindie.com/state-of-indie/embed/email-security/1" title="How indie SPF records end" width="100%" height="326" style="border:0" loading="lazy"></iframe><p>Source: <a href="https://awesomeindie.com/state-of-indie/email-security">State of Indie: Email security</a>, Awesome Indie</p>

~all (soft fail) is the common, cautious choice: receivers are told unlisted servers are suspicious, not forbidden. With an enforced DMARC policy on top, either ending works; without one, SPF on its own decides little.

Which services those SPF records let send mail — Google, Amazon SES, SendGrid and the rest — is in Email providers.

Protected, half protected, open

How well indie domains are protected against spoofing
  • SPF and enforced DMARC25%
  • Enforced DMARC, no SPF2%
  • Records, nothing enforced61%
  • Neither SPF nor DMARC12%
Show the numbers
SPF and enforced DMARC25%
Enforced DMARC, no SPF2%
Records, nothing enforced61%
Neither SPF nor DMARC12%
Embed this chart
Paste into your page
<iframe src="https://awesomeindie.com/state-of-indie/embed/email-security/2" title="How well indie domains are protected against spoofing" width="100%" height="326" style="border:0" loading="lazy"></iframe><p>Source: <a href="https://awesomeindie.com/state-of-indie/email-security">State of Indie: Email security</a>, Awesome Indie</p>

Since February 2024 Gmail and Yahoo require anyone sending them bulk mail to authenticate it with SPF and DKIM and to publish a DMARC record (p=none is enough for that rule). A domain that sends a newsletter or product email without them sees it land in spam or bounce.

By mail provider

Who handles a domain’s mail is a good guess at who set its records up — some providers walk their customers through SPF and DMARC, some do not.

Email authentication by mail provider
Mail handled byDomainsSPFAny DMARCDMARC enforcedBoth
Other or no recognised provider4,07075%52%20%18%
Google Workspace2,06687%85%37%36%
Zoho Mail44798%68%26%26%
Microsoft 36523899%87%46%45%
ImprovMX5995%54%15%15%
Fastmail5898%74%41%40%
Mailgun36100%69%28%28%
iCloud Mail28100%68%32%32%
Forward Email2568%72%48%48%
Migadu22100%100%86%86%
Yandex Mail8100%75%38%38%
Mail provider read from the domain's MX records. "Other or no recognised provider" includes domains that receive no mail at all. Greyed rows have fewer than 30 domains.

Domains on Google Workspace enforce DMARC 37% of the time; domains with no recognised mail provider, many of which receive no mail at all, 20%. A domain that never sends mail can still be spoofed — the usual advice for those is SPF "v=spf1 -all" and DMARC p=reject.

Are newer domains better protected?

SPF and DMARC by when the product was submitted
  • SPF record
  • Any DMARC record
  • DMARC enforced

Every domain checked as it is today, grouped by the half-year its product was submitted. Periods with fewer than 60 domains are left out.

Show the numbers
SeriesH1 2023H2 2023H1 2024H2 2024H1 2025H2 2025H1 2026H2 2026 (so far)
SPF record83%78%82%84%81%82%82%82%
Any DMARC record68%68%75%69%65%65%65%61%
DMARC enforced31%33%26%27%28%30%28%24%
Embed this chart
Paste into your page
<iframe src="https://awesomeindie.com/state-of-indie/embed/email-security/3" title="SPF and DMARC by when the product was submitted" width="100%" height="470" style="border:0" loading="lazy"></iframe><p>Source: <a href="https://awesomeindie.com/state-of-indie/email-security">State of Indie: Email security</a>, Awesome Indie</p>

Every domain is read as it is today, grouped by when its product was submitted to Awesome Indie.

How this was measured

Each month the site check reads the domain's TXT records (for SPF), its `_dmarc` TXT record (for the DMARC policy, the `p=` tag) and its MX records (for the mail provider). n = 7,061: indie product domains at their main domain. Products on a subdomain (`app.example.com`) or on a free host's subdomain (`example.vercel.app`) are left out, because mail policy lives on the main domain.

DKIM is not counted: checking it needs the selector a sender signs with, which DNS does not list. See the methodology for who is in the sample.

Edition by edition

Every edition is frozen the month it is published and never recomputed, so a figure quoted from it stays checkable. Past editions are in the edition menu at the top.

This is the first edition of this chapter. Every month adds a point here, so the lines start with the next edition.

Questions

What percentage of domains have DMARC?

64% of indie product domains publish a DMARC record, and 27% enforce it with p=quarantine or p=reject (n = 7,061).

How many domains use DMARC p=reject?

12% of indie product domains publish DMARC with p=reject, the strictest policy; 15% use p=quarantine.

What is the difference between DMARC none, quarantine and reject?

They tell receiving servers what to do with mail that claims to be from your domain but fails SPF and DKIM: p=none changes nothing and only sends reports, p=quarantine sends it to spam, p=reject refuses it.

Do I need DMARC to send email to Gmail?

Since February 2024 Gmail and Yahoo require bulk senders to publish a DMARC record (p=none is enough for that rule) along with SPF and DKIM. Enforcing it is what stops others from spoofing your domain.

Should SPF end in ~all or -all?

Both work once DMARC is enforced. Among indie domains with SPF, 80% end with ~all (soft fail) and 18% with -all (hard fail).

Cite and reuse

The figures are free to quote, chart and republish under CC BY 4.0: credit State of Indie by Awesome Indie with a link to this page. Every chart above has its own embed code, and the whole table is a CSV.

Citation
Awesome Indie (2026). State of Indie: Email security, November 2026 edition. https://awesomeindie.com/state-of-indie/email-security