Acceptable use
Some destinations are blocked on every account by default. This is not a plan limit. It applies to everyone, and it exists so the network stays usable for legitimate work.
Blocked by default
Section titled “Blocked by default”| Category | Includes |
|---|---|
| Government | All .gov domains |
| Education | All .edu domains |
| Banking and finance | Retail banks, payment processors, brokerages |
| Other sensitive targets | Categories we assess as high-risk |
We also maintain an ad-hoc blacklist of specific domains. We do not publish it. Publishing a list of what is protected is a map for the people we are protecting it from.
If you have a legitimate need
Section titled “If you have a legitimate need”Plenty of real businesses need data from blocked categories. Academic researchers
need .edu. Compliance teams need bank sites. Public-records companies need
.gov.
Contact support and ask. We will run a KYC check covering who you are, what the business is, and what you intend to collect, then unblock what your case justifies. Approval is per-account and per-category, not blanket.
If a request fails unexpectedly
Section titled “If a request fails unexpectedly”A blocked destination fails at our edge, before a proxy is chosen. If a domain you think should work is failing consistently while others succeed, it may be on the ad-hoc list. Ask support rather than guessing. Retrying will not help, and neither will changing targeting.
The rest
Section titled “The rest”Everything else in your agreement still applies. In short: do not use these proxies for fraud, for unauthorized access to systems you do not own, for harassment, or for anything you would not be willing to describe to us.
We would rather have the conversation up front than terminate an account after the fact, so if you are unsure whether a use case is acceptable, ask first.
Was this page helpful?
Thanks — that helps us fix it.