Skip to content
Passive exposure review / bounded scan

Your frontend is public. Your API keys shouldn’t be.

See what any visitor can see in your scripts, source maps and public files, and catch potential AI and SaaS credential exposure before it becomes an incident.

ReconVeil inspects authorised public resources without testing credentials. Review redacted evidence, confidence and coverage limits before deciding what to fix.

Free to startNo card requiredFor developers and security teams

Only scan sites you own or are explicitly authorised to test. A finding is evidence to review—not proof of a working credential.

  • AI API key exposure
  • SaaS credential exposure
  • Sensitive frontend configuration
  • Public security signals
—
layered detection rules
6
evidence analysis layers
—
scans conducted
0
raw secrets stored
Demo scan / passive modeRedacted preview
collect / boundedassess / redactedhandoff / ready
Public surface to safe decision

What secrets is your frontend exposing?

Browser-delivered JavaScript, public bundles and accessible frontend resources can reveal credentials or sensitive configuration within the permitted scan scope. Inspection includes statically referenced same-host scripts, not complete runtime application coverage.

If a detected credential is genuine and usable, exposure could lead to unauthorised API usage, unexpected AI and SaaS costs, exposed service credentials or unintended access to connected services.

Findings are potential exposures to review—not proof of compromise. Intentionally public keys are not automatically vulnerabilities.

See the full method
  1. 01
    Collect

    Collect reachable pages, scripts and files within safe request and size limits.

  2. 02
    Detect

    Flag potential secrets, exposed configuration and missing protections.

  3. 03
    Assess

    Explain each finding and prioritise what to review or fix.

Evidence layer
Exposure finding
observed
Backend service-role key
/env.js:4 · high confidence · masked display
SUPABASE_SERVICE_KEY: [redacted before storage]
likely exposurefingerprint: stable / masked
served from a public file privileged role indicator context signal recognised provider not contacted
Explainable evidence

Evidence before escalation.

Supported AI and SaaS credential formats are reviewed with context, confidence and redacted evidence. See why a candidate surfaced and what to do next; public-by-design keys are distinguished from backend secrets.

entropycontextfingerprintcoverage
ReconVeil — Security Evidence. Intelligent Assessment.

ReconVeil collects and analyses technical security evidence. AEGIS adds evidence-aware assessment of stored scanner findings. AEGIS Lite currently assesses the recorded versions of jQuery, Lodash and DOMPurify against a curated OSV advisory snapshot.

An assessment does not confirm exploitability, reachable vulnerable code or overall system security. AEGIS reads stored evidence only; it does not scan or contact your site.

How AEGIS assessments work
For the people shipping

Developers, small teams and security practitioners.

Use a fast public-surface review before release, after a frontend change or as a repeatable baseline in CI.

How data is handled

Redacted evidence, not raw secrets.

Values are redacted before storage. ReconVeil keeps masked displays, fingerprints, sanitised locations, coverage and recommendations. Do not send secrets to support.

Read data handling
Try it without a card

Explore the interactive demo.

Explore the real demo flow before creating a paid workflow. Free accounts do not require a bank card.

Try the interactive demo
Developer workflow

Make exposure review part of how your team ships.

Scheduled scans start with Pro. Developer adds scoped API and CLI access plus expiring CI baselines with justification and owner/team labels. Verify each exact hostname before automated scans.

See Developer workflow features

Developer accounts can also connect an MCP-capable assistant with OAuth. Access is read-only and returns redacted results only.

How the MCP integration works
01 / automate

Scheduled scans

Pro includes up to 3 schedules; Developer includes up to 10. Scheduled runs share your plan’s scan allowance.

02 / connect

CI, API and CLI

Developer adds scoped API and CLI access for redacted, machine-readable evidence and sanitized SARIF CI artifacts.

03 / compare

Governed baselines

Track accepted risk with expiry, owner/team labels and environment scope. Labels record responsibility, not team permissions. Accepted risk is not a verified fix.

04 / organise

Account-owned projects

Organise findings and read-only case history across your projects. Shared member access and project roles are planned, not available today.

Team collaboration, enterprise SSO/SAML and configurable retention are planned separately. Planned capabilities are not available today and are not included in today's subscription. Availability, eligible plans and pricing will be confirmed before launch. No release date is committed.

Explore planned capabilities
Start with the public edge

Turn exposure findings into safer next steps.

Scan your public website for potential credential exposure and risky configuration. Review redacted findings and recommended next steps—free, with no card required.

Authorised testing only · Read responsible use · FAQ