Email Security Analysis of leinss.com

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

Last updated: April 15, 2026

82B
This domain is protected against spoofing

SPF

OK
v=spf1 a mx include:spf.messagingengine.com include:mxlogin.com -all

DKIM

OK
Selectors: default, fm1, fm2, fm3

DMARC

Warning
v=DMARC1; p=quarantine; rua=mailto:3a591d04a2f5426fbda6a7aedc41511b@dmarc-reports.cloudflare.net,mailto:dmarc@leinss.com; ruf=mailto:dmarc@leinss.com; fo=1
Read the guide

MX

OK
in1-smtp.messagingengine.com, in2-smtp.messagingengine.com

MTA-STS

Missing

No record found

Read the guide

Recommendations

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

  2. 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 leinss.com, run a live analysis.

Analyze leinss.com live

Guides to understand these results