Guide
IP Reputation and Blacklists: How to Tell if a Proxy IP Is Clean
You can tell whether a proxy IP is clean by looking up its exit IP in DNSBLs, checking its ASN and IP type, and running a small test on the target site. The signals behind IP reputation, blacklist checks with dig and Python, what Spamhaus answer codes mean, what to do with a dirty IP, and which product fits which job.
Key takeaways
- IP reputation is how trustworthy websites, mail servers and security services consider an IP address to be, based on the traffic it has sent in the past.
- When checking a proxy IP, look up the exit IP you get through the proxy, not the gateway address; then check DNSBL listings, the ASN and IP type, and the rate of 403, 429 and CAPTCHA on the target site.
- In Spamhaus ZEN, an SBL or XBL listing means abuse or a compromised device; a PBL listing is normal for home and mobile IP ranges and is not a problem for web work.
- Spamhaus returns 127.255.255.254 to queries from public DNS resolvers; this is an error code, not a listing, and the test should be repeated from your own resolver.
- With a rotating product, the next request takes you off a listed IP; with a static product, check the IP right after buying, before tying it to an account, and contact support if it has an SBL or XBL listing.
IP reputation is how trustworthy websites, mail servers and security services consider an IP address to be, based on the traffic it has sent in the past. To find out whether a proxy IP is clean, you get the exit IP, look it up in DNS-based blacklists (DNSBLs), check the IP’s ASN and type, and run a small test on the target site. Showing up on a blacklist does not always mean the IP has been abused; what matters is which list it appears on and with which code.
“Clean IP” is a phrase you hear a lot in the proxy world, but it does not map to a single measurement. An IP can be clean on email blacklists and still look suspicious to a social media platform because of its history. That is why the check has to match the job you plan to use the IP for.
What is IP reputation, and what does it mean to be blacklisted?
Every IP address has a history: which network it belongs to, who has used it, which sites it has sent requests to and how often, and whether anyone has complained about it. Security services collect this data and assign the IP a reputation. Websites then use that reputation to decide whether to let a request straight through, show a CAPTCHA or block it.
A blacklist is a published list of IPs associated with abuse. The best known are the DNSBLs used in email. A mail server looks up the connecting IP in these lists, and if the IP is listed, it rejects the message or sends it to spam. How DNSBLs are queried and how they answer is defined in RFC 5782.
The reputation data websites use is usually not public. Bot protection and fraud prevention services keep their own measurements, and you cannot see from the outside exactly how they score a given IP. Public lists are therefore useful as a first check. The final answer comes from how the target site responds to the IP.
Why does an IP end up on a blacklist?
These are the most common reasons an IP gets blacklisted:
- Spam. If bulk, unsolicited email has gone out from the IP, or mail from it has reached trap addresses (spam traps), it lands on email blacklists.
- A compromised device. A computer, router or server infected with malware sends botnet traffic without its owner knowing. Lists such as Spamhaus XBL collect these IPs.
- Attack and scanning traffic. IPs that make brute-force login attempts, port scans or exploit attempts get reported to community abuse databases.
- A previous user. A static IP may have been used by someone else before it was assigned to you. In rotating pools, the same IP serves many users during the day, so what one person does affects everyone else using that IP.
- Network policy. Some lists flag the type of network, not abuse. Spamhaus PBL lists IP ranges that should not send email directly, such as home and mobile connections. Being on this list does not mean the IP is “dirty”.
That last point is where proxy users most often get it wrong. Most residential and mobile IPs show up on the PBL because they are home and carrier connections. For web scraping, price tracking or social media work, this has no effect.
Which signals determine IP reputation?
Sites do not rely on a single list; they weigh several signals together. The table below shows these signals and how you can check each one:
| Signal | What it shows | How to check |
|---|---|---|
| DNSBL listing | Whether the IP is on spam, botnet or policy lists | A DNS query with dig, or the list’s own lookup page |
| Community abuse reports | Whether attacks, scans or brute-force attempts from the IP have been reported | The IP lookup in report databases |
| ASN and IP type | Whether the IP belongs to a data center, a home internet provider or a mobile carrier | ISP and organization details in the IP lookup tool |
| Geolocation consistency | Whether the IP’s country and city match the location you expect | The IP lookup tool and the country the target site shows |
| Reverse DNS (PTR) record | Whether the IP maps to a name that looks like a server or a home connection | dig -x <IP> |
| History on the target site | Whether the IP has hit rate limits on that site before | A small-volume test; the rate of 403, 429 and CAPTCHA |
The ASN often matters more than the lists. Many sites treat traffic from data center ASNs more strictly, even when the IP is on no blacklist at all. How sites treat residential and datacenter IPs differently is covered in the residential vs datacenter comparison.
How do you check whether a proxy IP is blacklisted?
There are three steps: find the proxy’s real exit IP, look that IP up in the lists, then run a small test on the target site.
The gateway address you connect to is not the IP that websites see. So first, find the exit IP:
curl -s -x "http://USER:[email protected]:8989" https://api.ipify.org
Enter the returned IP in the IP lookup tool and check the country, city, ISP and organization. If you bought a residential product, the ISP field should show a home internet provider. To compare with your own connection’s IP, use the what is my IP tool.
Next, look the IP up in a DNSBL. You reverse the IP’s octets and put them in front of the list’s domain name. For 203.0.113.25, the Spamhaus ZEN query looks like this:
dig +short 25.113.0.203.zen.spamhaus.org A
An empty answer (NXDOMAIN) means the IP is not on this list. An answer in the form 127.0.0.x means it is listed, and the last number tells you which sublist. To test that your query works, use 127.0.0.2, an address the lists always keep listed: dig +short 2.0.0.127.zen.spamhaus.org A should return an answer.
Spamhaus does not return real results for queries coming from public DNS resolvers such as Google or Cloudflare; it returns 127.255.255.254 instead. Free queries are only allowed for non-commercial use. Run the test from your own resolver or your internet provider’s DNS, and see the Spamhaus DNSBL usage page for the rules.
If you are checking more than one IP, a short Python script using only the standard library does the same job:
import ipaddress
import socket
LISTS = ["zen.spamhaus.org", "bl.spamcop.net"]
def check(ip: str) -> dict:
reversed_ip = ".".join(reversed(str(ipaddress.IPv4Address(ip)).split(".")))
results = {}
for zone in LISTS:
try:
answer = socket.gethostbyname(f"{reversed_ip}.{zone}")
results[zone] = answer
except socket.gaierror:
results[zone] = None # not listed
return results
for ip in ["203.0.113.25", "198.51.100.7"]:
print(ip, check(ip))
For each IP, the script prints which code came back from which list. None means the IP is not listed. If you are checking a rotating pool, take a sample rather than looking at a single IP: pulling the exit IP 20–30 times and looking up each one gives you a more accurate picture of the pool as a whole.
How do you read a blacklist result?
Spamhaus ZEN returns several lists in a single query. According to Spamhaus’s own table, the answer codes read as follows:
| Answer | List | Meaning | What to do for proxy use |
|---|---|---|---|
| Empty (NXDOMAIN) | None | The IP is not on these lists | Move on to a small test on the target site |
127.0.0.2, 127.0.0.9 | SBL, DROP | Flagged as a spam source or malicious network | Do not use the IP for accounts or sensitive work |
127.0.0.3 | CSS | Low-reputation email sending | May have limited impact outside email; test on the target |
127.0.0.4 | XBL | Compromised device or botnet traffic | Do not use for account logins or long sessions |
127.0.0.10, 127.0.0.11 | PBL | Home or dynamic IP range that should not send email | Normal for residential and mobile IPs; not a problem for web work |
127.255.255.252–.255 | Error | Malformed query, public resolver or excessive queries | Says nothing about the IP; repeat the query from your own resolver |
Showing up on one list is different from showing up on several. An IP with an SBL or XBL listing very likely also scores low in the closed reputation systems websites use. A residential IP that appears only on the PBL, on the other hand, is a normal home connection as far as web traffic is concerned.
Not being listed does not mean the IP will work on every site either. Closed reputation systems use different data. The final call comes from a test on the target site: request a few pages and look at the rate of 403, 429 and CAPTCHA. To tell whether these error codes come from the proxy or from the target site, see the proxy error codes guide.
What should you do if a proxy IP is blacklisted?
That depends on the type of product.
With a rotating product (rotating residential, rotating datacenter, rotating mobile), one listed IP in the pool is not a big problem. You move to another IP on the next request or when the sticky period ends. If you use sticky sessions, you can get a new IP by changing the session ID. How session length affects IP selection is explained in the sticky vs rotating proxy guide.
With a static product (static residential, static datacenter, ISP proxy), the IP stays with you for the whole package period. So run the check right after you buy, before you tie the IP to any account. If you see an SBL or XBL listing, contact the support team before you start using the IP; you can discuss the options for replacing it with them. A PBL listing alone is not a reason to replace a residential IP.
If the IP got listed after you had been using it for a while, look at your own traffic first. The reputation of a static IP depends largely on the traffic you send. Requests that are too fast, too many simultaneous connections or repeated failed login attempts will get an IP flagged quickly. If you switch IPs without lowering your request rate, the new IP will get flagged the same way.
Most lists have a delisting process. It is handled by the network that owns the IP; as a proxy user, you are not expected to file a request on your own.
Which proxy type should you choose when reputation matters?
How much IP reputation matters depends on the job. When you collect data from public pages, the history of individual IPs does not matter much; what you look at is the pool’s overall success rate. For account logins, ad dashboards or jobs that need long sessions, the history of a single IP directly affects the outcome.
| Job | Recommended product | Why, in terms of reputation |
|---|---|---|
| Accounts you log in to from the same IP over a long period | Static Residential IPv4 | The IP is dedicated to you and does not change during the package period; your own traffic shapes its reputation |
| Jobs in the US that need a stable, ISP-registered static IP | ISP Proxy | Static IPv4 registered to an internet service provider; for long sessions and ad verification |
| Data collection on sites where blocking is common, SERP and price tracking | Rotating Residential IPv4 | If you land on a dirty IP, you move to another one on the next request |
| Targets that accept datacenter IPs, and a fixed address to add to a whitelist | Static Datacenter IPv4 | Fast and fixed, but some sites check data center ASNs more strictly |
| Mobile app and social media testing | Mobile proxy | Carrier IPs are shared among many users because of CGNAT; sites are more cautious about blocking these IPs wholesale |
At WeProxy, residential IPs come from a consent-based SDK partnership program. Türkiye static residential packages are on the Türk Telekom and Vodafone networks. ISP Proxy is currently offered in the US location, with Retail ISP and Mobile ISP packages. The differences between ISP and datacenter IPs are compared in detail in the ISP proxy vs datacenter proxy article.
IPs taken from open proxy lists fall outside this table. These addresses are used by many people at the same time, and most of them end up on blacklists quickly. The reasons are explained in free vs paid proxies.
How do you protect an IP’s reputation?
An IP that comes back clean from the lists can still get flagged quickly if it is misused. When you use static and sticky IPs, keep these points in mind:
- Tune your request rate to the target. When you get a
429, increase the wait time and respect theRetry-Afterheader. Sending dozens of requests per second from the same IP will get you rate-limited, even if the IP is on no list. - Keep jobs separate. Do not use the static IP you log in to accounts with for bulk data collection. A block in one job also affects the other job on the same IP.
- Match the IP to the session. Connecting to an account from an IP in a different country every time triggers security checks, even when the IP is clean. For work that needs a fixed location, use a static or sticky IP.
- Protect access. If someone else gets your proxy credentials, their traffic shapes your IP’s reputation too. Keep the username and password in environment variables instead of hardcoding them in scripts, and use an IP whitelist if your product supports it. Which product supports which method is listed in the proxy authentication guide.
- Check regularly. Look up static IPs with the Python script above every week, or before tying them to a new account. If you log the results with the date and IP, you can see when a problem started.
Using a proxy to send email harms IP reputation faster than anything else, and spam-like sending is prohibited under the acceptable use policy. When collecting data, follow the target site’s terms and its robots.txt rules, and if you process personal data, meet your obligations under GDPR and other applicable data protection laws.
Frequently asked questions
How do I know if a proxy IP is blacklisted?
First, send a request through the proxy to an address such as api.ipify.org to get the exit IP. Reverse that IP’s octets, put them in front of a list such as zen.spamhaus.org and query it with dig; an empty answer means the IP is not listed, and a 127.0.0.x answer means it is. Then check the ASN with an IP lookup tool and run a small test on the target site.
Is it a problem if a residential proxy IP appears on Spamhaus PBL?
No. The PBL lists IP ranges that should not send email directly, such as home and mobile connections, and it does not indicate abuse. Most residential and mobile IPs appear on this list. It has no effect on web scraping, price tracking or social media work. The listings that point to a problem are SBL, CSS and XBL.
What does a 127.255.255.254 answer mean in a Spamhaus query?
It is an error code, not a listing. Spamhaus does not return real results for queries from public DNS resolvers such as Google or Cloudflare and returns this code instead. 127.255.255.252 indicates a mistyped list name, and 127.255.255.255 indicates excessive queries. Repeat the test from your own resolver or your internet provider’s DNS.
Will an IP that is not blacklisted work on every site?
Not necessarily. Public lists mostly measure email abuse, while websites use their own bot protection and fraud prevention data and also look at the ASN type. So test an IP that comes back clean from the lists on a few pages of the target site and watch the rate of 403, 429 and CAPTCHA.
What should I do if the static proxy IP I bought is blacklisted?
Before tying the IP to an account, check which list it appears on and with which code. If it has an abuse listing such as SBL or XBL, contact the support team and ask about the options for replacing it. A PBL listing alone is not a reason to replace a residential IP. If the IP got listed after you had been using it for a while, check your own request rate first.









