Email Authentication Check

protonmail.com

This check reviews your domain's email authentication setup to help protect against spoofing and phishing.

All data shown is public and sourced from DNS.

Last checked less than a minute ago

0 out of 110
Good

Domain Health Score

Your domain has basic email authentication in place. Consider strengthening your configuration for better protection.

Top Recommendation

+10

Add aggregate reporting (rua) to receive DMARC reports

DMARC improvement

protonmail.com has a DMARC record but no reporting configured, limiting visibility into authentication results. SPF is published with a soft fail policy (~all), flagging unauthorized senders without blocking them. A few improvements would strengthen protonmail.com's email authentication posture.

0

DMARC Check Results

27 / 50 points

Score Breakdown

DMARC record published
+10
Syntax valid
+5
Quarantine policy
+12 / 20
Aggregate reporting (rua) not configured
0 / 10
Forensic reporting (ruf) not configured (optional)
0 / 5

Configuration issues detected

DMARC record is valid but no reporting email is configured.

Entry:

v=DMARC1; p=quarantine; fo=1; aspf=s; adkim=s;

Without a reporting address (rua), you won't receive aggregate reports from email providers. These reports show who is sending email as your domain and whether authentication passes or fails.

Enable Reports Now

Great! You have a DMARC policy in place. Now start receiving reports in your own monitoring inbox to track email authentication results and identify potential issues.

  • Automated DMARC report processing every 5 minutes
  • Track all sending sources and authentication results
  • Email alerts when your DNS records change
0

BIMI Check (default selector)

5 / 20 points

Score Breakdown

BIMI record published
+5
BIMI record valid
0 / 5
Logo URL accessible and valid SVG
0 / 5
No VMC certificate configured (optional)
0 / 5

Missing required 'l' (logo) URL.

Current BIMI Entry:

v=BIMI1; l=; a=;

Logo URL

Missing logo URL (l=)

Mark Certificate

No certificate URL provided (a=). Optional when using self-asserted logos.

0

SPF Record Check Results

26 / 30 points

Score Breakdown

SPF record published
+10
Syntax valid
+5
Soft fail policy (~all)
+6 / 10
No configuration warnings
+5

SPF record is valid.

protonmail.com TXT SPF Entry:

v=spf1 include:_spf.protonmail.ch ~all

Syntax Check

OK

DNS Lookup Count

2 / 10 max

Root-level mechanisms requiring DNS queries: 1.

Void Lookups

0 / 2 max

Default Policy

~all

Soft fail: Mark emails from unauthorized servers as suspicious but don't reject

All Authorized IP Addresses

Grouped by DNS record source (includes and sub-includes)

include:_spf.protonmail.ch
185.70.40.0/24
185.70.41.0/24
185.70.43.0/24
79.135.106.0/24
79.135.107.0/24
109.224.244.0/24

This record also contains:

include:_spf2.protonmail.ch
include:_spf2.protonmail.ch
85.9.206.169
85.9.210.45
188.165.51.139
57.129.93.249

DNS Lookup Details

1
include:
_spf.protonmail.ch
Valid

SPF record found

Lookup cost: 1
Included by protonmail.com

TXT Record

v=spf1 ip4:185.70.40.0/24 ip4:185.70.41.0/24 ip4:185.70.43.0/24 ip4:79.135.106.0/24 ip4:79.135.107.0/24 ip4:109.224.244.0/24 include:_spf2.protonmail.ch ~all

Processed recursively per RFC 7208

2
include:
_spf2.protonmail.ch
Valid

SPF record found

Lookup cost: 0
Included by _spf.protonmail.ch

TXT Record

v=spf1 ip4:85.9.206.169 ip4:85.9.210.45 ip4:188.165.51.139 ip4:57.129.93.249 ~all

Processed recursively per RFC 7208

0

TLS Security

10 / 10 points

Score Breakdown

TLS-RPT record configured
+5
MTA-STS policy configured
+5

TLS-RPT (Reporting)

TLS-RPT Reporting Configured

Current TLS-RPT Entry:

v=TLSRPTv1; rua=https://reports.proton.me/reports/smtptls

Reporting URIs:

https://reports.proton.me/reports/smtptls

MTA-STS (Policy)

MTA-STS Policy Configured

Current MTA-STS Entry:

v=STSv1; id=190906205100Z;

Policy ID:

190906205100Z

Know when your DNS records change

The check you just ran shows your current configuration. But DNS records change, sometimes without you knowing. A well-meaning IT change, a third-party provider update, or an unauthorized modification can break your email delivery overnight.

Configuration Drift

IT changes that accidentally break authentication

Provider Updates

Third-party services changing their SPF includes

Unauthorized Changes

Attackers modifying records to send as you

DMARCTrust monitors your DNS records continuously. When something changes, you get an email alert with exactly what changed and why it matters. No more surprises when customers complain their emails bounced.

Check Another Domain

Run a free email authentication check (DMARC, SPF, BIMI).

We will generate a shareable URL for your domain.

Try popular examples: google.com, amazon.com, booking.com

Explore other domains

Discover how other organizations configure their email authentication

Popular Domains

Frequently checked

Well-Configured

Reject policy + valid SPF

Same Policy

Also using quarantine

Showing domains checked by our users. All data is from public DNS records.

About This Checker

What we check

We analyze your domain's email authentication: DMARC policy and alignment, SPF record and includes, and BIMI logo and certificate status when present.

Why it matters

Healthy authentication improves delivery and blocks spoofing. Major inbox providers increasingly expect DMARC and aligned SPF/DKIM from senders.

Included features

  • DMARC syntax, policy, and reporting validation
  • SPF record evaluation and include analysis
  • DKIM/SPF alignment interpretation
  • BIMI record and VMC detection
  • Clear setup and remediation guidance

Related Tools

Monitor your email authentication 24/7

This check shows a snapshot. With DMARCTrust, you get continuous monitoring of your DMARC reports and DNS records, with instant alerts when something changes.