I5P.COM

Free IP Lookup API

Free to use, no registration required (anonymous calls are rate limited); an API key raises your quota. Returns JSON, CORS enabled.

1. Look up your own IP

GET /api/myip

Returns the caller's public IP and its geolocation.

2. Look up a specific IP

GET /api/ip?ip=8.8.8.8

Optional &key=YOUR_API_KEY raises the rate limit.

3. Look up a domain (resolve, then locate each IP)

GET /api/ip?domain=baidu.com

Returns every IP the domain resolves to, each with its geolocation.

4. Plain-text lookup for the command line

GET /ip

Built for curl and shell scripts — returns a single line of plain text instead of JSON.

$ curl https://www.i5p.com/ip
103.118.252.70 | Hong Kong Island, Hong Kong, China | Alibaba Cloud
$ curl "https://www.i5p.com/ip?ip=8.8.8.8"
8.8.8.8 | Mountain View, California, United States | Google Cloud/DNS/DoH/DoT

No parameter looks up your own address; ?ip= looks up a specific one; ?lang=en or ja switches language.

# Through a proxy — returns the proxy exit IP (no auth)
curl -x http://127.0.0.1:8080 https://www.i5p.com/ip

# When the proxy needs credentials
curl -x http://user:password@127.0.0.1:8080 https://www.i5p.com/ip

For a SOCKS5 proxy just use socks5:// instead of http://. This is the quickest way to confirm a proxy is working and where it exits.

Example response

{
  "code": 0,
  "msg": "ok",
  "data": {
    "ip": "8.8.8.8",
    "country": "United States",
    "province": "California",
    "city": "Mountain View",
    "zip": "",
    "isp": "Google Cloud/DNS/DoH/DoT"
  }
}

5. QR code generation

GET /qr/?data=TEXT&size=300&p=82

A GET request returns an image/png directly, ready to drop into an <img> tag.

data QR content (required, URL-encoded); size 80–1200, default 320; p style ID 1–120, or your own ID created while signed in; format=base64 returns a JSON data URI.

<img src="https://www.i5p.com/qr/?data=https%3A%2F%2Fwww.i5p.com&size=300&p=82">

QR

Full parameters and a live playground: QR Code

6. Barcode generation

GET /bar/?data=TEXT&type=ean13

A GET request returns an image/png directly. Seven 1D symbologies supported.

data barcode content (required); type one of code128 / ean13 / ean8 / upca / code39 / itf / codabar, default code128; w module width 1–8; h height 20–400; fg/bg colors; text=0 hides the caption.

<img src="https://www.i5p.com/bar/?data=6901234567892&type=ean13&w=3&h=140">

Barcode

Full parameters and a live playground: Barcode

Request signing

Requests carrying a key must be signed. Your api_secret never appears in the URL, so a leaked link (logs, browser history) cannot be used to forge further requests.

key your API key; ts Unix timestamp in seconds (300s tolerance); nonce random string of 6–64 chars (single use within 300s); sign the signature. All four may instead be sent as X-Api-Key / X-Api-Ts / X-Api-Nonce / X-Api-Sign headers.

Algorithm: take every parameter except sign and callback, sort by parameter name ascending, join as k1=v1&k2=v2 (raw values, no URL encoding), then HMAC-SHA256 with your api_secret, lowercase hex.

// PHP
$key    = 'a1b2c3d4e5';
$secret = '你的secret';
$p = ['ip' => '8.8.8.8', 'key' => $key, 'ts' => time(), 'nonce' => bin2hex(random_bytes(6))];
ksort($p);
$base = [];
foreach ($p as $k => $v) { $base[] = "$k=$v"; }
$p['sign'] = hash_hmac('sha256', implode('&', $base), $secret);
echo file_get_contents('https://www.i5p.com/api/ip?' . http_build_query($p));
// Node.js
const crypto = require('crypto');
const key = 'a1b2c3d4e5', secret = '你的secret';
const p = { ip: '8.8.8.8', key, ts: Math.floor(Date.now() / 1000),
            nonce: crypto.randomBytes(6).toString('hex') };
const base = Object.keys(p).sort().map(k => `${k}=${p[k]}`).join('&');
p.sign = crypto.createHmac('sha256', secret).update(base).digest('hex');
const url = 'https://www.i5p.com/api/ip?' + new URLSearchParams(p);
fetch(url).then(r => r.json()).then(console.log);
#!/bin/bash
KEY="a1b2c3d4e5"; SECRET="你的api_secret"
IP="8.8.8.8"; TS=$(date +%s); NONCE=$(head -c6 /dev/urandom | xxd -p)
BASE="ip=$IP&key=$KEY&nonce=$NONCE&ts=$TS"   # already in ascending key order
SIGN=$(printf '%s' "$BASE" | openssl dgst -sha256 -hmac "$SECRET" -r | cut -d' ' -f1)
curl "https://www.i5p.com/api/ip?$BASE&sign=$SIGN"

Create keys in your dashboard. If the admin disables “require signing”, sending only key also works (not recommended).

CORS & JSONP

Every JSON endpoint sends Access-Control-Allow-Origin: *, so fetch/XHR works cross-origin. Add ?callback=fnName (or jsonp=) to get JSONP for direct <script> use.

<script src="https://www.i5p.com/api/myip?callback=showIp"></script>
<script>function showIp(r) { console.log(r.data.ip); }</script>

Notes