Exposure Detection

Learn how Scanner detects and scores security exposures in web applications through passive analysis.

How Exposure Scoring Works

Our exposure scoring system evaluates multiple factors to produce a score from 0-100. Higher scores indicate more publicly visible configurations, missing protections, or exposed data.

0-30
Low Exposure
Good security posture with minimal public exposure
31-69
Medium Exposure
Some areas need attention to reduce risk
70-100
High Exposure
Significant exposure requiring immediate review

Score Components

Security Headers
Missing or misconfigured security headers
Up to 30 points
Source Maps
Publicly accessible JavaScript source maps
Up to 20 points
Detected Exposures
Based on severity of individual findings
Up to 30 points
Sensitive Files
Exposed configuration and data files
Up to 20 points

Types of Exposures We Detect

🗺️

Source Map Exposure

Publicly accessible source maps can expose original source code, making it easier for attackers to find vulnerabilities.

medium severity
🔓

Missing Security Headers

Security headers like CSP, HSTS, and X-Frame-Options protect against common attacks. Missing headers increase exposure.

medium severity
📄

Exposed Configuration Files

Files like .env, .git/config, or package.json can leak sensitive information including credentials and internal paths.

high severity
⚠️

Weak Header Configuration

Headers that are present but misconfigured (e.g., wildcard CORS, unsafe CSP directives) provide weaker protection.

low severity
🔗

Exposed Endpoints

API endpoints discoverable in JavaScript bundles can reveal internal architecture and potential attack surfaces.

medium severity
🚨

Sensitive Public Files

Database configs, environment files, and version control data accessible publicly pose critical security risks.

high severity

Check Your Domain's Exposure

Run a scan to discover what's publicly visible on your website and get actionable recommendations.

Start Scanning