Email Security Analysis of evv.ee
Complete verification of evv.ee's SPF, DKIM, DMARC, and MTA-STS records. Find out if this domain is protected against email spoofing.
Last updated: April 15, 2026
SPF
OKv=spf1 ip4:185.31.240.85 ip4:217.146.69.42 include:spf.protection.outlook.com include:neti.ee include:evel.ee ip4:217.146.66.124 ip4:80.235.104.130 ip4:80.235.104.131 ip4:217.146.66.168 ip4:217.159.236.90 -allDKIM
OKSelectors: selector1, selector2DMARC
Warningv=DMARC1; p=quarantine; rua=mailto:dmarcreports@evv.ee; ruf=mailto:dmarcforensic@evv.ee; fo=0; adkim=r; aspf=r; pct=80; rf=afrf; ri=86400MX
OKevv-ee.mail.protection.outlook.comRecommendations
1Upgrade your DMARC policy from p=quarantine to p=reject for full blocking
With p=quarantine, spoofed emails are sent to spam instead of being blocked outright. Some recipients still check spam folders, and sophisticated attacks can be flagged as legitimate by users. p=reject ensures fraudulent emails never reach any folder.
2Add MTA-STS to enforce TLS encryption for incoming emails
Without MTA-STS, an attacker performing a man-in-the-middle attack can downgrade the connection between mail servers to plaintext, intercepting emails in transit. MTA-STS tells sending servers to only deliver via TLS with a valid certificate, preventing downgrade attacks.
Run a live analysis
The results above are updated daily. For an instant check of evv.ee, run a live analysis.
Analyze evv.ee liveGuides to understand these results
SPF Guide
Understand how SPF defines which servers are authorized to send emails for a domain.
DKIM Guide
Discover how DKIM cryptographically signs your emails to guarantee their authenticity.
DMARC Guide
Learn how DMARC orchestrates SPF and DKIM to protect your domain.
MTA-STS Guide
Learn how MTA-STS enforces TLS encryption to protect your emails in transit.
SPF vs DKIM vs DMARC
Compare the three protocols and understand how they work together.