Scanner IP addresses
HostedScan's external scanners run from a fixed set of public IP addresses. If a firewall, WAF, or geo-blocking rule drops traffic from these addresses, scans will report the target as unreachable or return far fewer findings than expected. Allowlist the scanner IP addresses to get complete results.
HostedScan provides two methods for identifying the scanner IP addresses.
Method 1: DNS lookup
The hostname scanners.hostedscan.com resolves to every scanner IP address (one A record per scanner), and each scanner IP also has reverse DNS pointing back to that hostname. Either direction identifies a HostedScan scanner.
Get the full IP list with a command such as nslookup:
nslookup scanners.hostedscan.com
Online DNS lookup tools such as MXToolbox work as well.
Method 2: Public API endpoint
HostedScan also maintains an API endpoint that returns a JSON array of the scanner IP addresses. This endpoint is public and does not require authentication:
https://api.hostedscan.com/scanners
Example response:
["104.200.29.231", "104.237.145.53", "104.237.146.30", "..."]
This endpoint is convenient for keeping firewall rules in sync automatically. For example, with curl and jq:
curl -s https://api.hostedscan.com/scanners | jq -r '.[]'
The list of scanner IP addresses can change as capacity is added. Prefer re-fetching the list from DNS or the API endpoint over hardcoding a copy of it.
Related
- Internal network scanning: scan private networks that external scanners cannot reach, without opening any inbound ports.
- How can I fix an unreachable target?
- What IP addresses are used for the HostedScan vulnerability scanners?