Skip to content

Latest commit

 

History

4 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 

Repository files navigation

iplogs API: free VPN, proxy and Tor detection

API status No API key Free limit OpenAPI 3.1 Datasets: CC BY 4.0 IPv4 + IPv6

iplogs.com tells you whether an IPv4 or IPv6 address is a VPN, proxy, Tor exit, privacy relay or datacenter address. One request returns a verdict, a score from 0 to 1, the network behind the address and the evidence that produced the answer. It is free to use, with no API key and no sign-up.

This repository holds the public documentation, examples and links for the hosted API. The service is run by iplogs.com; its source code is private and is not published here.

On a published test of 1,043 addresses, the false-positive rate was 0.4%. The method and the misses are on /accuracy. The service tracks 4,190 VPN providers.

iplogs.com result for 23.234.89.127: Mullvad VPN server, VPN detected, 100/100, with key findings and technical details

Quick start

No install, no key. Run these in a terminal.

1. Check your own address

curl iplogs.com

2. Check any address

curl iplogs.com/8.8.8.8

curl, wget, HTTPie, xh and PowerShell get a short pretty-printed summary. From code, the same summary is at GET https://iplogs.com/v1/summary/8.8.8.8; add ?pretty for indented JSON.

3. Full check from code: POST /v1/check

curl https://iplogs.com/v1/check \
  -H 'content-type: application/json' \
  -d '{"ip":"185.220.101.34"}'

GET https://iplogs.com/v1/check/185.220.101.34 returns the same result without a body. Add "mode":"fast" (or ?mode=fast) to answer from in-memory lists in microseconds, with no live probes. Use it when you have a hard time budget, such as a login form.

4. Many addresses: POST /v1/bulk-check

Up to 100 addresses per call. Each row is compact and no live probes run.

curl https://iplogs.com/v1/bulk-check \
  -H 'content-type: application/json' \
  -d '{"ips":["185.220.101.34","8.8.8.8","10.0.0.1"]}'

A private address (for example 10.0.0.1) comes back as a row with an error field, and the rest of the batch still runs.

Prefer a browser? Paste a list into the bulk checker.

Node.js

const res = await fetch("https://iplogs.com/v1/check", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({ ip: "185.220.101.34" }),
});
const { verdict, score, is_vpn, is_proxy } = await res.json();

Python

import requests

r = requests.post("https://iplogs.com/v1/check", json={"ip": "185.220.101.34"}, timeout=30)
r.raise_for_status()
data = r.json()
print(data["verdict"], data["score"], data["is_vpn"])

More languages (PHP, Go, Java) are on the docs page.

Example response

Abridged: a Tor exit checked with POST /v1/check.

{
  "score": 1,
  "verdict": "vpn_detected",
  "is_vpn": true,
  "is_proxy": true,
  "is_tor": true,
  "reputation": "greylist",
  "signals": [
    { "type": "tor_exit", "weight": 0.95, "matched": true, "detail": "…" },
    { "type": "vpn_aggregator_cidr", "weight": 0.65, "matched": true, "detail": "…" }
  ],
  "ip_info": {
    "ip": "185.220.101.34",
    "asn": "AS60729",
    "org": "Stiftung Erneuerbare Freiheit",
    "country": "Germany",
    "country_code": "DE",
    "vpn_provider": "Tor"
  },
  "request_id": "req_0c51bd51-f66"
}

Verdict bands, from the score:

Score verdict
below 0.30 clean
0.30 to 0.59 suspicious
0.60 to 0.84 vpn_likely
0.85 and above vpn_detected

The score is evidence strength, not a probability. The website shows the same score on a 0 to 100 scale. Responses also carry is_tor, is_relay, is_hosting and is_crawler flags, so you can, for example, let iCloud Private Relay users through while blocking VPNs. Full field list: docs.

iplogs.com result for 8.8.8.8: Google public DNS, clean, 0/100

Limits

Free, no key
Rate 60 requests a minute, bursts of up to 30
Full checks (live probes included) 2,000 a day
After the daily quota Still answered, from the fast path ("mode":"fast")
Bulk 100 addresses a call; three calls at once, then one every 5 seconds
Timeout Full checks stop at 30 seconds (HTTP 504); send "mode":"fast" for a hard budget
Caching Full results are cached per address for 30 minutes

Limits count per calling address (IPv6 per /64), not per address you look up. Over the limit returns 429 with a Retry-After header. Private, loopback and link-local addresses return 400.

Need more? There are pay-as-you-go and Business plans: see pricing.

Use cases

  • Sign-up and login risk: flag VPN, proxy and Tor traffic before it creates accounts, in fast mode if you have a latency budget.
  • Fraud and abuse review: score a batch of addresses from checkout or API logs with /v1/bulk-check.
  • Log triage: paste an access log's addresses into the bulk checker and see which come from hosting, VPN or Tor networks.
  • Geo and licence enforcement: compare the address's network and country with what the user claims.
  • Self-checks: open iplogs.com in a browser to test your own connection, including a WebRTC leak test, or use the DNS leak test.

Things to know before you ship

  • Privacy relays are not VPN users. Check is_relay before acting on the verdict.
  • Search-engine and AI crawlers run in datacenters. Check is_crawler before blocking.
  • A missing vpn_provider is not a clean result. Decide on verdict or is_vpn.
  • Bulk rows skip live probes, so a borderline address can score lower than a single full check.

Privacy

Access logs are deleted after 30 days. Details: privacy policy.

Datasets

The aggregated VPN-provider dataset is published at /data/vpn-providers.json, and the other datasets are listed on /tools.

  • Datasets are licensed under Creative Commons Attribution 4.0 (CC BY 4.0). You may copy, redistribute and build on them, including commercially, if you give credit.
  • Suggested credit: Data: iplogs.com (CC BY 4.0), https://iplogs.com/tools
  • The CC BY 4.0 licence covers the published datasets only. It does not cover the API service or its live responses; use of those is governed by the terms.

Links

Website and live checker https://iplogs.com
API docs https://iplogs.com/docs
OpenAPI 3.1 spec https://iplogs.com/openapi.json
Accuracy and method https://iplogs.com/accuracy
Bulk checker https://iplogs.com/bulk
Pricing https://iplogs.com/pricing
SDKs and code samples https://iplogs.com/sdks
Changelog https://iplogs.com/changelog
Status https://status.iplogs.com
Terms, privacy https://iplogs.com/terms, https://iplogs.com/privacy
LLM-readable summary https://iplogs.com/llms.txt

Feedback and issues

Found a wrong verdict? Open an issue here with the address, what you expected and the request_id from the response. Please don't post anything private.