Skip to content

Email Deliverability in Runet: SPF/DKIM/DMARC 2026

TL;DR:

Based on Enterno.io Email Checker Q1 2026 (50K domain sample): SPF configured on 78% of domains, DKIM — 62%, DMARC — only 34% (and only 12% of those on p=reject). Top errors: SPF with +all (8%), DKIM without key rotation (>2 years — 45%), DMARC at p=none as permanent (94% of those who set it).

Methodology

Analysis via Enterno.io Email Checker for Q1 2026: 50,000 domains (.ru, .рф + RU-hosted). Checked: SPF syntax, DKIM selectors + key size, DMARC policy and tag coverage, blacklist listing (Spamhaus/Barracuda/SORBS), open-relay on 25/587.

Protocol coverage

ProtocolCoverageCorrect setup
SPF78%92% without +all
DKIM62%55% with key ≥ 2048 bit
DMARC34%12% on p=reject

DMARC remains the most underused — without it SPF+DKIM do not fully protect from spoofing. And p=none is "reports only", not protection.

Top-5 setup errors

  1. SPF with +all (8%) — allows sending from ANY server. Equivalent to no SPF. Fix: ~all or -all.
  2. DKIM keys older than 2 years without rotation (45%) — critical vulnerability on private-key leak.
  3. DMARC p=none forever (94% of 34%) — monitoring without protection. Goal — p=reject.
  4. Missing DMARC rua/ruf (67%) — no way to track abuse.
  5. Open relay on 25/587 (2%) — rare but present in legacy systems. Consequence: blacklist listing within 24 hours.

Blacklist status

From 50K domains: 4.2% listed in Spamhaus SBL/XBL, 2.1% in Barracuda BRBL, 1.3% in SORBS. Most common listing reason — compromised hosting account (60%), followed by legitimate marketing emails from domains without SPF (25%).

Check a domain against blacklists online — /en/email-check.

Recommendations

  1. Configure SPF with ~all (not +all).
  2. DKIM — 2048-bit keys, rotate yearly.
  3. DMARC — start with p=none + rua, then after 4 weeks → p=quarantine, another 4 weeks → p=reject.
  4. Monitor blacklist status daily (Pro+ plan).
  5. Follow the how-to-setup-dmarc guide.
SPF + DKIM + DMARCFull email protection triad check
Antispam StatusBlacklist check
MX ConfigurationCorrect mail server configuration
Email ScoreEmail deliverability score

Why teams trust us

MX
MX record check
SMTP
SMTP verification
SPF
SPF + DKIM + DMARC
Free
no signup

How it works

1

Enter email address

2

Check MX + SMTP

3

Get validity verdict

Why check email settings?

Proper SPF, DKIM, and DMARC configuration directly impacts email deliverability. Without these records, your emails land in spam or are rejected before delivery.

SPF Check

SPF record correctness: syntax, allowed server list, fail mechanism.

DKIM Analysis

Presence and validity of DKIM signature for the specified selector.

DMARC Policy

DMARC record parsing: policy, rua/ruf reports, SPF and DKIM alignment.

Email Score

Numerical delivery readiness score with improvement recommendations.

Who uses this

Email marketers

mailing list verification

Developers

registration validation

Sales

CRM contact check

Sysadmins

mail delivery troubleshooting

Common Mistakes

Missing SPF recordWithout SPF, emails from your domain are treated as potential spoofing.
SPF with ?all instead of -all?all means "neutral" — that's not protection. Use -all.
DMARC without policyp=none only collects reports. Move to p=quarantine or p=reject.
Not reading DMARC reportsDMARC generates reports on all emails. Analyze them to find unauthorized sending.

Best Practices

Deploy SPF → DKIM → DMARC sequentiallySPF first, then DKIM, then DMARC. Each step must work before moving to the next.
Start DMARC with p=noneCollect reports for 2–4 weeks, ensure all legitimate mail passes, then tighten policy.
Add rua report addressrua=mailto:dmarc@yourdomain.com — receive weekly aggregate reports.
Check after changing providerWhen changing hosting or ESP, always update SPF and DKIM keys.

Get more with a free account

Email check history and API keys for service integration.

Sign up free

Learn more

Frequently Asked Questions

Is data current?

Q1 2026. Updated quarterly.

Can I cite this?

Yes, with attribution to Enterno.io.