
Why DMARC p=none is the easiest security conversation to open
The short answer
A DMARC record set to p=none is monitoring mode: receiving servers are told to deliver mail that fails authentication anyway, so anyone can still send email as the domain. You can prove it from public DNS and the fix is small, which makes it an easy first security conversation.
On this page
Most security conversations with a new prospect start with you asking for something: time, access, a network scan, a questionnaire. A DMARC record set to p=none lets you start the other way round. You already know something specific about their business, you can prove it from public DNS, and the fix is small enough to say yes to.
What p=none actually means
DMARC tells receiving mail servers what to do with email that claims to come from a domain but fails authentication. It has three policies:
| Policy | What receiving servers do with mail that fails |
|---|---|
p=none |
Deliver it anyway and send the domain owner a report. |
p=quarantine |
Send it to spam. |
p=reject |
Refuse it. |
p=none is monitoring mode. It was designed as the first step of a rollout: publish it, read the reports for a few weeks, fix the senders that fail, then move to quarantine and reject. In practice, many companies publish p=none, often because a mailbox provider or an insurer asked them to have "a DMARC record", and never take the next step. Nobody reads the reports. Anyone can still send email as their domain, and receiving servers are told to let it through.
That is the gap. It is not a theory about their network. It is a public record anyone can look up in seconds.
Why it opens doors
It is specific. "Your domain's DMARC policy is set to none, so mail spoofing your domain is still delivered" is a sentence about their company, not a category of risk. Specific findings get replies; generic warnings get deleted.
It is verifiable. The prospect, or their current IT person, can check it in a minute. You are not asking them to trust you, you are pointing at something they can see.
It shows they already care. Someone at the company published the record. They took the first step, so you are not selling the idea of email security from scratch. You are offering to finish a job they started.
It is a contained project. Moving from p=none to enforcement means inventorying every service that sends mail as the domain (the CRM, the billing system, the website forms, the newsletter tool), making sure each one passes SPF or DKIM in alignment, and then tightening the policy in stages. It is real work with a clear end, which makes it a good first engagement.
It has outside pressure behind it. Since 2024, Google and Yahoo require bulk senders to publish DMARC, and more providers are following. Insurers increasingly ask about email authentication at renewal. You are not inventing urgency.
How to raise it
Keep the first message short and about them:
Subject: Mail can still be sent as northwind-dental.com
Hi Emma, I noticed your domain publishes a DMARC record set to monitoring only (p=none). That means email pretending to come from your practice is still delivered to patients and suppliers. Moving to enforcement is usually a one to two week project once every sending service is accounted for. Happy to show you what we found, no strings attached.
A few things make this work:
- Name the record, not the fear. Say what is configured and what it means. Skip the breach statistics.
- Show the scope. A rough timeline tells them this is a project, not a retainer they did not ask for.
- Offer the evidence. A short report with the actual DNS records is easy to forward to whoever makes the decision.
What to bring to the first call
- The current DMARC, SPF and DKIM records, copied from DNS.
- A list of the services you can already see sending mail as their domain (MX records and SPF includes are a good start).
- The rollout plan: monitor and fix senders, move to
p=quarantineat a low percentage, thenp=reject. - What happens after: ongoing report monitoring is where a one-off fix becomes a monthly service.
Finding these at scale
Checking one domain by hand takes a minute. Checking every company in your service area that fits your ideal client profile does not. This is the kind of work 0gaps agents do every week: scan the companies that match your MSP, find gaps like p=none that map to a service you already sell, and hand you the decision-maker with the outreach ready to send.
Whether you use a tool or not, the lesson holds. The best first conversation is about something real, specific and fixable. A half-finished DMARC rollout is all three.

Written by
Vladimir KhoetsyanCTO and co-founder
Vladimir Khoetsyan is CTO and co-founder of 0gaps. He leads 0gaps product and engineering, from the gap scanner and AI agents to PSA and CRM integrations.
Vladimir Khoetsyan on LinkedInKeep reading
- PlaybookHow to win a business that already has an IT provider (without trash-talking them)Most good prospects already have IT. Here's how MSPs start the conversation with a gap anyone can check, handle "we already have someone", and stay on the radar.
- OperationsThe 20-minute weekly marketing routine for MSP ownersWhat to review, what to approve and what to ignore each week, so marketing keeps moving without eating your week.
- OutreachLead with the gap: why a real finding beats a generic cold emailCold email fails when it is about you. Outreach built on a specific, verifiable finding about the prospect gets read, forwarded and answered.