Migrate from IPHub
Move from IPHub to VPNDetection: change the request, map each IPHub field to its VPNDetection field, and compare the answers before you switch.
This guide moves an integration from IPHub to VPNDetection. It shows how the request changes, which VPNDetection field answers each of IPHub's, how rules that read them change, and how to compare the two services on your own traffic before you switch.
Before you begin
- A VPNDetection API key, if you need more than the free plan's fields. Without a key, a lookup answers the free plan's fields:
is_vpn,is_tor,is_relay, and the address's country and network. See Plans and fields. - A sample of a few hundred addresses from your own traffic, one per line in
sample.txt, for the comparison in step 4.
1. Change the request
IPHub takes your key in the X-Key header, and returns proxyType only when you send Accept-Version: 2.2:
curl -H "X-Key: $IPHUB_KEY" -H "Accept-Version: 2.2" https://v2.api.iphub.info/ip/8.8.8.8VPNDetection takes the address as the path and your key in the Authorization header:
curl -H "Authorization: Bearer $VPNDETECTION_API_KEY" https://api.vpndetection.io/8.8.8.8If your code can't set a header, send the key in the apikey query parameter instead; see Authentication. To make the request from your code with an official library, see Use an SDK.
2. Map the fields
IPHub answers a block code and, in version 2.2, the proxyType object. VPNDetection answers one top-level flag for each kind of address, with a detail object beside it. Fields after Paid plan: come with a paid plan; the rest come with every plan, the free plan included.
| IPHub | VPNDetection | Notes |
|---|---|---|
block | is_vpn; Paid plan: is_hosting, is_resproxy, is_dcproxy | Read the classifications your rule acts on, instead of one code. |
proxyType.residentialProxy | Paid plan: is_resproxy, resproxy.last_seen | resproxy.last_seen says when the address was last seen in a pool. |
proxyType.proxy | Paid plan: is_dcproxy, is_mobproxy, is_pubproxy | One flag for each kind. |
proxyType.tor | is_tor | |
proxyType.hosting | Paid plan: is_hosting, hosting.provider | hosting.provider names the hosting company. |
proxyType.relay | is_relay, relay.provider | relay.provider names the relay operator. |
asn, isp | asn.asn, asn.name | asn.asn is a number, as IPHub's is. |
countryCode, countryName | location.country, location.country_name | |
hostname | hostname | |
proxyType.cloudGaming | No counterpart |
The IP lookup reference documents every VPNDetection field.
3. Update your rules
The main change is from a code to classifications:
- IPHub's
blockis 1 for a non-residential address and for a recently seen residential proxy. The equivalent rule on the free plan isr.isVpn || r.isTor || r.asn?.type === 'hosting', and a paid plan addsis_hostingand the proxy flags. - VPNDetection answers every field in every answer, so no version header is needed.
- A field your plan doesn't include is absent rather than
false, so a rule checks that a paid field is present before it acts on the value. See Plans and fields.
4. Compare the answers
Before you switch, run both services on your sample and review the addresses where they disagree. This script prints each address where IPHub's block decision and VPNDetection's differ. Save it as compare.mjs beside sample.txt, install the library with npm install vpndetection, and run node compare.mjs:
import { readFileSync } from 'node:fs';
import { VPNDetection } from 'vpndetection';
const client = new VPNDetection({ apiKey: process.env.VPNDETECTION_API_KEY });
const ips = readFileSync('sample.txt', 'utf8').split('\n').filter(Boolean);
for (const ip of ips) {
const res = await fetch(`https://v2.api.iphub.info/ip/${ip}`, {
headers: { 'X-Key': process.env.IPHUB_KEY, 'Accept-Version': '2.2' },
});
const theirs = await res.json();
const ours = await client.lookup(ip);
const theirFlag = theirs.block === 1;
const ourFlag = ours.isVpn || ours.isTor || ours.asn?.type === 'hosting';
if (theirFlag !== ourFlag) {
console.log(ip, 'IPHub:', theirFlag, 'VPNDetection:', ourFlag);
}
}Every provider builds its own data, so some disagreement is expected. Look up a few of the addresses on both sides. If you believe VPNDetection's answer is wrong, send us the address.
5. Switch over
Once the comparison looks right, switch in stages, so you can stop at any point without affecting your users:
- Run both side by side. Keep deciding with IPHub, and log VPNDetection's answer beside it for a few days of real traffic.
- Switch the decisions. Decide with VPNDetection, and keep logging IPHub's answer while you watch for surprises.
- Remove IPHub. Once your logs are clean, delete the old client from your code and revoke its key.
Next steps
When the answers suit your rules, switch your code to VPNDetection. Protect a web app applies rules in middleware, and the guides cover sign-ups, logins, payments and country rules. Before you launch, review the go-live checklist.