A 403 Forbidden with proxies means the website received your request, understood it, and decided not to serve it. Unlike a 407 (the proxy rejecting your credentials) or a 502 (a hop in the chain failing), a 403 comes from the destination. Something about the request made the site's access rules or bot protection refuse it. The most common reasons are the IP type, missing or unusual headers, the TLS or browser fingerprint, and request patterns that look automated.
The good news: you can isolate which of these it is with a few controlled tests, rather than buying more IPs and hoping.
Step 1: Confirm the 403 Comes from the Website
Run the request with curl -v. If you see "200 Connection established" before the 403, the proxy built the tunnel and the website sent the 403:
curl -v -x http://USERNAME:[email protected]:8080 https://example.com -o /dev/null 2>&1 | grep -E "^< HTTP"
# < HTTP/1.1 200 Connection established
# < HTTP/2 403Then look at the body and headers of the 403 response. A branded CDN or bot-protection page means an automated system decided; a plain "Forbidden" from the origin often means an IP or geography rule.
Step 2: Run the Same Request Without a Proxy
Send the identical request from your own connection. This single test splits the problem in two:
- 403 without the proxy too: the problem is your request, not the IP. Fix headers, fingerprint or the URL before touching proxies.
- 200 without the proxy, 403 with it: the site is reacting to the proxy IP or its location. Move to the IP-focused fixes below.
Fixing Header and Client Problems
Many 403s are triggered by default client signatures. Python requests announces itself as python-requests/2.x; curl sends curl/8.x. Some sites block those outright. Send what a browser sends:
import requests
PROXY = "http://USERNAME:[email protected]:8080"
headers = {
"User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36",
"Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8",
"Accept-Language": "en-US,en;q=0.9",
}
r = requests.get("https://example.com", headers=headers,
proxies={"http": PROXY, "https": PROXY}, timeout=30)
print(r.status_code)Headers alone won't fool advanced protection. Those systems also look at the TLS handshake and HTTP/2 settings, which differ between Python, Node and a real browser. If a site still returns 403 with browser headers, try the same URL in a real browser driven by Playwright or Selenium through the proxy. If that works, the block is fingerprint-based, not IP-based. Our browser fingerprinting guide explains what's being checked.
Fixing IP-Based 403s
Datacenter IP ranges are refused
Many sites block or challenge datacenter ranges as a class because few real visitors come from servers. If datacenter proxies get 403s and your home connection doesn't, switch the same job to residential proxies. The comparison in datacenter vs. residential proxies covers when each makes sense.
The country is restricted
Some content is licensed or legally limited to certain countries, and the site returns 403 elsewhere. Add country targeting to the username, for example USERNAME-country-us, and compare. If the site only serves one market, use that market's exits.
The specific IP has poor reputation
Individual IPs pick up reputation from previous traffic. With rotating proxies, retrying with a new IP is cheap: drop the session parameter or change its id. If one in ten requests gets 403 and a retry succeeds, that's IP reputation at work. Read what is IP reputation for the background.
Fixing Behavior-Based 403s
If the first few requests succeed and 403s appear later, the site is judging your behavior, not your starting point. Typical triggers:
- Too many requests from one IP or session in a short window. Rotate more often or slow down.
- Requesting deep URLs without ever loading the page that links to them, and with no Referer.
- Missing cookies that a real visit would have set on the first page.
- Perfectly regular timing. Add random delays between requests.
- Hitting paths that robots.txt disallows. Respect robots.txt, the site's terms and reasonable rate limits; see are proxies legal.
For a full checklist of what sites look at, see why proxies get blocked.
A Quick Diagnostic Table
- 403 everywhere, even without proxy: request or URL problem.
- 403 on datacenter, fine on home connection: IP type. Use residential.
- 403 from some countries only: geo restriction. Use country targeting.
- Random 403s that clear on retry: IP reputation. Rotate per request.
- 403 after N successful requests: rate or behavior. Slow down and rotate.
- 403 with plain client, fine in real browser: fingerprint. Use a browser.
Testing This with NodeProxies
Because NodeProxies is pay as you go with a $3 minimum and balance that never expires, you can run all of the tests above on a small budget: a 100 MB residential plan is enough to compare a datacenter IP, a residential IP and several countries against the same URL. Create an account, generate credentials in the dashboard, and use the proxy username builder to add country or session options without typos.
FAQ
Why do I get 403 Forbidden only when using a proxy?
The site is reacting to the proxy IP: its type (datacenter), its country, or its reputation. Try residential IPs, a different country, or a fresh IP on retry.
Is 403 the same as being banned?
Not necessarily. A 403 can be temporary and tied to one IP, one session or one burst of traffic. If it persists across fresh IPs and slower rates, the site is refusing that type of access and you should check its terms.
Can changing the User-Agent fix a 403?
Sometimes. It fixes blocks aimed at obvious library user agents. It won't fix blocks based on TLS fingerprints, IP type or behavior.
Does 403 mean my proxy credentials are wrong?
No. Wrong credentials give a 407 from the proxy. A 403 means the proxy worked and the website refused the request.
