Is it blocked, or is it your setup?
Two quick tests tell you which:
Test | Result | What it means |
Open the same site with the proxy switched off | It loads | The site is fine; the problem is the proxy |
Open a different site through the proxy | It loads | Your proxy works — this one destination is blocked or restricted |
Open a different site through the proxy | It also fails | A configuration problem, not a block |
Blocked by default
These are restricted on all our proxies until you ask for them to be opened:
All .gov domains, including sites such as irs.gov.
Outlook and other Microsoft services, including Microsoft Teams.
Some webmail providers, such as mail.com, may also be blacklisted on individual proxies.
The block applies to new proxies too. If you buy more proxies later, they start blocked, even if an earlier proxy on your account was already approved.
Outbound email is a separate rule
SMTP traffic on port 25 is blocked on all proxies and cannot be opened by request. Reading your own inbox through a proxy is fine; sending bulk or unsolicited email is not permitted.
How to request access
Contact support with the exact URLs you need. Approval covers only the domains you list, so include every one you use.
Explain what you need it for in one line — for example, signing in to your own work mailbox, or checking your own tax account. Requests without a reason take longer.
Include the proxy IP addresses the approval should apply to.
Wait for confirmation. Requests are usually reviewed quickly, and access works within a few minutes of approval.
If you need many domains opened, send them as one list rather than as separate requests — it is processed as a single bulk whitelist. There is no fixed limit on how many you can ask for.
If the destination is not blocked
When other sites fail through the proxy too, work through these:
Set the proxy type to HTTP. Most services that misbehave over SOCKS5 work normally over HTTP.
Try another port — 2534, 3389 or 5433 — keeping the same IP, username and password.
Try a different IP from your package. If the second one works, the first address is blacklisted by that site and should be replaced.
Turn off any "proxy DNS" option in your extension or application. It conflicts with some services.
Test in a private window or another browser to rule out a cached session or a browser extension.
Re-check the password character by character, or switch the package to IP authorization.
Play Store and Android emulators
Try a different IP address from your package first — the Play Store rejects some address ranges outright.
Check whether the emulator needs SOCKS5; several only support that type.
Turn off proxy DNS in the emulator's network settings.
What to send support
The exact URL that fails, and whether it fails on every proxy or only one.
The proxy IP address and port.
The browser, application or emulator, and your operating system.
The error message or a screenshot of what you see.