DMARC is public and operationally meaningful, making it a useful qualification clue for MSPs that sell email-authentication services.

DMARC offers a visible starting point

DMARC policy is published at _dmarc and can be queried without entering a company's environment. It can help an MSP identify a plausible discussion about reporting, sender alignment or enforcement strategy. It cannot show whether the organization has an internal project or whether mail protection is generally effective.

dig +short TXT _dmarc.example.com

Signal 1: no valid DMARC record observed

After a reliable lookup and syntax check, no valid record can make implementation a reasonable discovery topic. It is still necessary to understand whether the domain is used for email. A domain that intentionally never sends email may have a different risk and priority profile.

Signal 2: p=none

A monitoring-only policy is not inherently bad. It is often a deliberate stage of a DMARC rollout. Commercially, it can indicate that reporting, sender inventory, alignment or enforcement work may be relevant.

A more useful discovery question is: "Who owns your aggregate reporting and the roadmap toward enforcement?" Claiming that every domain on p=none is insecure is an overreach.

Signal 3: enforcement without obvious reporting context

p=quarantine or p=reject indicates a published receiver policy. DNS does not reveal whether reports are actively reviewed or all legitimate senders align. Operations and monitoring can remain a discussion even when enforcement is already configured.

Signal 4: visible reporting providers

The rua reporting destinations may indicate an external DMARC management vendor. That changes the possible sales motion from initial deployment to monitoring, optimization, consolidation or migration. A reporting address is not proof of the contract owner or service quality.

Segment the opportunity, do not generate one generic red flag

Observed posture Possible discovery angle
No valid DMARC observed Initial domain-authentication assessment
p=none Reporting and enforcement roadmap
p=quarantine Operational tuning and path to reject
p=reject Ongoing management and reporting
Recognized reporting provider Managed operations or consolidation

Pair DMARC with the rest of the stack

Microsoft 365 behind Proofpoint with p=none is a different sales conversation than Google Workspace with no recognized inbound gateway. Neither profile proves missing protection, because native and API-based controls may not appear in public MX.

Use Find Leads to research available infrastructure-based segments or Scan Prospects to qualify a known list. Convert the data into a respectful discovery question, not a claim about a vulnerability.

Suggested qualification conversation

A salesperson sees a validated p=none record. The appropriate preparation note is: "DMARC appears to be in monitoring mode at the observed date; ask who reviews aggregate reports and whether a rollout plan exists." The opening message should mention the MSP's authentication specialization rather than leading with an alleged security failure. If the buyer responds that they are intentionally running a monitored deployment, that is valuable discovery data, not an objection to argue away.

Conversely, a p=reject record can still be relevant to a managed reporting offer if that service is part of your portfolio. The objective is to find service fit, not rank companies by a simplistic DNS-derived fear score.

Turn infrastructure signals into a qualified prospect list.

Analyze domains you already know, or find new companies that match the technologies you target. Public DNS observations support discovery, not proof of an internal security weakness.

MSP Lead Generation: How to Find Qualified IT Prospects in 2026 →How to Build a Targeted MSP Prospect List Using DNS and Email Security Data →