Check whether DMARC is actually protecting your sending domain.
Folderly Lens turns public DMARC posture into an outbound decision: retire domains that poison the estate, fix weak policies, and keep domains with clean external signals.
DMARC mistakes that show up in outbound
No DMARC
The domain has no visible policy for receiver-side authentication alignment.
Monitoring only
p=none records help observe, but they do not enforce a clean sending posture.
No re-scan loop
Policies drift. Lens turns remediation into a before/after check your team can copy.
How to use the DMARC result
If DMARC is missing
Add a policy before scaling outbound. Lens recommends an enforced policy for serious sending estates because mailbox providers read alignment as a trust signal.
If DMARC is p=none
Use monitoring mode only as a transition state. For cold-email infrastructure, leaving domains at p=none creates a visible gap in the trust profile.
If DMARC is enforced
Keep checking SPF, DKIM alignment, MX health, and blacklist status. DMARC enforcement is necessary, but it does not make a damaged domain safe by itself.
DMARC checker FAQ
What does Lens test?
Lens checks whether DMARC exists and whether the policy is missing, monitoring-only, or enforced. It then combines that with other public signals for the verdict.
Is p=none enough?
It is useful for observation, but weak for production outbound. Lens treats p=none as a fix item when the estate needs a trustworthy sending posture.
Does this replace placement tests?
No. DMARC checks structure and authentication posture. Placement tests measure where mail lands after sending.