See the visible stack
Workspace, MX routing, email-security gateways, DNS provider and policy records become structured account intelligence.
About SecuTest
External infrastructure intelligence for MSP prospecting.
SecuTest turns public technical signals into compact prospect intelligence: what infrastructure is visible, what the evidence supports, where a commercial gap may exist, and which service is worth qualifying next.
Why it exists
Sales teams need technical context before the discovery call.
Traditional lead databases are good at company attributes. SecuTest focuses on externally observable infrastructure so an MSP can qualify accounts around the services it actually sells.
Keep the source attached
Technical evidence stays inspectable. A classification should be explainable from the DNS or protocol signal that produced it.
Translate signal into a question
Gap and Sell Next are qualification hypotheses, not claims about the prospect's complete internal environment.
What SecuTest observes today
Public signals only, with explicit boundaries.
The current product uses bounded, non-intrusive checks. No agent required, no credential attacks, and no exploitation or persistence.
MX, SPF, DKIM and DMARC
Mail routing and email-policy signals support provider detection, workspace inference and prospect qualification.
Microsoft and Google
Microsoft 365 can be strengthened with Entra ID, Autodiscover and DKIM evidence. Google Workspace is classified from supported Google signals.
DNS, TLS, HTTP and exposure
Additional public evidence can add context, but the product remains focused on evidence that helps an MSP qualify a commercial conversation.
Point-in-time observations: public infrastructure changes. A signal that is unavailable, unrecognized or not detected is not automatically evidence that a technology or control is absent.
Evidence model
Observed, inferred, unknown.
SecuTest is moving toward a single intelligence contract where every conclusion can preserve its source, confidence and evidence.
Observed
Current principleA public record or protocol response was actually observed, such as an MX hostname or DMARC policy.
Inferred
Current principleMultiple observations support a classification, for example Microsoft 365 behind an email-security gateway.
Unknown
Current principleThe available evidence is insufficient to classify the signal reliably. SecuTest should say so rather than manufacture certainty.
Historical
Product directionThe roadmap adds first-seen, last-seen and confirmed changes so infrastructure migrations can become time-based buying signals.
Customer data boundary
Customer data stays customer data.
Domains scanned or uploaded by a customer belong to that workspace's Customer Intelligence. They are not used to populate SecuTest Global Intelligence or the proprietary global dataset.
Your scans and prospects
Customer scans, notes, exports, prospect history and workspace data remain customer-scoped.
SecuTest collection only
The proprietary dataset is designed to be fed by SecuTest-operated collection infrastructure, not by customer prospect lists.
A clean product boundary
The separation reduces ambiguity around ownership, retention, deletion and the future data moat of the platform.
Direction
Scanner → proprietary dataset → search → change intelligence.
The current product qualifies domains you bring. The roadmap progressively adds proprietary global collection, direct search and filters, historical changes, buying signals and API access. Those future capabilities are not presented as current features until they ship.