FixVibe

// docs / scans

Scan प्रकाराः

FixVibe runs three kinds of scans against three kinds of targets. Each has different gating, different speed, च different blast radius — pick तत् one that matches what त्वम्'re testing.

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 शक्नोति run against any URL — न domain verification, न attestation. The trade-off अस्ति depth: passive misses everything that requires sending input प्रति discover.

What passive catches

  • Missing सुरक्षा headers (HSTS, CSP, frame-options, etc.).
  • Insecure cookie attributes (न 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 सह 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 वयम् gate it: तत् attestation flow

Active probes शक्नोति theoretically affect production — slow responses, दोषः spikes, garbage दत्तांशः in test stores. We require त्वम् प्रति:

  1. Verify तत् domain via DNS TXT वा an HTTP file (Account → Domain-नामानि).
  2. Attest authorization — a single confirmation at scan-start time saying त्वम् have permission. Server-stamped सह तव 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 scans never write प्रति तव repo च never persist source code — only finding evidence अस्ति stored. Quota: same scansPerMonth bucket as URL scans.

Trigger via API

curl
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 scans

The home page lets unsigned-up visitors run a single passive scan per browser session. These scans expire 24 hours after creation च शक्नोति be migrated प्रति a real लेखा by signing up before they expire — तत् auth callback automatically attaches तत् anonymous scan प्रति तत् नूतनम् org.

Scan प्रकाराः — Docs · FixVibe