Who runs an IP or ASN, is a route valid, abuse contacts, routing visibility, CIDR math.
payments ON MAINNET (real money) · 9 live endpoints
| Endpoint | Price | What it answers |
|---|---|---|
GET /abuse-contact | $0.02 | Abuse contact email(s) and the responsible regional registry for an IP address, prefix or AS number. |
GET /asn-profile | $0.03 | Profile of an AS number: holder, registry block, announced IPv4 and IPv6 prefix counts and abuse contact. |
GET /cidr-calc | $0.02 | IPv4 CIDR math: network, broadcast, netmask, usable hosts and range; optionally test if an IP is inside the block. |
GET /ip-geo | $0.02 | Approximate country, city and coordinates of a public IP, with how much of its prefix that location covers. |
GET /ip-parse | $0.02 | Classify an IPv4 or IPv6 address: version, public or private, special range, canonical form and reverse-DNS name. |
GET /ip-profile | $0.03 | Profile of a public IP: announcing AS and holder, enclosing prefix, whether it is routed, abuse contact and country. |
GET /prefix-routing | $0.02 | Routing visibility of a prefix: origin ASes, share of RIS peers that see it, first and last seen, covering routes. |
GET /route-origin-check | $0.05 | Check an IP is originated by the AS you expect, with its RPKI status: MATCH, MISMATCH or MULTI_ORIGIN, a hijack screen. |
GET /rpki-check | $0.02 | RPKI route-origin validation: is this AS authorized by a ROA to announce this prefix? valid, invalid or unknown. |
GET /catalog returns this list as JSON. Activity hub · uptime.
Network facts come from RIPEstat (RIPE NCC) public routing and registry data and local computation, provided as is. Registry data can be stale or wrong, geolocation is approximate, and RPKI status describes route-origin validation only. This is not a threat verdict about an address. Every paid response carries a disclaimer field.