Flags
Number of main scanner threads. Each main thread spawns additional per-protocol worker threads internally. The effective concurrency is higher than this value — for example, the HTTP scanner uses 20 worker threads per main thread, so with
--threads 10 there can be up to ~200 concurrent HTTP connections.Connection timeout in seconds for each protocol check. Increase this value on high-latency networks or when scanning through a SOCKS proxy. Decrease it to speed up scans against known-responsive networks.
Split the target list into groups of at most N hosts and scan one group at a time. A value of
0 (the default) places all hosts in a single group.Example: --max-scangroup 100 with 299 targets produces three groups: 100 / 100 / 99.Cannot be combined with --split-into.Split the target list into exactly N equally-sized groups and scan one group at a time. A value of
1 (the default) places all hosts in a single group.Example: --split-into 3 with 299 targets produces three groups: 100 / 100 / 99.Cannot be combined with --max-scangroup.Skip the first N scan groups. Use this to resume a partially completed scan without a
.resume file, or to distribute a scan across multiple machines by skipping groups already handled elsewhere.Example: --split-into 3 --skip 1 scans groups 2 and 3, skipping group 1.Number of AD objects retrieved per LDAP page during enumeration of computer accounts and SPNs. Reduce this value if the DC enforces a lower maximum page size or if large page requests cause timeouts.
Threading model
RelayKing uses a two-level threading model:- Main threads (
--threads): Control the number of host-level workers processing targets in parallel. - Protocol worker threads: Each main thread spawns protocol-specific sub-threads. HTTP and HTTPS scanners, for example, use 20 worker threads per main thread.
--threads 10, the scanner can maintain up to approximately 200 concurrent HTTP connections. Increasing --threads multiplies this concurrency proportionally.
Enabling
--proto-portscan typically has a larger impact on total scan time than increasing --threads, because it eliminates connection attempts to closed ports entirely. Use --proto-portscan before tuning thread counts.