Possibly a duplicate of https://feedback.huntress.com/feature-requests/p/external-recon-for-a-block-of-ips

I understand that the IP addresses scanned by External Exposure are automatically picked up as the egress addresses of user traffic, then scanned. However, it would be very uncommon for any service to be mapped to or listening on those IPs. Generally, we would have some IPs designated for user egress and other IPs designated for listening services. It would be great if we could manually add endpoints via IP/DNS/subnet to be scanned by the tool. Currently doing this type of monitoring directly with shodan, would be great to have it done via Huntress. We understand that there are costs to Huntress, so you could bill this per 24 endpoints OR perhaps we could even BYO Shodan account and Huntress can use the shodan API via integration?