An IP ban is a block a website or network service places on one IP address, or a range of addresses, so that requests from it are refused, often after brute-force login attempts, abusive request volumes or other rule-breaking. Bans can be temporary or permanent, and because ISPs reassign and share addresses, they can also catch innocent users.

A ban's scope can extend beyond a single IP, some sites block traffic at the ASN or IP-range level rather than one address at a time, which is why proxy providers with poor IP diversity can see rising ban rates even when rotating frequently.

Some sites use "soft" bans that serve deliberately wrong or degraded data instead of blocking the request outright, which can be harder to detect than an explicit block since the scrape appears to succeed while quietly returning unusable results.

How Websites Enforce an IP Ban

The block is a rule set at the network or server level, not in the page itself:

  • Web server rules: for example, nginx's deny directive, which accepts a single address or a CIDR range.
  • Host-level tools: TCP wrappers (/etc/hosts.deny), or log-monitoring tools like Fail2ban that ban addresses automatically.
  • CDN or WAF rules: these can block or challenge traffic by IP address, range, ASN or country.

Signs Your IP Has Been Banned

  • 403 Forbidden on pages that normally load. Logging in again makes no difference.
  • 429 Too Many Requests, a rate-limit block that may include a Retry-After header.
  • A CAPTCHA or JavaScript challenge instead of the content. These pages are often served with a 200 status, so check the page body, not just the status code.
  • The site works from a different network. If it does, the block is tied to your IP.