Skip to navigation

Proxy gateway reference list

See how many users sit behind a gateway IP, so you can refine IP blocking without blocking whole households or networks.

The proxy gateway list surfaces gateway IP addresses, such as proxies, Tor nodes and network gateways, and estimates the average number of users behind each one. Malicious users hide their real IP behind these nodes, and most suspicious activity, including botnet distribution and control, takes place behind them. But a gateway such as a home router also puts many legitimate devices behind a single IP.

This is a reference list, not a block list. Don’t block every IP on it. Use it as extra information to refine your IP or device blocking, for example to decide whether blocking an IP would also block many legitimate users.

When to use it

Use the gateway list to build extra logic on top of your blocking feeds. For example, block a flagged IP only when the gateway list shows a small number of users behind it, so you don’t block a large group of users.

If you’re looking for proxy and Tor IPs to block, use the IP block lists instead. They include Tor and proxy IPs (for example under the proxy fraud type) when they meet Pixalate’s high-IVT criteria.

At a glance

File formatCSV
File nameGateways_YYYYMMDD
ColumnsIP, user_bucket
File sizeUp to 1 GB

For the update schedule, access and file locations, see Delivery and integration or contact support@pixalate.com.

Schema

ColumnTypeDescription
IPstringA gateway IP address.
user_bucketstringThe range that the average number of users behind the IP falls in, written as lower-upper (for example 2-5), or 500+.

Every gateway has more than one user, so the buckets start at 2.

user_bucketAverage number of users behind the IP
2-52 to 5
6-10More than 5, up to 10
10-20More than 10, up to 20
20-50More than 20, up to 50
50-100More than 50, up to 100
100-500More than 100, up to 500
500+More than 500

Example rows (made-up values):

203.0.113.14,2-5
198.51.100.77,20-50
192.0.2.201,500+

Apply it pre-bid

  1. Load the latest gateway file next to your IP block lists.
  2. When a request’s IP is flagged by one of your blocking feeds, look up the IP in the gateway list.
  3. Use the user_bucket value in your blocking rule. For example, block the IP when few users sit behind it, and treat IPs with many users with more care.