NOT A SCANNER. PROOF, NOT PROBABILITIES.
If it does not reproduce, it is not a finding.
A scanner hands your reviewer a pile of maybe. NAXXAN is an autonomous red team that attacks your deployed surface, fires every exploit twice with a clean negative control, and hands your reviewer evidence — verifiable online, forever.
$995 · first five engagements only · report in 48h from signed scope · full refund before execution
The reviewer wants evidence. Your tools hand them opinions.
One of these is probably true right now: an enterprise security review is asking for proof of your external posture, a release with real exposure ships next month, or an AI feature is about to go to production. And after this summer's public reporting on autonomous agents, companies running them in production are fielding a harder question from above: how do we know what ours do when nobody is watching?
The scanner you already pay for
Checks headers, versions, and configuration. Never attempts an exploit. When the reviewer asks "has anyone actually proven this?", the honest answer is no — and its output is a list of "possibles" your team stopped triaging months ago.
The pentest you can't schedule in time
Real expertise, weeks of lead time, a point-in-time snapshot that ages in days. And when a finding is disputed, the dispute is a clash of opinions: nothing re-runs, so nobody can settle it.
The "AI-powered" tool that cried wolf
"The model believes there could be an injection." Your team burns an afternoon refuting a ghost. Ask any security buyer what breaks trust in a tool fastest: findings that turn out not to be real. The second time it happens, the report stops being read.
A hypothesis becomes a finding only when the exploit works in our sandbox and reproduces — twice, with a clean negative control. There is no step in our pipeline through which an unproven claim reaches your report.
A report your reviewer can interrogate.
You are not buying a scan or a document to believe. You are buying artifacts a skeptical third party can check on their own.
The interactive report
One self-contained HTML file, no login. Every finding ships with its PoC as a curl your reviewer can copy, paste, and re-run; the raw request and response; and a fingerprint of the whole report. They don't take your word for it — or ours.
The verified-secure attestation
A one-page certificate of what held: every attack class we ran against the target, with date and evidence, plus a fingerprint anyone can check online at /verify. What resisted goes on the record, not into a shrug.
The retest, included
After your fixes, we re-run every PoC and close each finding with a status: FIXED, still-vulnerable, or regressed. The engagement ends in a state, not a document.
Public verification
/verify shows the current status of any certificate we issue. Send the link to your auditor, your customer, or your board; they don't need an account with us either.
A "we found nothing" without a certificate is just an opinion.
Under the hood Every candidate finding executes twice, passes a negative control — the same probe with the payload removed must find nothing — and survives our own refutation before you ever see it. How it works →
Email to report in four steps.
Scope — one page, by email
You email engagements@naxxan.ai with your domain. We reply with a one-page scope: the target, read-only rules, and what we may create while testing (declared, itemized). It gets signed by someone with authority over the system — payment alone authorizes nothing.
The agent runs — ~100 s per run
An autonomous red-team agent maps the surface, writes a PoC for each hypothesis, and executes them in an isolated sandbox with no egress. A human operator approves every action that executes a test: the AI does not authorize itself.
Adjudication — we attack our own findings before you see them
Each candidate is refuted in class before it ships: is this a real auth bypass, or a public endpoint doing exactly what it was built to do? A reflection, or a real outbound request? Reproduction kills the hallucinated finding; adjudication kills the misclassified one. What survives is what you get.
Delivery and retest — within 48h of the signed scope
The report and the attestation land in your inbox. After your fixes, the included retest re-runs every PoC and closes each finding as FIXED / still-vulnerable / regressed.
Why 48 hours, if a run takes ~100 seconds? Because the machine's speed is not the product — the accountability is. The window covers the human gate on every action, adjudication of every finding, and a reviewed report before it ships. You get the agent's speed with a human signature on how it was used.
We publish even what we didn't find.
CYBERGYM · SUITE V1 · MEASURED ON OUR PUBLIC BENCHMARK SUITE (JUICE SHOP — VULNERABLE-BY-DESIGN, PUBLIC: THE ONLY TARGET WE CAN NAME) ────────────────────────────────────────────────────────────── Detection 2 of 4 known bugs (50%) · 3 runs · 95% Wilson CI [15%, 85%] (n = ground truth) False positives 0 — 9 findings adjudicated, 3 runs Run time ~100 s per run Signature ed25519 · public key available
Honest note A small suite with a wide interval — we print both. We publish even what we didn't find: suite v1 contains four known bugs and we land two; the two we miss are named, not buried (a BOLA we haven't landed within the run's budget, and an SSRF where the target reflects our probe but never makes the outbound connection). Every figure here is measured on our public benchmark suite and signed with ed25519. And when our own adjudication kills one of our numbers, we withdraw it and correct ourselves in public. If a vendor's benchmark never moves, ask who grades it.
In one engagement we delivered a CRITICAL finding. Our own adjudication killed it: the behavior reproduced, but the class was wrong — a public endpoint behaving as designed, not an auth bypass. We corrected the report, refunded the engagement in full, and built the class check that keeps that error from being born again. If your security provider has never been wrong, ask how they would know.
The sample report
Against OWASP Juice Shop (public, vulnerable by design): 5 validated findings, 3 negative hypotheses, each finding executed twice with a negative control, a 104.54 s run, generated end-to-end by the agent with no manual correction of the content.
One authorized domain, verified live
Direct, and with nothing to install: 3 findings delivered, 7 attack classes closed verified-secure with certificate.
The engineering floor
Underneath all of it: 668 tests, mypy strict, 0 errors. What cannot be tested cannot be promised.
One fixed price. No severity-contingent fee.
NAXXAN Verify External
USD 995 — the first five engagements signed and paid · USD 1,500 from the sixth
- One standard-scope target: one public app or API with its domain
- Validated findings with a reproducible PoC: zero "possibles"
- Deterministic CVSS severity
- Stack-specific remediation guidance
- Post-fix retest included: every finding closes as FIXED / still-vulnerable / regressed
- Verified-secure attestation with a verifiable fingerprint
- Read-only: no credentials, no repo access, nothing to install
Full refund before the first authorized execution.
100% payment upfront (card or ACH). Payment does not authorize the test — the signed scope does.
What you pay for is the analysis, the adversarial validation, and retest accountability — not consultant time or infrastructure. No severity-contingent fee. The price is the price.
Adjacent — quoted separately
- Authenticated Deep-Dive
- Codebase Verification
- AI & MCP Red Team (AI, LLM, MCP, or agent surfaces, when expressly authorized)
Visible and requestable through the same asynchronous flow; price by proposal. Running agents in production? The third one is the conversation to have.
NAXXAN Continuous — where we're headed. Recurring verification that starts from everything the previous one learned. It is not operational yet, so we don't sell it: join the waitlist → engagements@naxxan.ai
01How long does it take, total?
48 hours from the signed scope to the report and attestation in your inbox. Most of your own time is reading one page and signing it. The agent's runs take ~100 seconds; the rest of the window is the human gate on every action, adjudication, and report review.
02Is it legal for you to run this against my production?
Nothing runs until a one-page scope is signed by someone with authority over the system — payment alone authorizes nothing. The verification is read-only against the one target you authorize: no destructive payloads, no real data exfiltrated, no denial of service. Anything we create while testing (a test account, a record) is declared in the report.
03What exactly is a "standard-scope target"?
One public application or API with its domain — what an outside attacker sees. That is the unit Verify External is priced on. Additional targets, authenticated surfaces, and codebases are adjacent services, quoted separately.
04Who is behind NAXXAN?
A security engineer who builds in the open. We don't run a padded team page: the verifiable part of who we are is on this page — the public benchmark, the signed metrics, the sample report, and the correction we published when we got one wrong. One email, engagements@naxxan.ai, reaches the humans doing the work.
05What if you find nothing?
You keep the verified-secure attestation: every attack class we ran, what held, with date and evidence, and a fingerprint anyone can check at /verify. A "we found nothing" without a certificate is just an opinion.
06Do you write to my systems or touch my data?
No. Read-only by design: the PoCs prove a fault exists without destroying anything, exfiltrating real data, or taking the service down. Any test account or record we create is declared in the report.
07If you find something critical, do you charge more?
No. The price is the price. No severity-contingent fee — we do not charge more for finding something severe. That incentive inflates severities, and inflated severities are the fastest way to lose your blue team's trust. And when one of our own findings does not survive our refutation, we correct the report. It has already happened, and how we handled it is on this page.
08How do I verify your numbers are real?
Start with the sample report: full findings, no signup, PoCs you can re-run yourself today. Then pick any certificate and check its fingerprint online at /verify. The benchmark metrics are digitally signed and the public key is published. Every finding in a real report can be re-executed on request.
09Do you need access to my code or credentials?
Not for Verify External. We verify your authorized domain from the outside — exactly what a real attacker sees. Codebase and authenticated verification are adjacent services with their own scope.
10Who executes — a human or AI?
An autonomous red-team agent runs the assessment; the sample report took 104.54 s end to end. A human operator approves every action that executes a test. The AI does not authorize itself.
11How do I start?
Email engagements@naxxan.ai with your domain and a time window. We reply with the one-page scope; you sign it; the verification runs; the report lands within 48 hours of the signature. Calls are possible, never required.
12What about continuous verification?
Where we're headed, on a waitlist. We do not sell what is not operational yet.
One email starts it.
Email engagements@naxxan.ai with your domain and a time window. We send back the one-page scope — target, read-only rules, what we may create while testing — you sign it, the verification runs, and within 48 hours of the signature you have the report, the attestation, and a retest waiting for your fixes.
For Verify External we need nothing else from your side: no credentials, no repository, nothing to install. Prefer a call first? Possible. Never required.
suggested subject: Verify External — [your domain]
$995 for the first five engagements · full refund before the first authorized execution