docs(wiki): JS Recon's TruffleHog engine is on for new projects
Existing projects keep their value (with the opt-in SQL); Travis CI Token
reports only what TruffleHog confirmed when it ran, with the numbers behind
that; why every JS Recon validator stays; regenerated settings registry.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs(wiki): JS Recon's TruffleHog engine
The JS Reconnaissance page documents the engine (merge, rules V1/V2, the
kept validators, the sidecar's hardening and network rule, the exclusion
list and its re-review on upgrade, the coverage reasons, the new Secret
properties) and the Phase 0 regex fixes. Settings reference, registry and
MCP reference regenerated for the two new fields; key validation is
tighten-only for Rules of Engagement.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs(wiki): settings sentences point at the generated registry, no stale counts (drift-map #49)
recon_settings/registry.json has 741 fields: 673 settable over MCP, 19
create-only, 49 never. The wiki quoted 180+, 190+, 196+, 245+, 328+ and
"650 of 717" (with 19 + 48). Each sentence now drops the number and, where
a reader wants the list or the breakdown, links Project-Settings-Registry,
which is generated from the registry. The preset-schema sentence follows
recon-preset-schema.ts: it covers every recon-pipeline parameter.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs(wiki): every recon preset in the reference tables, no stale preset counts (drift-map #46)
There are 26 built-in recon presets (webapp/src/lib/recon-presets/index.ts).
The Recon-Presets reference table lacked GraphQL Recon, Internal Network &
Active Directory, AI / LLM Surface Recon, Web Cache Poisoning and Supply
Chain Audit; they are added in the card grid's order with each preset's own
short description. The VHost & SNI decision table gains the four presets the
content test decides but the page omitted. The 21/22 counts become sentences
without a number.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs: wildcard DNS control, puredns skips recorded, unverified subdomains (plan 08)
Running-Reconnaissance: puredns failures are a Coverage Limitations line; RedAmon's
own wildcard control (random-label probe per zone, the drop rule and its CNAME
exception, late names, the zone stamp, limits); DNS off writes "unverified".
Creating-a-Project: the Subdomain Discovery panel and the fallback.
Subdomain-Takeover-Detection: takeover candidates under a wildcard zone are real
records. Attack-Surface-Graph: is_wildcard_zone / wildcard_ips, "unverified".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs: scan roots below their registrable domain, one Domain per registrable domain
Nested wildcards and covered-by notes, the Ownership TXT column and the
two accepted records, the widening notice, once-per-domain work, the org
Domain and its scan-root Subdomains, the old-model refusal and flagged saved
views, and the one-time Domain churn in a version compare.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs: batch targets group by registrable domain; auth scope only narrows
A batch hostname now groups under its registrable domain from the Public
Suffix List (foo.example.co.uk under example.co.uk, not co.uk). Document
the scope groups, what the list refuses, the upgrade effect on old graphs
and schedules, recon's own re-check, origin discovery's full PSL, the
auth scope rule shared by recon, agent and recordings, and that profile
scope hosts only narrow it. Regenerate the settings registry page.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs: OpenAPI import as a resource-enumeration tool
OpenAPI joins the group 5 tool lists, the session-header and capture-proxy
rows, the reconnaissance glossary, and the preset notes. Project Settings
Reference gains the openapi-import section the settings form links to: what
is fetched, what is never called, scope and address rules, run conditions,
withdrawal, and the per-document status.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs(roe): replace, remove and history of a project's RoE
Rules of Engagement: the upload is available after creation, from the
project form and the graph dashboard's RoE tab. New sections cover
replacing a document (set, reset, restored, kept; Widens), removing one,
what a document may never set or may only tighten, when a change takes
effect (next scan, running scans refuse, the agent at its next message,
schedules paused, third-party authorization) and the superseded-document
history. The engagement panel section describes the header actions and
the two notices. New screenshot of the replace review; the settings tab
and RoE tab screenshots re-taken.
Creating a Project: the record changes only with the document after
creation, and the upload stays available afterwards.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs: Multi mute, Models by feature and the three-layer Priority Board
Multi mute on Muted Nodes and the Red Zone, Models by feature in Global
Settings and on every feature page that asks for a model, the settings
that retire the per-project CypherFix model, and the Priority Board's
rules, review and decision layers with the MCP review and run tools.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs: partial recon covers every root of a Domain batch
Recon-Pipeline-Workflow: a Domain-batch section for Partial Recon (every
root in one run, stale and empty roots, literal vs wildcard scope,
per-root loops, refusals and the run report); custom subdomains may name
any project root. Creating-a-Project: cross-root hosts join their own
domain in a full batch run, and partial recon covers the whole batch.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
docs: preset load confirms and saves, presets hold every setting, applied badge
Recon-Presets and Creating-a-Project describe the new load flow (confirm,
replace, save immediately), what a preset now captures and excludes, and the
"Preset applied" badge. The settings registry page is regenerated and the
stored-parameter count is 715 for the new loadedPreset column.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
docs: split Rules of Engagement into limits and record
The engagement is two unrelated things, and the wiki described it as one.
Rules-of-Engagement.md is rewritten around the split: the LIMITS are ordinary
settings, reachable from the form and the API alike and enforced at scan start,
and the RECORD is the contract a person writes and no token can touch. The
"set once at creation, read-only afterwards" claim is gone; only the record is
creation-time.
Also updated:
- Recon-Presets: a preset never carries the engagement, at capture or at apply,
and the exclusion is a registry query rather than a name-prefix match
- MCP-Server: update_recon_settings reaches the limits in either direction, and
what keeps that safe is enforcement at scan start, not a write-time rule
- Creating-a-Project: tab 1 is the Engagement Record; the limits live elsewhere
and stay editable
- Origin-Discovery: the mechanism is unchanged, the field classification is not
- AI-Gauntlet: its RoE checkbox is a per-launch confirmation, distinct from the
project's engagement limits
- Project-Settings-Reference: an Engagement Limits section, and two checked
counts instead of one wrong one. "714 configurable parameters" overstated the
surface exactly as the "245+" it replaced understated it
- Project-Settings-Registry and MCP-API-Reference: regenerated
A test fails any page that still names tighten_engagement_roe, the tighten_only
disposition, or a roe* field as MCP-settable.
docs: add redamon.org/docs canonical banners + XBEN 8/16-20 walkthrough videos
Prepend a canonical banner to each curated wiki page linking to its version on
the official docs site (redamon.org/docs), so search engines consolidate
authority onto the owned domain instead of ranking the GitHub wiki. Also adds
the walkthrough video links to XBEN-008/016/017/018/019/020 in the benchmark table.
docs: Domain batch across the targeting-mode wiki pages
The project form's targeting mode is now three modes, not a domain/IP boolean.
Updated every page that described the two-mode selector:
- Creating-a-Project: the Targeting Mode section now lists Single Domain / IP /
CIDR / Domain batch, plus a full Domain Batch Mode subsection (the grouping
rule with the worked example, one-scan-not-many, progressive graph writes and
single version, the size limits).
- Running-Reconnaissance: the "Domain Mode vs IP Mode" table gains a Domain batch
column and a note that it runs the Single-Domain pipeline once per group.
- Project-Settings-Reference: target-config table renamed to a three-mode
Targeting Mode row plus the Domain Batch Hostnames field.
- Pentest-Reports and Home: scan-mode / overview wording.
First target mode renamed "Domain / Hostname" -> "Single Domain" to match the UI.
docs: remove Tor/proxychains recon-routing references
The "route reconnaissance traffic through Tor" feature was removed from the
product. Scrub the wiki of the removed setting and its behaviour:
- drop the "Use Tor for Recon" project-setting rows (Creating-a-Project,
Project-Settings-Reference)
- delete the naabu and puredns "Tor / proxychains" paragraphs
- graphql-cop always runs --network host now (no -T / -x / HTTP_PROXY)
- reword masscan raw-SYN notes and stealth/preset copy to drop Tor framing
Kept: CriminalIP threat-intel "Tor/VPN/proxy" TARGET detection, PDCP
anonymous-mode API access, and captured tool --help in session transcripts
(all unrelated to the removed routing feature).