The most useful infrastructure signal is one that changes the next question a salesperson asks, not one that produces the most alarming headline.
Separate observation, interpretation and offer
A DMARC TXT record is an observation. The statement "this domain publishes a monitoring-only policy" is an interpretation. "We can help plan enforcement" is an offer. Keeping those three layers separate prevents a common mistake: representing public configuration as proof that a company is vulnerable or poorly managed.
Translate common signals into honest questions
| Public evidence | What you can say | Discovery question |
|---|---|---|
Valid DMARC p=none |
Monitoring-mode policy is published | Who owns reporting and the enforcement roadmap? |
| Recognized email gateway MX | A gateway is in the inbound path | Is policy administration internal or managed? |
| Microsoft 365 indicators | Evidence is consistent with M365 | How are email security and recovery responsibilities divided? |
| No recognized gateway MX | No known gateway in visible MX | Which native or API-based controls protect mail today? |
The final example is important. Absence of a recognized MX gateway never proves absence of email security. Microsoft Defender, API-based products and other layers may not be detectable from the same records.
Write the message around the customer's job
Avoid: "Our scan shows your security is weak." That statement overreaches. Prefer: "We work with MSP teams on DMARC reporting and enforcement. Is that managed internally today?" The prospect can understand the offer without accepting an unsupported diagnosis.
A concise sequence might begin with one relevant observation, follow with a concrete example of what your service includes, and end with a simple opt-out. Tailor channel and consent practices to applicable regulations and platform rules.
Prepare the call with an evidence sheet
Before speaking to the company, the rep should see the observed hostname or TXT record, timestamp, detection confidence, potential service fit and an explicit caveat. This reduces the chance a salesperson turns a technical inference into a factual claim while improvising.
Keep raw evidence internally in SecuTest rather than dumping DNS records into an unsolicited email. The commercial value is the explanation of what the service would solve.
Use the right product path
Scan an existing account list with SecuTest Scan Prospects. When the team needs fresh target companies fitting a technology profile, explore Find Leads. A detected stack helps choose conversations; it cannot guarantee a renewal event or a purchase intention.
Review objections as product feedback
If prospects say they already have a provider, ask whether they own the implementation, monitoring or escalation path. Record "not relevant" as feedback on the sales hypothesis, not automatically as a detector bug. Separate technical accuracy metrics from commercial conversion metrics.
Three objections and how to handle them
"We already have email security." That answer is expected when you target accounts with a recognized gateway. Ask whether your service complements their current provider or whether they outsource administration. Do not push a replacement pitch if the prospect does not need one.
"How do you know what we use?" Say that the observation came from publicly published DNS routing or policy records. Explain what those records can and cannot reveal. Do not imply privileged access, a penetration test or an assessment of the company's internal systems.
"DMARC is intentionally on monitoring." Acknowledge that this may be a sound rollout choice. A relevant follow-up is whether the reporting and enforcement roadmap are already owned. If the project is covered, close the conversation respectfully. Positive responses matter more than trying to win an argument about a DNS string.
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.