Why sites are blocked
Residential IPs run on other people’s home internet connections, and misuse by one customer can cost every customer access. Orgo blocks ticketing sites because the network forbids buying tickets with bots, and so do the Terms of Service. The other categories use large amounts of data or put the shared network at risk.How a block matches a site
- An entry blocks that domain and every subdomain.
ticketmaster.comalso blockswww.ticketmaster.comandm.ticketmaster.com. - An entry never blocks a name that only contains it.
fast.comdoesn’t blockbreakfast.com. - YouTube itself isn’t blocked, because Google sign-in passes through
youtube.com. Its video comes fromgooglevideo.com, which is blocked, so YouTube pages open and videos don’t play.
Blocked sites
Each domain below also blocks all of its subdomains.Ticketing
Ticket sellers and resale sites.Video streaming
Streaming services, and the domains their video comes from.Music streaming
Music and radio streaming, and the domains their audio comes from.Gambling
Sportsbooks, casinos, poker, sweepstakes casinos and fantasy sports.Torrents
Torrent search and download sites.Speed tests
Speed test sites, which use as much data as they can by design.Sites that are never blocked
Orgo never blocks the hosts listed below. Neither Orgo’s list nor a block on one account can include them, or a domain they sit under. An entry blocks every subdomain, so a block ongoogle.com would take Gmail with it.
Only these hosts are covered. Signing in to a bank, payment or government site still fails, because the network blocks those sites itself, described in What the network blocks itself.
Webmail and platform domains
These domains are never blocked.
A separate site on one of these platforms can still be blocked, such as
tv.apple.com or music.youtube.com.
Hosts that webmail and sign-in run on
These hosts and everything under them are never blocked.The exit IP check
ipify.org and api.ipify.org are never blocked, because Orgo reads the computer’s exit IP from api.ipify.org.
What the network blocks itself
The network that carries residential traffic blocks these by default, for every account on Orgo, on top of Orgo’s list. Orgo doesn’t lift them, for one account or for everyone.- Government sites.
- Banks and payment sites.
- Apps that pay you for sharing your internet connection.
- Mail ports (SMTP and IMAP). Chrome doesn’t use these ports, so webmail in Chrome isn’t affected, and a mail program on the computer doesn’t go through the residential IP.
- UDP. While the residential IP is on, Chrome has QUIC (HTTP/3) turned off, and WebRTC sends no UDP outside the proxy.
Addresses that skip the residential IP
Only Google Chrome is set up to use the residential IP. The terminal, curl, other browsers and every other program on the computer keep its data center address. In Chrome, these addresses never use the residential IP. Chrome connects to them straight from the computer:
Orgo’s Chrome policy lists
127.0.0.1, localhost and <local>, which means names with no dot. Chrome itself always connects straight to loopback and link-local addresses, and to names ending in .localhost.
Every other address goes through the residential IP, private ones too: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 100.64.0.0/10 and 0.0.0.0.
While the residential IP is on, Chrome can’t reach machines on a private network. To open a server running on the computer, use
localhost or 127.0.0.1, not 0.0.0.0.What Chrome shows for a blocked site
- A blocked
https://site shows “This site can’t be reached” withERR_TUNNEL_CONNECTION_FAILED. - A blocked plain
http://address shows an error page instead. - A blocked site fails. It never goes out through the data center address instead.
- When every site fails this way, the account may be out of residential data. See When data runs out.
- A site that opens and then shows its own block or check page isn’t on these lists. That is the site’s own bot check, described in Bot checks.