Bulk targets + excludes

What it is

Two operations that make wide rollouts painless:

• Bulk import: paste a newline-separated list of IPs / CIDRs / hostnames into one textarea. The classifier rejects anything that isn’t a syntactically valid scope (so .convert.com or _dmarc.x bounces instead of silently entering as junk).
• Per-target excludes: a free-text list of IPs / CIDRs that RustScan honours via --exclude-addresses, AND the cloud’s “host ignore” rules honour at query time. Same list, both surfaces.

What it produces

• The import endpoint streams progress and returns {added, skipped_dupe, rejected_with_reason}.
• Excludes hide matching IPs from the inventory and prevent the scanner from pinging them.

What to use it for

• Onboarding a new customer / acquisition with a 10k-IP scope list (paste, watch the import bar, done).
• Excluding sensitive third-party services hosted on your IP range (e.g. a customer’s appliance you don’t want to probe).
• Decommissioning the long tail (bulk-pause everything in a CIDR that’s been re-IP’d).

Why it matters

Most security tools require either a CSV upload, a one-IP-per-click flow, or a vendor-managed Excel sheet. None of those scale to a weekly-churning surface. Bulk import + excludes turn surface management from “tickets to operations” to “paste into a textbox.”

Why it’s valuable

• No CSV ceremony. Just paste.
• Same exclude list for both directions. A single edit covers scanning AND searching.
• Bulk-pause / bulk-resume / bulk-delete. Quick-actions on the target list act on every selected row.

How to use it

Admin → Targets → Bulk import. Paste your list (one per line), optional company assignment for everything in the batch. Inspect the preview before commit.

For excludes: open a target’s edit drawer, paste the IPs / CIDRs to exclude. Same syntax as the RustScan --exclude-addresses flag.