What does attack surface mean on this page?
A map is the start of the loop, not the outcome. When a route, commit, or setting appears, the same workspace investigates it.
WORKSPACE/Attack surface
Understand the attack surface. Keep it current.
The research workspace watches web apps and APIs, source, cloud accounts, and workspace settings. A new route, commit, or config is the reason to investigate again.
Find vulnerabilities. Prove their impact.
What stays in view
Scope comes from four surfaces
Discovery is the start of the investigation, not a spreadsheet you maintain. Each surface stays connected so the next change is visible.
WEB
Apps and APIs
Routes and endpoints that are live, so a new path is in scope for the next hypothesis.
SOURCE
Repositories
Local code, GitHub, and GitLab. A commit changes what the workspace should read.
CLOUD
AWS, Google Cloud, Azure
Connected accounts. A new host or an exposed resource shows up as something to investigate.
WORKSPACE
Microsoft 365 and Google
Tenant and organization settings that change after the last review.
Then investigate
A visible surface is not a finding. The next step is a hypothesis, a test, and evidence of impact.
It does not stop at the map
The same workspace runs the next pass when the surface changes. You review what appeared. You do not rebuild the list by hand.
Evidence
What we can prove about the surface
The outside view of a public hostname is a first-party measurement. It is not the whole workspace.
- ~2 min
- Free external scan, typical run
- 41k+
- Domains mapped on the free scanner
- 0
- Packets that enter your network
01A public hostname can be mapped from outside without an agent or inbound ports.
ResultThe public Attack Surface Scan maps subdomains, IPs, open ports, and visible products in about two minutes. Trusteed reports 41k+ domains mapped on that scanner. The scan sends no packets into the target’s internal network.
MethodPassive and unauthenticated external reconnaissance. Timing is wall-clock from submit to first report. Domain count is the cumulative first-party total on the free tool as of the date below.
Scope · September 2026Internet-facing hostnames. Not authenticated API testing, source review, cloud inventory, or workspace configuration.
Buying questions
What should the workspace keep in view?
Attack surface here is the scope of the research: web apps and APIs, source, cloud accounts, and workspace settings. A change is the reason to investigate again.
02Which surfaces feed the surface?
You do not need every surface on day one. Connect the estate a change will actually come from.
| Surface | What a change looks like |
|---|---|
| Web | A new route or API |
| Source | A commit in local code, GitHub, or GitLab |
| Cloud | A new or exposed cloud resource |
| Workspace | A tenant or organization setting |
03When is this the wrong buy?
The workspace only sees what you connect. A one-time export is not a continuous surface.
Not a fitWrong buy for a laptop inventory or a one-week consultant map with no follow-up.
Find vulnerabilities. Prove their impact.
Start from the surface you can already name. Keep it in the workspace as it changes.