Email Security Analysis of emilfrey.de

Complete verification of emilfrey.de'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

SPF

OK
v=spf1 mx include:spf.protection.outlook.com include:_spf1.emilfrey.de include:_spf2.emilfrey.de include:_spf3.emilfrey.de include:eu.transmail.net include:inxserver.com include:spf.mailjet.com include:25357506.spf10.hubspotemail.net -all

DKIM

OK
Selectors: s1, s2

DMARC

Warning
v=DMARC1; p=none;
Read the guide

MX

OK
mxb-0027ea02.gslb.pphosted.com, mxa-0027ea02.gslb.pphosted.com

MTA-STS

Missing

No record found

Read the guide

Recommendations

  1. 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.

  2. 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.

  3. 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.

Need help securing your domain?

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

Contact us

Run a live analysis

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

Analyze emilfrey.de live

Guides to understand these results