External Attack Surface Review for MSPs
Use a passive external attack surface review to explain what a prospect publishes, what it means, and what it cannot prove.
Open the related path →PROSPECT · SOLUTION
Prepare MSP discovery with sourced public-domain evidence, sample findings, clear assessment limits and useful next questions.
Run a free domain scoreJoin Open Beta
EVIDENCE · INSIGHT · PROOF
Published SPF, DKIM and DMARC evidence.
Selected published configuration and records.
Supported public observations, with their dates and limits.
Not established by public evidence. Ask for approved read-only access.
Last reviewed September 25, 2026.
Review supported public-domain observations. Record their dates and limits. Translate a possible consequence into a question the buyer can answer.
When that question requires tenant evidence, request customer-approved, read-only access. Keep the public review and tenant review distinct.
SCOUTz keeps the source, timestamp, boundary, and next choice together. That makes the page useful to the seller, the owner, and the operator who receives the work after the meeting.
State why the account is relevant, show one dated observation, and ask permission to test whether the consequence matters. The goal is a shared question, not a surprise report or a forced product demonstration.
Move from observation to ownership, current practice, and the next evidence needed. A useful question names what was observed and what remains unknown. It lets the owner or IT contact correct the record without losing the thread.
A bounded next choice: stop, authorize a deeper review, or scope a first work item. The meeting should end with an owner and a next step, not an unqualified promise to send a generic proposal.
A published email-authentication record raises a policy question. It does not prove fraudulent mail was delivered. Ask who owns the policy, whether it is intentional and which approved check should follow.
This example is deliberately narrow. A finding can start a useful business conversation without proving a breach, a clean environment, a complete compliance program, or a commercial outcome. The report should say which of those statements it can support and which remain for the MSP and customer to establish.
Domain-review limits → Methodology → Static illustrative client-safe sample (PDF) → Pricing → Join Open Beta →
SCOUTz begins with the least intrusive source that can answer the question. 35 public sources for a domain scan; 92 sources with read-only Microsoft 365 consent. See the methodology for the full unit ledger.
Every finding carries authored business-language explanation, consequence, recommendation, and the evidence it came from. A check that could not be read appears as NOT ASSESSED THIS SCAN, so the next choice is visible instead of hidden inside a score.
The MSP still owns authorization, interpretation, customer communication, remediation, and the final commercial decision. SCOUTz supplies the record and the route. That boundary is what makes the output safe to use in a real relationship.
The public domain layer reads disclosed public records and signals. A customer-approved Microsoft 365 review reads supported configuration and metadata through a read-only connection. SCOUTz does not read messages, files, documents, chats, or prompts.
No. A check that could not be read is declared as a non-read. It remains visible on the record and is not converted into a pass or a blended score.
Yes. Client-safe output is designed for the MSP's name, logo, colors, contact details, and delivery motion while operator evidence remains available to the team doing the work.
The MSP reviews the evidence, agrees the next action with the customer, performs the work through its own process, and uses a supported rescan or source refresh to show what changed.
No. It makes discovery more specific. The evidence gives the MSP a starting question, while the prospect supplies context, ownership, priorities, and the decision path.
Read the methodology, review the trust boundary, see the sample report, compare pricing, and run the public tools before you choose the next step.
RELATED SOLUTIONS
Use a passive external attack surface review to explain what a prospect publishes, what it means, and what it cannot prove.
Open the related path →Use an evidence-first security discovery questionnaire with plain-language questions tied to observable states and unknowns.
Open the related path →Bring dated evidence, clear limits, and useful questions.