Email Security Analysis of stclair.org

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

Last updated: April 15, 2026

72B
This domain is protected against spoofing

SPF

Warning
v=spf1 include:spf-00402c01.pphosted.com include:spf.elasticemail.com ~all
Read the guide

DKIM

OK
Selectors: s1, s2

DMARC

Warning
v=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=100
Read the guide

MX

OK
mxa-00402c01.gslb.pphosted.com, mxb-00402c01.gslb.pphosted.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. 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.

  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.

Run a live analysis

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

Analyze stclair.org live

Guides to understand these results