Acceptable use
Some destinations are blocked on every account by default, and so is targeting some locations and networks. 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 | .gov and .mil domains, with some public-information sites left open |
| 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.
Blocked locations and networks
Section titled “Blocked locations and networks”A request whose targeting asks for one of these is refused, whatever the
destination. So, rarely, is a request whose destination address is on a blocked
network. It does not matter how the targeting is sent: options on the
password, X-Rayobyte-* headers and sticky sessions are all checked.
| Blocked | Includes |
|---|---|
| Sanctioned countries | Cuba (CU), Iran (IR), North Korea (KP), Syria (SY) |
| Occupied regions of Ukraine | Crimea, including Sevastopol, and the Donetsk and Luhansk regions |
| Washington, DC | The District of Columbia and several federal government and military sites in Virginia and Maryland |
| Sensitive networks, by ASN | Networks run by governments, the military, law enforcement, banks and payment companies, healthcare providers, critical infrastructure operators and international organizations |
Washington State (-region-washington) is not affected.
The proxy refuses the request before it chooses an exit and answers 451, with
the header X-Rayobyte-Block-Reason: targeting and this body:
Targeting this network or location is not permitted under our Acceptable Use Policy.Over SOCKS5 the reply is 0x05. A refused request is not billed. Retrying it
returns the same 451, and so does connecting through a different entry point.
The sanctioned countries and the occupied regions of Ukraine do not appear in the dashboard’s Geolocation picker. We do not publish the list of blocked networks, for the same reason we do not publish the domain list.
If one of these blocks affects a legitimate business purpose, ask support to review your use case.
If you have a legitimate need
Section titled “If you have a legitimate need”For a blocked domain
Section titled “For a blocked domain”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.
For a location or network
Section titled “For a location or network”If a blocked location or network gets in the way of a legitimate business purpose, email [email protected] with what you need to target and why, and we’ll review your use case. The sanctioned-country and occupied-region blocks follow sanctions law.
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.
A 451 with the header X-Rayobyte-Block-Reason: targeting comes from our
location and network blocks. Usually your
targeting options asked for a blocked location or network. Rarely, the
destination address is on a blocked network.
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.