Why does an IP show a specific VPN provider?
Spur names the VPN provider in the operator field of the tunnels object. Many providers publish their server lists, so you can often check the attribution against the provider's own list. VPN brands that run on another provider's network show that provider's name, for example Mozilla VPN shows as Mullvad VPN.
Where the provider name appears
When an IP is part of a VPN service, the Context API's tunnels object includes an operator value that names the provider, for example MULLVAD_VPN. The IP page shows the same provider name.
Checking an attribution yourself
Many VPN providers publish lists of their servers. If an IP sits in the same network range as servers on the provider's own list, that's a quick way to confirm the attribution. The address traffic leaves from can differ from the server address users connect to. See Entrance IPs vs. Exit IPs for Anonymizing Tunnels.
VPN brands that run on another provider's network
Some VPN products run on another provider's servers. Spur names the provider that operates the network. For example, Mozilla VPN runs on Mullvad's servers, so traffic from a Mozilla VPN user shows as Mullvad VPN.
If you think the provider is wrong
Use the Report button on the IP's page in the Spur app. For how Spur classifies IPs in general, see How Spur IP Classifications Work: Observed Behavior, Not IP Ownership.
Similar questions
How does Spur detect VPNs, residential proxies, and ISP proxies?
Spur classifies an IP from the activity it observes on it, not from who owns the IP. It combines several kinds of evidence, including infrastructure and routing data, behavior over time, and ongoing research into VPN and proxy services, and evaluates them together to decide whether an IP belongs to a VPN, residential proxy network, ISP proxy, hosting provider, or other category.
Does the use of a VPN always indicate malicious activity?
No. Many users rely on VPNs for privacy, remote work, travel, or security. VPN detection should be viewed as an additional signal that helps organizations better understand the context of a connection rather than as evidence of malicious intent.
How can I download all IP addresses for a certain VPN or proxy provider?
This functionality is reserved for our on-prem data customers. Our API access only allows for individual IP Address lookups.
Why is a Cloudflare IP address classified as Anonymizing?
Some IPs belonging to a CDN like Cloudflare are classified as Anonymizing because they're used as the TLS entry point for an anonymizing tunnel service. The connecting client's TLS handshake names a legitimate-looking hostname, and the CDN routes the traffic to unrelated tunnel infrastructure behind it — the named domain and the CDN provider itself aren't involved in or aware of the proxying. In Spur's data this is reflected in the `tunnels` field, which distinguishes an IP's role as a tunnel entrance from its role as an exit. If your use case depends specifically on identifying egress points, you can filter out entrance-only IPs, since these are rarely also used as an exit for other services.
What does the risks field represent?
The Context API's risks field is an array of specific risk-factor tags observed for an IP, rather than a single composite score. Current values include AD_FRAUD, CALLBACK_PROXY, GEO_MISMATCH, LOGIN_BRUTEFORCE, TUNNEL, and WEB_SCRAPING — an IP can carry more than one, or none.
Related guides & explainers
Entrance IPs vs. Exit IPs for Anonymizing Tunnels
Some anonymizing tunnel configurations route through shared infrastructure, like Cloudflare, before reaching the tunnel operator's own exit point. Here's why blocking the entrance IP can affect unrelated legitimate traffic, and what to enforce on instead.
Anonymizing vs. Non-Anonymizing Tunnels: What the "anonymous" Flag Means
Not every tunnel Spur detects is built to anonymize. The tunnels object's anonymous flag distinguishes corporate/ZTNA infrastructure from services designed to obscure a user's origin.
Why the Organization Field Isn't Available the Same Way Across Spur's Data Feeds
The Context API's per-IP organization field isn't guaranteed in every data feed. Each feed has a different schema and covers a different slice of IP space, so field availability varies by feed.
Context API Chrome Extension
Install Spur's Context API Chrome Extension to look up IP enrichment data directly from any web page — highlight an IP and get results inline, without leaving your browser. This is a developer-mode tool, not a Chrome Web Store listing.