Blocked Destinations
Stop a credential from reaching specific hosts or ports using blocklist presets and custom host/port rules, including what a blocked request looks like to your client.
Blocked destinations let you decide where a credential's traffic is allowed to go. You apply ready-made blocklist presets, add your own custom host and port rules, or both. The gateway checks the rules before it opens the outbound connection, so a blocked request never leaves the network and uses no data.
Because you pay per GB, this is a practical way to keep ad and tracker hosts out of a scraping job and cut what you pull down.
Set it up
Open the credential's Blocked tab
Go to Services, open your Residential service, and select the Sub-users tab. Open the credential you want to restrict and switch to its Blocked tab. Rules apply to that one credential, so different tools on the same package can have different restrictions.
Apply blocklist presets
Presets are named sets of hosts that Proxio maintains, plus any private presets you have saved. Each one is a chip showing its name and roughly how many hosts it covers. Click a chip to apply it, click again to remove it.
Add custom rules
Pick Host or Port, type the value, and press Add.
- A host rule matches at label boundaries, so a rule for
doubleclick.netalso blocksads.doubleclick.netbut leavesnotdoubleclick.netalone. You do not need to list subdomains separately. - A port rule blocks that destination port outright, whatever the host. Use
it to keep a credential off
25or any other port you never intend to reach.
You can keep up to 100 custom rules on one credential. Remove a rule with the trash icon on its chip.
Presets
A preset saves you from re-typing the same list on every credential. Two kinds show up in the Blocked tab:
| Kind | Who maintains it | Who sees it |
|---|---|---|
| Built-in | Proxio | Every account |
| Private | You | Only you |
To build your own, choose New preset, give it a name, and paste your hosts one per line or comma-separated. The same label-boundary matching applies. You can keep up to 50 private presets per account, and reuse each across as many credentials as you like. Deleting a private preset removes it from your catalog; built-in presets stay put.
What a blocked request looks like
The block happens before the outbound connection is dialed, so your client sees a refusal rather than a response from the destination:
- Over HTTP/HTTPS:
403 Forbidden, carrying anX-Proxio-Blocked: customer-ruleheader. Match on that header to tell your own rule apart from a403the destination sent back. - Over SOCKS5: a generic connection-refused reply. SOCKS5 has no headers, so test the same request over HTTP when you need to know exactly why it failed.
Blocked requests are never retried, and they transfer no data.
Rules and limits
- Rules only ever remove access. They stack on top of the restrictions Proxio applies network-wide, and cannot open up a destination those restrictions block. See Acceptable Use.
- Proxio's own infrastructure hosts cannot be added as rules.
- A change takes effect within about 30 seconds while it propagates to the gateway.
- Limits: 100 custom rules per credential, 50 private presets per account.