Network targets
IP and CIDR targets
Add a public IP or a range up to /24, attest that you may scan it (or be auto-verified from inside it), and get a daily port scan with history per target.
Updated · 2 min read
What can be a target
A single public IPv4 address, or a CIDR range of at most 256 addresses (/24). Larger ranges are refused with "Split it into blocks of /24 or smaller". Private, loopback, link-local, multicast and other reserved ranges are refused outright, and the guardrail runs again inside the scan itself as defence in depth.
The attestation
Before a target is scanned you must agree to the exact statement:
I own, operate, or am authorized in writing to run security scans against this IP address or network.
The attestation is stored with the target, with who gave it and when. Over MCP, add_ip_target takes attestation: true, and the tool's instructions tell the assistant to pass it only after you have said so in words.
Auto-verification from inside the range
If you add a target while connected from an address inside it (the office network, a VPN that exits through the range), the request's source address proves the point and no attestation is needed. The target is recorded as connected-from with "Auto-verified: request originated from <ip>, inside the target". In the iOS app the add form offers Use this connection with the public address the phone is using.
Scanning
| When | What |
|---|---|
| At add time | Targets of 32 addresses or fewer are scanned immediately and the result returns with the add. Larger ranges wait for the nightly sweep, so a /24 added at 09:00 is not 256 addresses probed at 09:00 |
| Daily | Every target with daily_scan on is probed in the daily sweep, which starts at 06:00 UTC |
| Scan now | POST /api/ip-targets/:id/scan (tool scan_ip_target), once per hour per target. Small ranges answer inside the request; larger ones are queued |
The probe is the same 128-port TCP connect scan the domain scanner uses, from a sandboxed container. See Hosts and open ports.
Results
Each scan records, per address, the open ports with the service name (from the banner where one was read, otherwise by what the port number means), the version where visible, and a risk note. GET /api/ip-targets/:id/scans (tool list_ip_target_scans) lists past scans so a newly opened port is visible as a change.
Clients
A target can be filed under a scan client (client_id) so a customer's ranges sit with their domains. See Groups, Personal and Business.
Removing
DELETE /api/ip-targets/:id stops scanning and removes the target with its history. Turn daily_scan off with PATCH to pause instead.
Common questions
Can I add a hostname? No. Hostnames are domains; add the domain and its hosts are discovered. Network targets are for addresses that have no domain of their own.
IPv6? Not yet. The guardrail and the probe are IPv4.
Will the scan trip my IDS? It is a connect scan against 128 ports, paced and bounded. An intrusion detection system will log it; it will not see an exploit attempt.
Keep reading
Related articles
- Business profile and keyword targetsThe saved business profile that every measurement centres on, location verification, targeting mode and radius, and up to 25 tracked phrases per domain.Local SEO ·Updated
- Rank checksLive positions for every tracked phrase on the local pack and organic surfaces, one credit per phrase per surface, with history and the surfaces you can add.Local SEO ·Updated
- Add your first domainWhat the add-domain sheet turns on by default, what the first scan covers, and how to import a list of domains at once.Getting started ·Updated