Email Security Analysis of angledavocat.fr

Complete verification of angledavocat.fr's SPF, DKIM, DMARC, and MTA-STS records. Find out if this domain is protected against email spoofing.

Last updated: April 15, 2026

68C

This domain is vulnerable to spoofing

v=spf1 +ip4:109.234.162.11 +include:spf.protection.outlook.com -all

Selectors: default

Warning

v=DMARC1; p=none;

angledavocat-fr.mail.protection.outlook.com

Missing

No record found

1Change your DMARC policy from p=none to p=reject to block spoofing
With p=none, your DMARC record only monitors — it doesn't actually block spoofed emails. Attackers can still send emails as your domain and they'll be delivered normally. Switching to p=reject instructs receiving servers to drop fraudulent messages before they reach the inbox.
2Add rua=mailto:dmarc@yourdomain to your DMARC to receive reports
Without DMARC reporting (rua=), you have no visibility into who is sending email on behalf of your domain. Aggregate reports let you detect spoofing attempts, identify misconfigured legitimate senders, and confidently tighten your policy over time.
3Add 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.

If you're not sure how to apply these fixes, get in touch and we'll help you out.

Run a live analysis

The results above are updated daily. For an instant check of angledavocat.fr, run a live analysis.

Understand how SPF defines which servers are authorized to send emails for a domain.

Discover how DKIM cryptographically signs your emails to guarantee their authenticity.

Learn how DMARC orchestrates SPF and DKIM to protect your domain.

Learn how MTA-STS enforces TLS encryption to protect your emails in transit.

Compare the three protocols and understand how they work together.