Was verursacht Proxy-Sperren und wie man sie vermeidet

Why Do Proxies Get Banned?

A proxy ban occurs when a target website blocks traffic from a specific IP address or range of addresses. The website has determined — through various signals — that the traffic coming from that IP is automated, abusive, or otherwise unwanted, and it refuses to serve further requests from it.

Understanding why bans happen is the first step toward preventing them. Whether you are scraping websites, monitoring prices, or tracking SERPs, knowing the detection signals and how to mitigate them will dramatically improve your success rates.

Common Ban Triggers

1. Excessive Request Volume

The most basic detection signal is request rate. If a single IP sends 100 requests per second to the same website, it is clearly not a human browsing. Most websites set rate limits — thresholds that trigger blocks or CAPTCHAs when exceeded. These limits vary widely: some sites allow 10 requests per minute per IP, while others tolerate hundreds.

2. Known Proxy/Datacenter IP Ranges

IP intelligence services (MaxMind, IPinfo, IP2Location) classify IPs by type. Datacenter IPs are easy to identify because they belong to hosting provider ASNs (AWS, Google Cloud, OVH). Many websites automatically block or challenge all traffic from known datacenter IP ranges. This is why residential proxies have higher success rates — their IPs are classified as consumer connections.

3. IP Reputation Blacklists

Multiple services maintain blacklists of IP addresses known to be used for scraping, spamming, or other automated activity. When your proxy IP appears on these lists, websites that subscribe to the blacklist service will block you preemptively — even before you send a single request. Pool health monitoring helps providers remove blacklisted IPs from rotation.

4. Suspicious Request Patterns

Even at reasonable request rates, your traffic pattern can reveal automation:

• Uniform timing: Requests arriving at exact intervals (every 2.0 seconds) instead of the random intervals of human browsing
• Sequential access: Visiting pages in alphabetical or numerical order rather than following natural navigation paths
• No sub-resource loading: Real browsers load images, CSS, JavaScript, and fonts — scrapers that fetch only HTML stand out
• Missing referrer headers: Browsers always send a referrer when navigating between pages; scrapers often don't
• Abnormal depth-first patterns: Crawling deep into a category before moving to the next, rather than browsing like a human

5. Mismatched Fingerprints

Anti-bot systems correlate multiple signals to build a visitor profile. When these signals contradict each other, the visitor is flagged:

• Geo mismatch: IP says Germany, but the browser timezone is US Pacific and Accept-Language is en-US
• TLS fingerprint: The TLS Client Hello signature doesn't match the claimed browser (e.g., Python requests library claiming to be Chrome)
• JavaScript execution: Bot detection scripts test for browser APIs that headless browsers may not fully implement
• WebRTC leak: WebRTC can expose the real IP behind a proxy if not properly configured

6. Concentrated Subnet Traffic

If multiple IPs from the same /24 subnet (e.g., 185.23.100.1 through 185.23.100.254) all hit the same website, the site may block the entire subnet. Good IP rotation algorithms ensure subnet diversity between consecutive requests.

7. Session and Cookie Anomalies

Websites set cookies on the first visit and expect them on subsequent requests. Scrapers that don't maintain cookies, that present expired cookies, or that show inconsistent session state (logged in on one request, anonymous on the next) trigger suspicion.

Types of Bans and Blocks

Block Type	How It Looks	Severity	Recovery
CAPTCHA challenge	CAPTCHA page instead of content	Soft block	Rotate IP, slow down
HTTP 403 Forbidden	Access denied response	Medium block	Rotate IP, change fingerprint
HTTP 429 Too Many Requests	Rate limit exceeded	Soft block	Wait and retry, reduce rate
Empty/corrupted response	Blank page or garbage data	Stealth block	Verify with different IP
Redirect to block page	Sent to a "blocked" notice	Medium block	Rotate IP, check headers
IP blacklist	Connection timeout or reset	Hard block	IP is burned, use different one
Subnet/ASN ban	All IPs in range blocked	Hard block	Switch to different ASN

Prevention Strategies

Use Residential Proxies for Protected Targets

Residential proxies have IPs assigned by ISPs to real households. They pass ASN-level checks that block datacenter IPs. For websites with strong anti-bot protection, residential proxies are the baseline requirement. For the most aggressive targets, mobile proxies offer even higher trust due to CGNAT IP sharing.

Implement Smart Rate Limiting

Don't hit the target as fast as your connection allows. Instead:

• Research the target's rate limits (try escalating request frequency until you see 429s or CAPTCHAs)
• Add random delays between requests (e.g., 1-5 seconds with jitter)
• Distribute requests across time rather than sending them in bursts
• Use different rate limits for different endpoints (search pages vs product pages)

import time
import random
import requests
PROXY = "http://USERNAME:PASSWORD@gate.proxyhat.com:8080"
for url in urls:
    resp = requests.get(
        url,
        proxies={"http": PROXY, "https": PROXY},
        timeout=15,
    )
    # Random delay between 1.5 and 4.5 seconds
    time.sleep(random.uniform(1.5, 4.5))

Rotate IPs Intelligently

IP rotation distributes your traffic across many addresses. But rotation must be combined with other strategies:

• Rotate per-request for independent page fetches
• Use sticky sessions for multi-step workflows requiring session continuity
• Ensure subnet diversity — don't send consecutive requests from the same /24 range
• Match rotation strategy to the target's sensitivity — more aggressive sites need faster rotation

Set Realistic Headers

Every request should include headers that match a real browser:

headers = {
    "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36",
    "Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8",
    "Accept-Language": "en-US,en;q=0.9",
    "Accept-Encoding": "gzip, deflate, br",
    "Connection": "keep-alive",
    "Upgrade-Insecure-Requests": "1",
    "Sec-Fetch-Dest": "document",
    "Sec-Fetch-Mode": "navigate",
    "Sec-Fetch-Site": "none",
    "Sec-Fetch-User": "?1",
}

Rotate User-Agent strings across a set of current, popular browsers. Ensure the User-Agent matches the TLS fingerprint — claiming to be Chrome while sending a Python TLS signature is an instant red flag.

Align Geo Signals

When using geo-targeted proxies, align all request metadata with the proxy's location:

• Set Accept-Language to match the country's primary language
• If using browser automation, set the timezone to match the proxy's geography
• Disable WebRTC to prevent real-IP leaks

Handle Cookies and Sessions Properly

Maintain cookies across requests within a session. Use a session object (like requests.Session() in Python) that automatically handles cookie persistence. When rotating IPs, also start a fresh cookie jar — don't carry cookies from one IP to another, as this creates inconsistency.

Recovery Techniques

Detecting Bans Early

Don't wait until your entire pipeline fails. Monitor for ban signals:

• Track success rate per target domain — a sudden drop indicates bans are starting
• Watch for CAPTCHA pages (check response body for CAPTCHA indicators)
• Monitor response sizes — blocked responses are often much smaller than real pages
• Check response times — some sites intentionally slow responses to suspected bots (tarpit)

Implementing Retry Logic

import requests
from time import sleep
PROXY = "http://USERNAME:PASSWORD@gate.proxyhat.com:8080"
def fetch_with_retry(url, max_retries=3):
    for attempt in range(max_retries):
        resp = requests.get(
            url,
            proxies={"http": PROXY, "https": PROXY},
            timeout=15,
        )
        if resp.status_code == 200 and len(resp.text) > 1000:
            return resp
        # Exponential backoff before retry (new IP via rotation)
        sleep(2 ** attempt)
    return None

Escalation Strategy

When blocks persist, escalate your approach:

1. First: Reduce request rate and add more randomized delays
2. Second: Switch from datacenter to residential proxies
3. Third: Add browser automation (Puppeteer/Playwright) to execute JavaScript and pass browser checks
4. Fourth: Implement full fingerprint management (TLS, canvas, WebGL)
5. Fifth: Use mobile proxies for the highest-trust IP classification

Key takeaway: Proxy bans are caused by a combination of signals — not just the IP address. Preventing bans requires a holistic approach: quality proxies with smart rotation, realistic request patterns, proper headers, and consistent fingerprints. When bans do occur, detect them early and escalate your strategy incrementally.

Frequently Asked Questions

How long do proxy bans typically last?

It varies by target. Some sites block IPs for minutes or hours, others for days or permanently. Rate-limit blocks (429) usually expire within minutes. IP blacklists can persist for months. With rotating proxies, ban duration is less relevant because you automatically get a fresh IP.

Can rotating proxies prevent all bans?

Rotation prevents IP-based bans from cascading, but it doesn't address fingerprint-based or behavior-based detection. You need rotation plus realistic request patterns, proper headers, and consistent browser fingerprints.

Which proxy type is least likely to get banned?

Mobile proxies have the lowest ban rate because mobile IPs are shared by many real users via CGNAT. Residential proxies are next, followed by ISP proxies. Datacenter proxies have the highest ban rate on protected sites.

How do I know if my proxy IP is already blacklisted?

Test the IP against your target before starting a large job. Send a single request and verify you get a normal response. You can also check IPs against public blacklist services, though these don't cover all private blacklists that websites maintain.

Should I use the same proxy for all my targets?

No. Different targets have different sensitivities. Use dedicated proxies for high-value, persistent tasks and shared rotating proxies for bulk data collection. Match proxy type and strategy to each target's protection level.