Skip to main content
SecuTest

About SecuTest

About SecuTest: cybersecurity technology intelligence.

SecuTest provides external infrastructure intelligence for IT and security teams, technology researchers and service providers. It turns publicly observable domain infrastructure into evidence-backed technology intelligence.

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.

Signal

See the visible stack

Workspace, MX routing, email-security gateways, DNS provider and policy records become structured account intelligence.

Evidence

Keep the source attached

Technical evidence stays inspectable. A classification should be explainable from the DNS or protocol signal that produced it.

Action

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 prospect workflow uses bounded, non-intrusive checks. No agent required, no credential attacks, and no exploitation or persistence.

Email

MX, SPF, DKIM and DMARC

Mail routing and email-policy signals support provider detection, workspace inference and prospect qualification.

Workspace

Microsoft and Google

Microsoft 365 can be strengthened with Entra ID, Autodiscover and DKIM evidence. Google Workspace is classified from supported Google signals.

External posture

DNS provider and public mail records

Scan Prospects prioritizes published MX, NS, SPF and DMARC evidence. It is not an internal-security assessment, and it does not claim to reveal every protection installed by the prospect.

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 distinguishes a measured public signal from a supported inference and an unknown result. Technical evidence is kept available for inspection.

Observed

Current principle

A public record or protocol response was actually observed, such as an MX hostname or DMARC policy.

Inferred

Current principle

Multiple observations support a classification, for example Microsoft 365 behind an email-security gateway.

Unknown

Current principle

The available evidence is insufficient to classify the signal reliably. SecuTest should say so rather than manufacture certainty.

Historical

Product direction

The roadmap adds first-seen, last-seen and confirmed changes so infrastructure migrations can become time-based buying signals.

Two focused workflows

Scan Prospects or Find Leads.

Qualify the domains you already have with a subscription, or look for matching prospects in SecuTest's separately collected dataset.

Scan Prospects

Bring your own domains

Scan one domain or a bulk list, inspect infrastructure evidence and export your prospect intelligence when your plan permits it.

Find Leads

Search collected prospects

Use available infrastructure filters to explore the separately sourced dataset and purchase an eligible CSV once, subject to marketplace availability.

No CRM required

Keep qualification simple

SecuTest is not a sales pipeline manager. It provides technical context and opportunities to qualify in the outreach tool you already use.

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.

Customer Intelligence

Your scans and prospects

Customer scans, technical evidence, CSV exports, prospect history and workspace data remain customer-scoped.

Global Intelligence

SecuTest collection only

The proprietary dataset is fed by SecuTest-operated collection infrastructure, not by customer prospect lists.

Why it matters

A clean product boundary

The separation reduces ambiguity around ownership, retention, deletion and the data model of the platform.

Direction

Better detection, then useful change signals.

The two current products are Scan Prospects and Find Leads. Future capabilities include verified infrastructure changes, buying signals and API access. They are not presented as current features until available.