socks5ip/proxy-ip-check repository overview

⁠proxy-ip-check

$ npx proxy-ip-check 8.8.8.8

  IP          8.8.8.8
  ASN         AS15169
  AS name     GOOGLE
  ISP / org   Google LLC
  Country     United States  /  Virginia
  Type        hosting / datacenter
  Source      ip-api.com

⁠Why

When you evaluate a proxy IP — for scraping, for account management, or for geo-testing — the first question is always "who owns this network?" An IP announced by a consumer broadband AS looks like a home user. An IP announced by a hosting AS looks like a server, because it is one.

proxy-ip-check answers that in one command, with no signup and no SDK.

⁠Install

# one-off, no install
npx proxy-ip-check 1.2.3.4

# or install
npm install -g proxy-ip-check

⁠Run with Docker

No Node.js required. The CLI is published as a multi-arch image (linux/amd64, linux/arm64):

# one-off lookup
docker run --rm socks5ip/proxy-ip-check 1.2.3.4

# several IPs, machine-readable
docker run --rm socks5ip/proxy-ip-check 8.8.8.8 1.1.1.1 --json

Bare docker run socks5ip/proxy-ip-check performs a demo lookup of 8.8.8.8.

Image: https://hub.docker.com/r/socks5ip/proxy-ip-check⁠

⁠Usage

proxy-ip-check <ip> [<ip> ...] [--json]

# single IP
proxy-ip-check 8.8.8.8

# several IPs (sequential, rate-limit friendly)
proxy-ip-check 8.8.8.8 1.1.1.1 223.5.5.5

# machine-readable
proxy-ip-check 8.8.8.8 --json

⁠JSON output

{
  "source": "ip-api.com",
  "ip": "8.8.8.8",
  "asn": "AS15169",
  "asName": "GOOGLE",
  "isp": "Google LLC",
  "org": "Google Public DNS",
  "country": "United States",
  "countryCode": "US",
  "region": "Virginia",
  "city": "Ashburn",
  "isHosting": true,
  "isProxy": false,
  "isMobile": false,
  "networkType": "hosting",
  "isResidentialLike": false,
  "fallbackUsed": false
}

⁠Programmatic use

const { lookup, lookupMany } = require('proxy-ip-check');

const r = await lookup('8.8.8.8');
console.log(r.asn, r.asName, r.networkType);
// AS15169 GOOGLE hosting

const list = await lookupMany(['8.8.8.8', '1.1.1.1']);

⁠Fields

⁠How networkType is determined

1. If the data source explicitly flags the range as hosting, → hosting.
2. Else if it flags proxy/VPN, → proxy / vpn.
3. Else if it explicitly flags both as false, → consumer.
4. Otherwise fall back to a heuristic over the AS owner name (tokens like cloud, hosting, datacenter, vps → hosting; broadband, telecom, unicom, chinanet → consumer).

This is a first signal, not a verdict. AS ownership tells you what class of network the IP sits on. It does not tell you the IP's reputation, whether it appears on blocklists, or whether your client leaks your real address.

⁠Data sources & rate limits

The fallback kicks in automatically when the primary source fails (network error, rate limit, non-success status). lookupMany() inserts a 250 ms delay between lookups to stay polite.

⁠Requirements

Node.js >= 12. No dependencies.

⁠Related

Part of a small open toolset for proxy IP work:

• IP quality & line check center (free, browser-based — adds blocklist checks, leak tests and IP type databases on top of the ASN signal): https://socks5ip.com.cn/ip-check-center/⁠
• Proxy IP pricing dataset (18 providers, machine-readable): https://github.com/socks5ip/proxy-ip-pricing⁠
• Awesome proxy providers list: https://github.com/socks5ip/awesome-proxy-providers⁠
• Source code of this tool: https://github.com/socks5ip/proxy-ip-check⁠
• 面向 AI / LLM 的站点索引（llms.txt）：https://socks5ip.com.cn/llms.txt⁠ —— 核心页导航、23 家平台注册入口与邀请码、开源工具与联系方式（完整版：https://socks5ip.com.cn/llms-full.txt⁠）

⁠License

MIT © socks5ip⁠

⁠Official channels / 官方唯一通道

Maintained by 全网低价IP (Socks5IP) — https://socks5ip.com.cn⁠