You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4c12fe8
Browse filesBrowse the repository at this point in the historyBrowse files
Derive the MCP verdict from the library's Stats.Verdict (#263)
runMCPScan rebuilt a scan.Stats from the public Stats field by field to
reach the engine's verdict, a reverse mapping no test guarded. The
library now exports Stats.Verdict and the Verdict* constants, through
engineStats, the inverse of stats, which a round-trip reflection test
covers. The MCP server uses it via mcpVerdict, keeping its two
documented additions (not_run, and unreliable after an error), and a
table test checks its verdicts against internal/report for the same
scans. Reasons now name max_queries and the server's -max-duration
instead of raw setting tokens.
Fixes#263
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
22
22
- Takeover hints recognize two more providers: a CNAME to `*.animaapp.io` is marked `provider:anima` and one to `*.trydiscourse.com` is marked `provider:discourse` (#134, thanks @jdotc1).
23
23
-`-log-format json` writes the diagnostics on stderr (notices, warnings, errors, `-v` lines) as JSON Lines, one object per line with `time`, `level` (`error`, `warn`, `notice`, `info`, `debug`), `kind` (`message`, `scan`, `verbose`, `progress`, `simulation`, or an engine notice's category such as `wildcard` or `cap`), the `target` being scanned, the `message`, and the `settings` codes an engine message names (`["max_queries"]`). The simulation banner becomes one `simulation` notice, progress is an event with its numbers and only with an explicit `-progress`, and `-silent` keeps its meaning; results on stdout are unchanged. `SUBENUM_LOG_FORMAT` and the config file set it like any flag (#198).
24
24
-`-dry-run` prints what a scan would do without scanning: per target the candidates left after dedupe, invalid entries and `-exclude`, the queries (one per name and record type, and the most with every `-attempts` retry, both capped by `-max-queries`), how long they take at `-rate`, and whether the resolver passes the preflight, which is its only DNS query. `-format json` or `jsonl` prints the plan as JSON. No `-o` file is written, and the run exits 1 only if a preflight fails. `-ct`, `-permute` and `-recursive` add work it cannot count without querying, and it says so (#192).
25
+
-`pkg/subenum` exports `Stats.Verdict(interrupted)` and the `VerdictComplete`, `VerdictDegraded` and `VerdictUnreliable` constants: a finished scan's verdict and reason by the same rules as the CLI's run-quality report. `subenum mcp` now takes its verdict from it rather than rebuilding the engine's counters by hand, and its reasons name `max_queries` and "the server's -max-duration" instead of raw setting tokens (#263).
25
26
-`pkg/subenum` exports `Permutations(seeds, words []string) []string`, the candidate generator behind `-permute`: from names already found it returns the nearby variants (`api-dev`, `dev-api`, `dev.api`, `api2`), relative to the apex and ready to pass as a second scan's `Words`. `nil` words selects the CLI's built-in list. It sends no DNS queries (#197).
26
27
-`-tui` pre-fills its form from the command line: `subenum -tui example.com -w big.txt -r resolvers.txt` opens with the domain, wordlist and resolver file filled in, over `SUBENUM_*`, config file and remembered values. Flags the form has no field for are named in a warning instead of being dropped silently; the form takes the first `-w`. The form gains **Resolver Pool** (`-r`) and **Rate/Resolver** (`-rate-per-resolver`) fields, remembered in `last.json`. After a scan, `r` restores the values just scanned rather than re-applying the launch flags over them (#195).
27
28
-`-rate-per-resolver N` caps the DNS queries per second sent to each `-r` pool resolver, so a high global `-rate` no longer lands in uneven bursts on single members. Lookups go to resolvers with room first and wait only when every cap is spent; `-rate` still caps the total, and the stricter limit wins. The end-of-run resolver table and the report's `resolvers` entries gain a `throttled` count, and `pkg/subenum` gains `Config.RatePerResolver` (#196).
Copy file name to clipboardExpand all lines: docs/library.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -117,7 +117,7 @@ for _, c := range changes.Changed {
117
117
118
118
## Accounting
119
119
120
-
`Stats` puts each candidate name into exactly one outcome: `Found`, `NXDomain`, `Timeout`, `Refused`, `Other` or `WildcardFiltered`. Alongside are `QueriesSent`, `Skipped` (left untested by `MaxQueries` or `MaxDuration`, with `Expired` set for the latter), `Excluded`, the result counters `Takeover` and `Internal`, and the resolver-pool counters `PoolHits`, `Confirmed` and `Unconfirmed`. `Aborted` means the reliability guard stopped the scan, so the negatives mean nothing. `Wildcard` and `WildcardFingerprint` describe a wildcard zone. `RetryInconclusive` fills `Retried`, `Recovered` and `Inconclusive` (the names still without an answer), and `AutoRate` fills `RateBackoffs` and `FinalRate`. `Total()` sums the outcomes.
120
+
`Stats` puts each candidate name into exactly one outcome: `Found`, `NXDomain`, `Timeout`, `Refused`, `Other` or `WildcardFiltered`. Alongside are `QueriesSent`, `Skipped` (left untested by `MaxQueries` or `MaxDuration`, with `Expired` set for the latter), `Excluded`, the result counters `Takeover` and `Internal`, and the resolver-pool counters `PoolHits`, `Confirmed` and `Unconfirmed`. `Aborted` means the reliability guard stopped the scan, so the negatives mean nothing. `Wildcard` and `WildcardFingerprint` describe a wildcard zone. `RetryInconclusive` fills `Retried`, `Recovered` and `Inconclusive` (the names still without an answer), and `AutoRate` fills `RateBackoffs` and `FinalRate`. `Total()` sums the outcomes.`Verdict(interrupted)`{% include unreleased.html library="Verdict" %} applies the CLI run-quality report's rules: `VerdictComplete`, `VerdictDegraded` or `VerdictUnreliable`, with the reason in plain words (naming `Config` fields such as `MaxQueries`).
0 commit comments