Check whether DMARC is monitoring-only or actually enforced.
Paste sending domains and Lens evaluates DMARC policy posture in the full scanner context. Missing or weak policy becomes a REHAB item before volume grows.
Why policy level matters
p=none
Useful for monitoring, but it does not ask receivers to quarantine or reject failing mail.
quarantine
A stronger stance that starts protecting the domain while leaving room for controlled rollout.
reject
The strongest published instruction, assuming SPF/DKIM alignment is correctly configured.
How to act on policy gaps
If DMARC is missing
Publish DMARC before scaling and start with reporting so legitimate senders can be inventoried.
If policy is p=none
Move toward enforcement after validating SPF/DKIM alignment for every legitimate sender.
If policy is enforced
Keep monitoring so vendor changes do not break alignment later.
DMARC policy checker FAQ
Is p=none bad?
It is not bad for initial monitoring, but it is weak as a long-term cold-email control.
Should every domain use reject?
Only after legitimate senders are aligned. Moving too fast can break real mail.
Does Lens read aggregate reports?
No. Lens is external-only; it checks the published public policy.