Tipi di scansione

Passive

Available on every tier. A passive scan never sends crafted attack input; it fetches the URL like a normal browser and checks shipped responses, client assets, BaaS exposure, DNS, and public security posture against 250+ vulnerability classes.

Because it's read-only, passive pò run against any URL — nò duminiu verification, nò attestation. The trade-off hè depth: passive misses everything that requires sending input à discover.

What passive catches

• Missing sicurità headers (HSTS, CSP, frame-options, etc.).
• Insecure cookie attributes (nò Secure / HttpOnly / SameSite).
• Weak TLS configuration, expired certs, missing HSTS preload.
• Secrets in JS bundles (Supabase service keys, AWS keys, Stripe sk_, etc.).
• Exposed source maps, debug endpoints, OpenAPI specs, GraphQL introspection.
• Open Supabase RLS / Firebase rules / Clerk misconfiguration.
• DNS (subdomain takeover, missing SPF/DKIM/DMARC).
• Threat-intel listings (Spamhaus, URLhaus).
• Outdated framework versions cù known CVEs.

Active Hobby+

Active scans perform bounded verification against verified domains you have explicitly authorized. They are available on the Hobby plan and higher tiers (Pro, Unlimited) and are designed to confirm risky behavior without publishing the underlying probe recipes.

Why noi gate it: u attestation flow

Active probes pò theoretically affect production — slow responses, errore spikes, garbage dati in test stores. We require voi à:

1. Verify u duminiu via DNS TXT o an HTTP file (Account → Duminii).
2. Attest authorization — a single confirmation at scansione-start time saying voi have permission. Server-stamped cù u vostru IP, user-agent, è timestamp; written à audit_logs.

For scheduled re-scans and API/MCP active starts, domain authorization is recorded from Dashboard → Domains and can be revoked at any time. Automated active scans use the authorized safety level for that domain.

GitHub repository Pro+

Repo scans skip deployed URL testing and review source through the FixVibe GitHub App or your OAuth connection. They report high-confidence code, dependency, and repository-security risks without storing your source code.

Repo scansioni never write à u vostru repo è never persist source code — only risultatu evidence hè stored. Quota: same scansPerMonth bucket as URL scansioni.

Trigger via API

curl -X POST https://fixvibe.app/api/v1/scans \
  -H "Authorization: Bearer fxv_..." \
  -H "content-type: application/json" \
  -d '{"target":"https://staging.example.com"}'

REST API and MCP can start passive scans, and can start active scans for verified domains that have been explicitly authorized in Dashboard → Domains. Full reference: /docs/api.

Anonymous one-shot scansioni

The home page lets unsigned-up visitors run a single passive scansione per browser session. These scansioni expire 24 hours after creation è pò be migrated à a real contu by signing up before they expire — u auth callback automatically attaches u anonymous scansione à u novu org.