Kalite eskan

Pasif

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 ka run against any URL — non domèn verification, non attestation. The trade-off se depth: passive misses everything that requires sending input pou discover.

What passive catches

• Missing sekirite headers (HSTS, CSP, frame-options, etc.).
• Insecure cookie attributes (non 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 ak known CVEs.

Aktif 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 nou gate it: la attestation flow

Aktif probes ka theoretically affect production — slow responses, erè spikes, garbage done in test stores. We require ou pou:

1. Verify la domèn via DNS TXT oswa an HTTP file (Account → Domèn).
2. Attest authorization — a single confirmation at eskan-start time saying ou have permission. Server-stamped ak ou IP, user-agent, ak timestamp; written pou 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 eskan never write pou ou repo ak never persist source code — only konklizyon evidence se stored. Quota: same scansPerMonth bucket as URL eskan.

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 eskan

The home page lets unsigned-up visitors run a single passive eskan per browser session. These eskan expire 24 hours after creation ak ka be migrated pou a real kont by signing up before they expire — la auth callback automatically attaches la anonymous eskan pou la nouvo org.