External visibility monitoring means checking your web assets (domains, APIs, services) from outside your network, exactly as attackers or users would see them. OutScope performs DNS, TCP, TLS, and HTTP checks from external vantage points to validate what's actually accessible on the internet, helping you discover shadow IT, exposed services, and misconfigurations before they become security issues.

OutScope is NOT a vulnerability scanner or DAST tool. We don't exploit or look for vulnerabilities. Instead, we're the pre-DAST reconnaissance step that answers 'What can the internet see?' before you run expensive security scans. We validate which assets are reachable, analyzable, blocked by WAF, require authentication, or expose APIs - helping you scope and prioritize what to test.

No. OutScope is completely agentless and requires zero credentials. We check your assets from the outside, just like any internet user or attacker would. This is actually a feature - it shows you the true external exposure without internal bias. Simply provide the domain or IP you want to check, and we'll probe it from our external nodes.

By default, OutScope operates in privacy-first mode and does NOT capture HTTP response content. We only collect metadata: DNS records, TCP connectivity status, TLS certificate information, HTTP status codes, and headers. Content sampling is opt-in (include_content_sample=true) and automatically deleted after 7-30 days. This ensures your sensitive data stays private while still providing actionable visibility insights.

Yes! OutScope automatically detects and classifies services, including API endpoints and documentation. We identify OpenAPI/Swagger specs, ReDoc interfaces, GraphQL endpoints, and common API patterns. This helps you discover forgotten APIs, internal documentation accidentally exposed to the internet, and understand your true external API attack surface.

OutScope reduces DAST noise and costs by pre-validating which assets are actually analyzable. Before running expensive DAST scans, we determine if a service is reachable, if it speaks HTTP, if it's blocked by WAF, if it requires authentication, and what type of service it is (HTML, API, etc.). This lets you scope DAST to only analyzable targets, saving time and resources.

Vantage points are the geographic locations from which we perform checks. Different regions may see different results due to CDN routing, geo-blocking, or regional DNS. OutScope workers can be named by region (eu-west-1, us-east-1, etc.) so you can verify how your services appear from different parts of the world, just like distributed attackers or users would see them.

OutScope implements fair usage rate limiting: per-minute request limits (30-120 req/min), concurrent check limits (5-30 inflight), and monthly quotas based on your plan. When you hit a limit, we return HTTP 429 with Retry-After headers. Our Python SDK automatically handles rate limits, waits when needed, and retries requests - making it seamless to create thousands of checks without manual limit management.

Absolutely! OutScope is API-first and designed for automation. Use our REST API or Python SDK to validate external exposure as part of your deployment pipeline. Check if new services are reachable, verify DNS propagation, validate SSL certificates, and confirm WAF rules are working - all before marking a deployment as successful. Perfect for infrastructure-as-code and GitOps workflows.

Check results (metadata like DNS, connectivity, status codes) are stored indefinitely in your tenant and available via API. However, HTTP content samples (when opted-in) are automatically cleaned after the retention period you specify (7-30 days). After cleanup, the content field shows 'CLEANED' status. You can configure retention per check to balance debugging needs with privacy requirements.

Yes! We automatically detect common authentication patterns including HTTP Basic Auth, OAuth redirects, login forms, API key requirements, and 401/403 responses. This helps you identify which services require authentication before testing, discover accidentally exposed authenticated endpoints, and understand your public vs. authenticated attack surface.

Checks typically complete in 5-30 seconds depending on the number of ports and paths. DNS resolution takes 1-3 seconds, TCP/TLS connectivity 1-5 seconds per port, and HTTP requests 2-10 seconds per path (including redirect following). Checks run asynchronously, so you can queue thousands and retrieve results when ready. Use our Python SDK for efficient batch processing.