Can I block specific services or countries?

If Spur identifies a provider such as NetNut, does that mean the traffic originated directly from that provider's customer?

Not necessarily. Proxy ecosystems often involve resellers, downstream providers, SDK operators, and shared infrastructure. A provider label identifies infrastructure associated with the traffic but should not be treated as attribution of a specific end user without additional evidence and investigation.

How can I download data on all IPv4 and IPv6 addresses?

IP location, routing, and ownership information is produced at the network level and presented into netblocks. Other data such as client fields or service attributions are produced on an individual IP address basis. For our API customer this coverage is automatically merged to produce full IPv4 and IPv6 coverage. For on-prem services, a combination of these two granularities must be used to cover all IP space.

Should Spur data be used as a blocking list?

Generally, no. Spur is designed to provide context and intelligence rather than a simple allow/block decision. Most organizations achieve the best results when Spur data is incorporated into broader risk models and decisioning workflows.

Can Spur enrich large volumes of IP addresses?

Yes. Organizations commonly use the Spur Context API and data feeds to enrich IP addresses at scale, enabling proxy detection, VPN identification, infrastructure classification, and geolocation analysis across large datasets.

Can organizations rely on country-level geolocation alone?

Country-level geolocation remains useful, but it should not be treated as a complete solution. Modern anonymization services allow users to appear in approved countries while operating elsewhere, making additional infrastructure context increasingly important.