Zscaler

What it is

The cloud enforcement node ranges Zscaler publishes for each of its eight clouds so customers can allow-list them. An employee behind a Zscaler gateway reaches the Internet from the gateway's address, so the location is the gateway's and the traffic is a workplace: the answer carries no risk weight for it, skips the datacenter weight the way it does for relay egress, and the cross-signal endpoint withholds its country comparisons.

What it answers

In the IP response this source feeds is_corporate_proxy, corporate_proxy, connection_type. Every answer names the datasets it read in its sources block with the date each was synced, so the figure on this page and the one in an answer are the same figure.

curl https://spaw.co/api/v1/ip \
  -H "Authorization: Bearer $SPAW_KEY" \
  -H "Content-Type: application/json" \
  -d '{"ip": "203.0.113.9"}'

How to read this page

A source names a network or an operator, never a person. An address inside one of these ranges tells you what the connection is — a cloud instance, a VPN exit, a gateway, a listed host — and nothing about who is behind it.

This page is a reference about detection, not a mirror of the operator's list: it prints counts and dates, not addresses. The operator publishes the list itself, at the address above, and is the place to read it.

More sources in corporate gateways

• Every source
• Every field, documented
• Look up an address

counts and dates read from the installed feed · checked 2026-09-13