IP Reputation
A judgement a site or a vendor makes about an address before it looks at your request. Mostly it is a judgement about the range, not about you.
Reputation is not a number stored somewhere with your name on it. It is a conclusion a defence system reaches from what it already knows: which organisation owns the range, whether it is a hosting network or a consumer one, what traffic has come from it recently and whether it appears on public lists.
The most important input is the least personal one. An address in a datacenter range carries the reputation of that range, and it carries it from the first request, before you have done anything. This is why a fresh datacenter address can be refused instantly while a residential address with a longer history passes.
What you can influence is narrow: pace, headers, whether you behave like the client you claim to be. What you cannot influence is who owned the address before you and what they did with it, and on shared pools that history arrives with the address.
Reputation is also not one thing. A payment processor, an ad network and a marketplace weigh the same address differently, and an address that is unwelcome on one is unremarkable on another. Testing on your actual target is the only measurement that means anything.
What feeds the judgement
Ownership comes first. Every address belongs to an autonomous system, and whether that system is a hosting provider or a consumer ISP is public information available to any site in a lookup.
History comes second: abuse reports, appearances on public blocklists, and whatever the site itself recorded from that range in the past. A large platform mostly trusts its own observations over anyone else’s list.
Context comes third, and it is where most surprises live. The same address arriving with a browser fingerprint and a plausible language header reads differently from the same address making a hundred identical requests a minute.
What actually changes the outcome
In order of how much difference it makes, cheapest first:
Checking what a target sees
# what the address looks like on paper
curl -s -x login_c_US:password@proxy.sotaproxy.com:10000 https://ipinfo.io/json
# the only measurement that matters: the target itself
curl -o /dev/null -s -w "%{http_code}
" -x login:password@YOUR-DC-IP:50100 https://target.example/
curl -o /dev/null -s -w "%{http_code}
" -x login_c_US:password@proxy.sotaproxy.com:10000 https://target.example/- Address class is the single largest lever. Moving from datacenter to residential changes the organisation behind the address, which is most of what the judgement is made from.
- ISP addresses sit in the middle by design: a consumer registration on server hardware, which is why they pass where datacenter ranges do not.
- Pace and headers are the parts you own. They will not rescue a refused range, and they will spoil a good one.
What reputation is not
It is not a score you can look up
Public checkers report list membership, not what your target thinks. The two disagree constantly.
It is not permanent
Ranges are reassigned and observations age out. An address refused last year is not necessarily refused today.
It is not the same everywhere
A marketplace and a bank weigh the same address differently, and neither publishes its weights.
It is not something we can raise for you
We can sell you an address in a different class. Nobody can sell you a better opinion held by somebody else’s system.
See this in practice
Ready to use ip reputation?
SotaProxy gives you access to rotating residential, mobile, datacenter, and ISP proxies. No minimum commitment.
Get started