Results for stclair.org
Analysis performed on April 15, 2026 at 02:50 PM
DKIM
OKSelectors: s1, s2DMARC
Warningv=DMARC1; p=quarantine; rua=mailto:re+c65a9ccabf43@inbound.dmarcdigests.com, mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com; ri=86400; fo=1; pct=100MX
OKmxa-00402c01.gslb.pphosted.com, mxb-00402c01.gslb.pphosted.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.
2Harden your SPF by replacing ~all with -all (hardfail)
With ~all (softfail), unauthorized senders are flagged but emails are usually still delivered. Switching to -all (hardfail) explicitly tells receiving servers to reject emails from unauthorized sources, providing much stronger protection against spoofing.
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.
Badge for your website
Display your email security score on your website.
<a href="https://spoofchecker.online/en/email-security/stclair.org" target="_blank" rel="noopener"><img src="https://spoofchecker.online/api/badge/stclair.org?score=72&grade=B" alt="Email security score for stclair.org" height="28"></a>