iplover API
Free JSON and plain-text endpoints: your own address, who is behind any address, its network type, and whether a crawler is real. No key, no sign-up, and CORS is open, so you can call it from a browser.
Quick start
From a terminal, no setup needed:
curl iplover.com
curl https://iplover.com/json
curl https://iplover.com/api/check/8.8.8.8.txt
curl "https://iplover.com/api/verify-bot.txt?ip=66.249.66.1&ua=Googlebot"
Endpoints
| Endpoint | What it returns | Limit |
|---|---|---|
GET /ip | Your public address as plain text. | None |
GET /json | Your address, approximate location and network. | None |
GET /json/{ip} | The registry record and reverse DNS of any public address. | 30 a minute plus the shared budget of 60 a minute |
GET /api/check/{ip} | Who is behind an address: category, network type and owner, with the evidence. | 30 a minute plus the shared budget of 60 a minute |
GET /api/verify-bot | Whether a crawler is who its user agent says it is. | 30 a minute plus the shared budget of 60 a minute |
POST /api/classify | Network types of up to 100 addresses in one request. | 30 a minute |
GET /api/asn/index | An address → network table, in small pieces, for lookups in the browser. | 30 a minute only requests our cache can't answer count |
GET /ip
Your public address as plain text.
Format: text
Limit: None
curl iplover.com gives the same answer: command-line clients (curl, Wget, HTTPie, xh, PowerShell) get the bare address on the homepage. Both also work over plain HTTP, for scripts that don't follow redirects.
Example
curl iplover.com
curl https://iplover.com/ip
Example response
203.0.113.7
GET /json
Your address, approximate location and network.
Format: JSON
Limit: None
The location is Cloudflare's estimate for your connection: usually the city of your provider's gateway, not your home. A VPN or a mobile network moves it.
Example
curl https://iplover.com/json
Example response
{
"ip": "203.0.113.7",
"ip_version": 4,
"country": "Italy",
"country_code": "IT",
"region": "Lombardy",
"city": "Milan",
"postal_code": "20121",
"latitude": 45.4642,
"longitude": 9.19,
"timezone": "Europe/Rome",
"asn": 64500,
"as_organization": "Example Telecom",
"user_agent": "curl/8.5.0"
}
GET /json/{ip}
The registry record and reverse DNS of any public address.
Format: JSON
Limit: 30 a minute (plus the shared budget of 60 a minute)
We ask the regional registry (RDAP) and a public DNS resolver. If a part fails, it is empty and status and errors say why. Complete answers are cached for an hour. Private and reserved addresses get a 422 with their kind.
Parameters
{ip}(in the path)- An IPv4 or IPv6 address.
Example
curl https://iplover.com/json/8.8.8.8
Example response
{
"ip": "8.8.8.8",
"ip_version": 4,
"summary": "This address belongs to Google LLC (a cloud/hosting network) in the United States. Its reverse DNS name is dns.google.",
"network": { "name": "GOGL", "handle": "NET-8-8-8-0-2", "range": "8.8.8.0 - 8.8.8.255", "cidr": ["8.8.8.0/24"], "country": "United States", "country_code": "US", "country_source": "address" },
"owner": { "organization": "Google LLC", "abuse_email": "network-abuse@google.com" },
"registration": { "registered": "2023-12-28", "last_changed": "2023-12-28", "registry": "ARIN" },
"hosting_network": true,
"reverse_dns": ["dns.google"],
"status": { "rdap": "ok", "reverse_dns": "ok", "rdap_via": "rdap.org" },
"errors": { "rdap": null, "reverse_dns": null },
"sources": { "rdap": "https://rdap.arin.net/registry/ip/8.8.8.8", "reverse_dns": "https://cloudflare-dns.com/dns-query" },
"fetched_at": "2026-11-16T19:20:48.593Z",
"cached": false
}
Errors: invalid_ip, not_public, rate_limited
GET /api/check/{ip}
Who is behind an address: category, network type and owner, with the evidence.
Format: JSON · text
Limit: 30 a minute (plus the shared budget of 60 a minute)
Checks the published lists described on Sources (clouds, large companies, crawlers, scanners, Tor, VPNs, blocklists), plus the registry and forward-confirmed reverse DNS. Add .txt for plain text and ?lang= for the language of the readable text. Private and reserved addresses get a 200 with the category reserved.
Parameters
{ip}(in the path)- An IPv4 or IPv6 address.
lang(query)- Language of the readable text: en, it, de, es, fr, pt. Field names and codes are always English.
format(query)textfor plain text (same as adding.txt).
Example
curl https://iplover.com/api/check/8.8.8.8
curl https://iplover.com/api/check/8.8.8.8.txt
Main fields
category- The strongest match, one of the categories below.
ispmeans no list matched: an ordinary network. level- How much attention it deserves:
bad,warn,info,goodorneutral. verdict,explanation,action- Three sentences in the requested language: what it is, why, and what to do.
matched- The sources that matched, with the evidence: a list, reverse DNS or the network number.
sources- Every source and its result:
matched,not_matchedornot_checked. A source we couldn't check is never counted as a clean result. owner- The registry record: organization, range, abuse contact and dates.
asn- The network number announcing the address, and its name.
reverse_dns- The PTR name, and whether it resolves back to the address (
forward_confirmed). country- Where the range is registered, not where the device is.
network- Network type (residential, mobile, hosting, VPN, Tor…).
identifiedwhen a published list says so,estimatedwhen we infer it, and labelled as an estimate. lists- How many sources were checked, and how recent our copies are.
Categories
category | Label | level |
|---|---|---|
attacker | Seen attacking our sensors | bad |
blocklisted | On a blocklist | bad |
tor | Tor exit node | warn |
relay | Privacy relay | info |
scanner | Known internet scanner | info |
bot | Verified crawler | good |
cloud | Cloud or hosting provider | info |
service | Large company's own network | info |
isp | Internet provider or business network | neutral |
reserved | Private or reserved address | info |
unknown | Not enough data | info |
The labels follow ?lang=. A network type such as VPN, Tor or hosting is not a sign of abuse; only attacker and blocklisted are about behaviour.
Example response
{
"ip": "8.8.8.8",
"ip_version": 4,
"category": "service",
"category_label": "Large company's own network",
"level": "info",
"verdict": "This address is part of Google's own network.",
"explanation": "It is in the IP ranges Google publishes for its own services (such as search, email or public DNS), not in the ranges it rents to cloud customers. …",
"action": "No action is needed based on these sources. If traffic from it misbehaves, report it to the abuse contact of Google.",
"matched": [{ "source": "google", "name": "Google IP ranges (goog.json)", "kind": "service", "evidence": "list", "detail": null }],
"sources": [{ "source": "aws", "name": "AWS IP address ranges", "kind": "cloud", "status": "not_matched", "updated_at": "2026-11-16T05:37:05Z" }, …],
"owner": { "organization": "Google LLC", "network": "GOGL", "cidr": ["8.8.8.0/24"], "range": "8.8.8.0 - 8.8.8.255", "abuse_email": "network-abuse@google.com", "registry": "ARIN", … },
"owner_status": "ok",
"asn": { "number": 15169, "name": "Google LLC" },
"reverse_dns": { "name": "dns.google", "forward_confirmed": true, "forward_addresses": [], "forward_error": false, "resolver": "cloudflare" },
"country": { "code": "US", "name": "United States", "source": "address" },
"network": {
"primary": "service",
"status": "identified",
"label": "Company's own network",
"explanation": "This address is in the IP ranges Google publishes for its own services, …",
"types": [{ "type": "service", "basis": "list", "source": "google", "provider": "Google", "label": "Company's own network", "attribution": null, … }],
"attribution": null,
"crawler": null,
"note": "The network type describes the network, not the person. …"
},
"providers": [{ "id": "ip2proxy", "name": "IP2Proxy", "status": "not_configured" }, …],
"lists": { "version": "89d308802d8e", "built_at": "2026-11-16T19:17:44.219Z", "newest_update": "2026-11-16T19:17:44.219Z", "checked": 36, "not_checked": 1, … },
"checked_at": "2026-11-16T19:31:38.854Z",
"language": "en",
"note": "No source is complete. …"
}
Errors: invalid_ip, rate_limited
GET /api/verify-bot
Whether a crawler is who its user agent says it is.
Format: JSON · text
Limit: 30 a minute (plus the shared budget of 60 a minute)
Give ip, ua or both. With an address, we check it against the bot's published ranges and forward-confirmed reverse DNS. Without one, we only tell you which bot the user agent claims to be. /api/verify-bot.txt returns plain text. Requests without an address don't count toward the limit.
Parameters
ip(query)- The address that sent the request (optional).
ua(query)- The User-Agent it sent (optional), up to 1000 characters.
lang(query)- Language of the readable text: en, it, de, es, fr, pt. Field names and codes are always English.
Example
curl "https://iplover.com/api/verify-bot?ip=66.249.66.1&ua=Googlebot"
curl "https://iplover.com/api/verify-bot.txt?ip=66.249.66.1&ua=Googlebot"
Main fields
verdict- The answer: one of the values below.
claim,botclaimis the bot the user agent names;botis the bot the verdict is about.identified- Bots whose published ranges or reverse DNS match the address.
evidence- The reverse DNS check and the lists we consulted, with their dates.
network- The address's network type, as in
/api/check.
Verdicts
verified- The address is in the bot's published ranges, or its reverse DNS is forward-confirmed under the operator's domain.
spoofed- The user agent claims a bot that publishes how to verify it, and the address doesn't match: likely fake.
different- The address belongs to a different known bot than the one claimed.
unverified- The claimed bot publishes nothing to check against, or its list was unavailable: we can't say either way.
notbot- No bot claim, and the address is in no bot's ranges.
claim- Only a user agent was given: the bot it claims to be.
noclaim- Only a user agent was given, and it names no known bot.
Example response
{
"ip": "66.249.66.1",
"user_agent": "Googlebot",
"verdict": "verified",
"reason": null,
"claim": { "slug": "googlebot", "name": "Googlebot", "operator": "Google", "category": "search", "tokens": ["Googlebot"], "robots": "yes", "verify": "ip" },
"bot": { "slug": "googlebot", … },
"identified": [{ "slug": "googlebot", "name": "Googlebot", "source": "googlebot", "list": "Google common crawlers (Googlebot)", "evidence": "list", … }],
"evidence": {
"reverse_dns": { "name": "crawl-66-249-66-1.googlebot.com", "forward_confirmed": true, "operator_domain": true, … },
"lists": [{ "id": "googlebot", "name": "Google common crawlers (Googlebot)", "fetched_at": "2026-11-16T19:17:44.219Z", "source_time": "2026-11-16T15:45:57.000000", "count": 317, … }]
},
"network": { "primary": "service", "status": "identified", "label": "Company's own network", "crawler": { "name": "Googlebot", "source": "googlebot", "evidence": "list", … }, … },
"owner": "Google LLC",
"asn": { "number": 15169, "name": "Google LLC" },
"known_bots": 34,
"checked_at": "2026-11-16T19:32:09.527Z"
}
Errors: empty, invalid_ip, rate_limited
POST /api/classify
Network types of up to 100 addresses in one request.
Format: JSON
Limit: 30 a minute
Uses only our copies of the published lists: no registry, DNS server or other service is asked. That makes it fast, but there is no owner or reverse DNS. The body can be at most 16 KB. Duplicates are merged, and entries that are not addresses come back in invalid. Our log checker uses this endpoint.
Parameters
ips(JSON body)- A list of addresses:
{"ips": ["…"]}. lang(query)- Language of the readable text: en, it, de, es, fr, pt. Field names and codes are always English.
Example
curl -X POST https://iplover.com/api/classify \
-H "Content-Type: application/json" \
-d '{"ips": ["8.8.8.8", "185.220.101.1"]}'
Main fields
results- One entry per address:
category,level,verdict,matched(source ids) andnetwork. invalid- Entries that are not IP addresses.
Example response
{
"results": [
{ "ip": "8.8.8.8", "category": "service", "category_label": "Large company's own network", "level": "info", "verdict": "This address is part of Google's own network.", "matched": ["google"], "network": { "primary": "service", "status": "identified", "label": "Company's own network", … } },
{ "ip": "185.220.101.1", "category": "tor", "category_label": "Tor exit node", "level": "warn", "verdict": "This is a Tor exit node.", "matched": ["tor", "x4bnet-vpn"], "network": { "primary": "tor", "status": "identified", "label": "Tor exit node", "types": [{ "type": "tor", … }, { "type": "vpn", "label": "Known VPN range (community list)", "attribution": "Source: X4BNet lists_vpn (CC BY-SA 4.0)", … }], … } }
],
"invalid": [],
"checked_at": "2026-11-16T19:21:02.311Z",
"note": "Network types from published lists only. Nothing you send is stored. …"
}
Errors: invalid_json, no_ips, invalid_ip, method_not_allowed, too_large, too_many, no_public_ips, rate_limited, unavailable
GET /api/asn/index
- GET
/api/asn/{gen}/v{family}/{shard}/{hash} - GET
/api/asn/n/{shard}/{hash}
An address → network table, in small pieces, for lookups in the browser.
Format: JSON · binary · text
Limit: 30 a minute (only requests our cache can't answer count)
Our WebRTC test and log checker use it to find an address's network without sending the address anywhere: download the index, take the last shard that starts at or below the address, and search it. The binary format is in the OpenAPI file, and a reader is at /js/asnmap.js. Network names and countries are in 256 text shards: network n is in shard n % 256. Rebuilt daily from iptoasn.com (public domain). If you need the whole table, download it from iptoasn.com instead.
Example
curl https://iplover.com/api/asn/index
Example response
{
"gen": 1,
"fetched_at": "2026-11-16T09:37:04.503Z",
"source_date": "2026-11-01T09:38:43.000Z",
"source": "https://iptoasn.com/",
"license": "PDDL 1.0 (public domain)",
"rows": { "v4": 405962, "v6": 94218 },
"v4": [0, 93810688, 136380928, …],
"v6": ["0000000000000000", …],
"h4": ["9c1e04aa", …],
"h6": ["51f0c2d7", …],
"hn": ["0be2a1c4", …]
}
Errors: not_found, rate_limited, unavailable
Errors
Errors are JSON with a stable error code and a readable message. The message is in English and its wording can change, so match on the code. Plain-text endpoints return the message as text, with the same status code.
HTTP/1.1 429 Too Many Requests
Retry-After: 60
Content-Type: application/json; charset=utf-8
{
"error": "rate_limited",
"message": "Too many checks. Try again in a minute."
}
| Code | Status | Meaning |
|---|---|---|
invalid_ip | 400 | Not an IPv4 or IPv6 address. |
empty | 400 | Neither ip nor ua was given. |
invalid_json | 400 | The body is not valid JSON. |
no_ips | 400 | No ips list, or it is empty. |
method_not_allowed | 405 | Wrong method: use POST. |
not_found | 404 | No such shard, or the table isn't built yet. |
too_large | 413 | The body is over 16 KB. |
too_many | 413 | More than 100 addresses. |
not_public | 422 | A private, reserved or special-use address. kind says which. |
no_public_ips | 422 | Only private or reserved addresses. |
rate_limited | 429 | Too many requests: wait the number of seconds in Retry-After (60). |
unavailable | 503 | A temporary problem on our side: try again in a minute. |
Rate limits
- Limits apply per visitor: one IPv4 address, or one IPv6 /64 (a single connection usually controls a whole /64).
- Each endpoint allows 30 requests a minute. The endpoints that contact other servers (
/json/<ip>,/api/check, and/api/verify-botwith an address) also share one budget of 60 a minute, so using several at once doesn't multiply it. /ipand/jsonhave no limit. For the network table, only requests our cache can't answer count.- Over the limit, you get
429withRetry-After: 60. Wait, then continue: don't retry in a tight loop. - The counters are kept at each Cloudflare location and are approximate. If abuse makes it necessary, we will lower them and say so here.
Code examples
Each example checks an address and waits when it is rate limited.
curl
# -f makes curl fail on 4xx and 5xx; --retry waits and retries on 429
curl -sf https://iplover.com/api/check/8.8.8.8 || echo "failed: see the status code"
curl -s --retry 3 --retry-delay 60 https://iplover.com/json
Python
# pip install requests
import time
import requests
def check(ip, lang="en"):
while True:
r = requests.get(f"https://iplover.com/api/check/{ip}",
params={"lang": lang}, timeout=20,
headers={"User-Agent": "my-app/1.0 (+https://example.com)"})
if r.status_code == 429: # rate limited: wait, then retry
time.sleep(int(r.headers.get("Retry-After", "60")))
continue
r.raise_for_status()
return r.json()
result = check("8.8.8.8")
print(result["category"], "-", result["verdict"])
# Up to 100 addresses at once, from the lists only
r = requests.post("https://iplover.com/api/classify",
json={"ips": ["8.8.8.8", "185.220.101.1"]}, timeout=20)
for item in r.json()["results"]:
print(item["ip"], item["category"])
JavaScript
// Works in browsers (CORS is open), Node 18+, Deno and Workers.
async function check(ip, lang = "en") {
for (;;) {
const res = await fetch(`https://iplover.com/api/check/${encodeURIComponent(ip)}?lang=${lang}`);
if (res.status === 429) {
// Rate limited: wait Retry-After seconds, then retry.
const wait = Number(res.headers.get("Retry-After") || 60);
await new Promise((resolve) => setTimeout(resolve, wait * 1000));
continue;
}
const body = await res.json();
if (!res.ok) throw new Error(`${body.error}: ${body.message}`);
return body;
}
}
const result = await check("8.8.8.8");
console.log(result.category, result.verdict, result.network?.label);
Versioning and changes
- The current version is 1.3.0. There is no version in the URL.
- We may add new fields and new values at any time: ignore the ones you don't know.
- We won't remove or rename a documented field, or change what it means, without announcing it here at least 30 days ahead, unless we have to stop abuse or follow the law.
- Readable text (verdicts, labels, messages) can be reworded at any time. Don't parse it: use the codes.
Changes
- 1.3.0 ():
asngainscountryandregistry: the country and registry of the allocation the address belongs to (from Team Cymru), not a location. The owner's name now comes from RIPE role objects when the registrant is only a maintainer account, and a 404 from rdap.org now asks the registry too. - 1.2.0 (): The network type can now come from the address's reverse DNS name (for example
dynamic.pool-…ormob-…) and from internet-provider words in the network's names; a newevidencefield says which. - 1.1.0 (): The network type now looks at every name of the network (registry organization, network name, ASN name), uses a community data center list, says “Residential or business ISP (estimate)” instead of “Not identified” when the names match nothing, and gives a new
confidencefield. - 1.0.0 (): First documented version.
Free use and fair use
- Free for personal and commercial use, without a key. There is no warranty and no uptime guarantee: see the terms of use.
- Stay within the limits, cache what you can, and send a User-Agent that names your app and how to reach you.
- Don't use it to scan address ranges or to build or resell a copy of our data. Don't use it as the only reason to block people: a network type is not proof of abuse.
- Results include data from the sources listed on Sources, each under its own terms. Some ask for credit: keep the
attributiontext when you show those results. - We may block traffic that harms the service, without notice. Credit is welcome but not required.
What happens to what you send
We don't store or log the addresses or user agents you send, or your own address.
To answer, /json/<ip>, /api/check and /api/verify-bot send the address to rdap.org and the internet registries' RDAP services, and look it up through public DNS resolvers (Cloudflare, or Google as a fallback), which ask Team Cymru for its network number. /api/classify and the network table send nothing anywhere. Cloudflare, our host, processes every request: see the privacy policy.
Other URLs under /api/ (such as /api/email-domain, /api/health and /report.json) serve our own pages and monitoring. They are not part of this API and can change without notice.