#
FAQ
Browse common questions and issues below. Don't see the answer you're looking for? Email us at help@netspi.com
An invalid CIDR means there are nonzero bits to the right of the netmask of the CIDR range. For
example, 192.168.0.1/24 is invalid because the netmask is 11111111.11111111.11111111.00000000 but the
binary representation of that IP address is 11000000.10101000.00000000.00000001.
In some cases a range like /31 is meant to denote "this address and the one after it", however that is not
RFC compliant. That difference is why these addresses are not corrected automatically, as it may result in
incorrect IP addresses being added.
Numbers presented on dashboards, e.g. "Live IPs", represent a daily max. It's possible an IP was live earlier today, but became unavailable at some point. This IP would be shown as not live in the grids, but would be included in the daily "Live IPs" count.
Please select here to access allowlist.
In addition to IP address, HTTP scanning traffic can be identified by the presence of one or both of the following headers:
X-NetSPI-EASM: help@netspi.comUser-Agent: NetSPI EASM (help@netspi.com)