Getting Started

This guide walks you through running your first scan on vapt.nexusvoidai.com, from sign-up to a finished report in about 3-4 hours.

---

1. Verify your domain

Before we test a target, you prove you are authorized to. In the dashboard, add your domain and choose one of three verification methods:

• DNS TXT record to add a record we provide to your DNS.
• Meta tag to drop a tag into your site's <head>.
• Verification file to upload a small file to your web root.

Verification usually takes under two minutes and confirms you have permission to scan the target.

---

2. Pay once

Choose your plan and pay securely via Stripe or Razorpay. There is no subscription and no recurring charge:

• Single Scan is one full pentest of one target.
• Bundle of 3 gives three scan credits, used on any domain you verify, whenever you want.

See the Pricing page for current prices.

---

3. Get your report

We deploy 150+ attacking agents against your verified target, validate every finding, and generate your reports. Within 3-4 hours you receive three documents:

• Full VAPT Report with every finding, its severity, CVSS, proof-of-concept evidence, and step-by-step remediation.
• Compliance Report with findings mapped to SOC 2, ISO 27001, PCI DSS, GDPR, and HIPAA controls.
• Business Report, a one-page executive brief with risk posture and a prioritized plan.

Download all three from Dashboard → Reports, or from the individual scan.

---

Your dashboard

Everything lives in one place at vapt.nexusvoidai.com:

• Domains to verify and manage the targets you are allowed to scan.
• Scans to start scans and track their status.
• Vulnerabilities for every finding across your scans, with status tracking (open, resolved, accepted risk).
• Reports to download the three reports for any completed scan.
• Trust & Badges to publish an attestation, get a public trust page, and copy your embeddable badge. See Trust & Attestations.
• Settings for account and billing.

---

After your first scan

• Fix and re-scan. Each finding ships with remediation guidance. Once you have deployed fixes, re-scan to verify them; findings you resolve stop counting against your posture.
• Mark accepted risks. If a flagged behaviour is intentional and by-design, mark it as an accepted risk with a justification. Accepted-risk items are documented separately and do not block a clean result.
• Publish your proof. A clean scan (0 Critical/High/Medium) issues a verifiable attestation you can publish. See Trust & Attestations.

Need continuous coverage instead of a point-in-time scan? Argus scans your source code and dependencies on every pull request, and the Red Teaming Suite runs ongoing adversarial testing of AI systems.