DMARC policy is set to 'none'
A DMARC record exists on `{found_at}` but its policy is `p=none`, which only asks receivers to report failures — it does not ask them to reject anything.
Why it matters
A DMARC record exists on `{found_at}` but its policy is `p=none`, which only asks receivers to report failures — it does not ask them to reject anything. Forged mail claiming to come from your domain is still delivered. `p=none` is the correct place to start while you confirm your own mail passes, but leaving it there indefinitely provides no protection.
How ShipReady detects it
Email-authentication DNS records (DMARC / SPF). Almost every AI-built SaaS sends transactional email — password resets, magic links, receipts — through Resend, SendGrid or Postmark. Setting that up gets the mail delivered; it does not stop anyone else sending mail that claims to come from the same domain. Without a DMARC policy, a receiving server has no instruction to reject a forgery, so an attacker can send "reset your password" from the product's own domain and the message will land in the inbox looking authentic. This is the only check in the scanner that reads DNS rather than HTTP. It is also the most deterministic: a record either exists or it does not, so there is no heuristic and no false-positive surface. The one place judgement is required is deciding WHICH domain to ask about — see _organizational_domain.
Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.1.0.
How to fix it
This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.
The DMARC record on {domain} uses p=none, which only collects reports and does not ask receivers to reject forged mail. Review your DMARC aggregate reports to confirm every legitimate sender passes SPF or DKIM alignment, then raise the policy to p=quarantine, and to p=reject once you have seen a clean period. Keep the rua= reporting address in place after tightening.Frequently asked questions
- What does "DMARC policy is set to 'none'" mean?
- A DMARC record exists on `{found_at}` but its policy is `p=none`, which only asks receivers to report failures — it does not ask them to reject anything.
- How serious is it?
- ShipReady rates this low. Worth fixing. Small individually, and they accumulate.
- How do I fix it?
- Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.
- Can I check my own site?
- Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check.
Related checks
Does your site have this?
ShipReady checks this and 73 other things across up to ten pages of your site. Free, no signup.
Scan my site