VPN / proxy / Tor intelligence

What does IP reputation data say about this address?

What this check is

Beyond who owns the network, reputation services track what an address is used for. This check asks an IP intelligence provider about the connecting address: is it a known VPN exit, a proxy, a Tor exit node, hosting space, crawler infrastructure, or an address with an abuse history or a high fraud score?

What Tells reads

The provider's flags for the connecting IP: VPN, proxy, Tor, datacenter, crawler, abuser
The provider's fraud score, when present

How to read your result

Fail: The address is flagged as Tor, a proxy, a VPN or crawler traffic, or carries a high fraud score. These are the heaviest network penalties in the verdict.
Warning: The address is hosting space or carries an abuse flag: suspicious company, not proof.
Pass: No flags raised.
Not available: The lookup was off or failed for this run.

Why it matters

Network reputation is the signal a browser cannot argue with, because it is not about the browser at all. It is also why the same automation can sail through from one connection and be stopped cold from another. Anyone debugging a bad score should read this row early: if the network is flagged, no amount of browser tuning fully compensates.

Where this matters most

Across the platforms Blowhorn works with, rated in the platform guide (H = matters a lot, M = contributes, L = no public evidence; tags mark vendor-stated, reported, or inferred evidence):

LinkedIn (M): VPN logins commonly trigger verification checkpoints [Reported]
X (M): VPN and Tor use raises lock and challenge rates, though neither is banned outright [Reported]
Reddit (H): many VPN exit nodes are pre-blocked by network security [Reported]
GitHub (M): signup and login over VPN or Tor more often draws verification [Inference]
Hacker News (M): accounts created over a VPN have been shadowbanned; moderators acknowledge the tradeoff [Reported]

Everywhere else in the set this one rates Low.

In your report

Find it in the checks table on the tool page, with the detail in the Network identity section. The same findings appear in the report JSON under verdict.reasons, and the agent guide explains how to read them programmatically.