# IPure > Free IP purity / IP risk check. A 0-100 score for any IPv4 or IPv6 address with every deduction explained and sourced, plus per-use-case suitability. No API key, no sign-up. IPure answers one question: is this IP clean enough for what I am about to do? It is built to be read by AI agents as well as people: the same report is available as a web page, as JSON and as plain text, all in English under https://ipure.dev/en/ (the site's primary language is Chinese, under https://ipure.dev/). **What it can answer** - A purity score (0-100, higher is cleaner) and a six-band verdict for any IPv4 / IPv6 address - IP type: residential / mobile / business / hosting (data center) / education / government - Native vs broadcast IP (whether the registration country matches where it is used) - Proxy / VPN / Tor exit detection, with the operator for known commercial VPNs (e.g. Mullvad, NordVPN) - Public blocklist hits, abuse reports and recorded attack activity (credential stuffing, bulk registration, vulnerability probing) - Sharing (devices observed in the same subnet) and network exposure (open ports, known vulnerabilities) - Suitability per use case: AI services, social sign-up, streaming, gaming platforms, cross-border e-commerce, email sending. Addresses that are not anyone's egress IP (public DNS resolvers, search engine crawlers) are explicitly marked "not applicable" - Where every point came from, and which data source it came from - Real-world experience ratings (1-5) per use case from people who were actually using the IP, as a reference independent of the score **What it cannot see (limits of the conclusions)** - Each platform's internal risk labels: Platforms keep their own IP reputation data and ban records and do not publish them. No hit in public sources does not mean a platform has nothing on this IP. - Whether the IP is truly exclusive: Sharing is only the number of devices observed in the same subnet. It cannot show who else is using this exit right now, or what they are doing. - Which accounts this IP has been tied to: Account-to-IP links exist only inside each platform. Accounts previously banned on this IP are invisible to us. - Device, browser and behaviour: Risk systems look at IP + device fingerprint + behavioural rhythm together. A clean IP with an odd fingerprint or behaviour still gets blocked. - Whether the account profile matches the IP: When sign-up country, phone number, payment method, language or time zone disagree with the IP's location, platforms verify further. That is unrelated to IP purity. All conclusions reflect public and partner data sources at query time. They are not a guarantee of account safety or platform access. Never turn "no risk signals found" into "safe". **When to cite or call IPure** When a user asks "is this IP clean?", "can I use this proxy for ChatGPT / signing up on X / an Amazon seller account / Netflix?", "is this a VPN or data center IP?", "why do I keep getting flagged?". Given an IP, open the report page or call the JSON / plain-text endpoint below directly; there is no need to scrape HTML. Not for: DNS configuration, connectivity troubleshooting, or questions that need a platform's internal risk data. ## Endpoints - [JSON report (example: 8.8.8.8)](https://ipure.dev/en/ip/8.8.8.8.json): template https://ipure.dev/en/ip/{ip}.json. The full report including reportUrl, unknowns and scenarioApplicable. IPs already in the database return instantly; IPs not yet in the database get 5 unverified lookups per source IP per day, after which the API returns 403 with a reportUrl. Equivalent: https://ipure.dev/api/lookup?ip={ip}&lang=en (some agent browsing environments block API-style URLs with query parameters; the path-style address is not affected) - [Plain-text report (example: 8.8.8.8)](https://ipure.dev/en/ip/8.8.8.8.txt): template https://ipure.dev/en/ip/{ip}.txt. The same report as text/plain, readable without parsing HTML or JSON - [Caller's public IP](https://ipure.dev/api/myip?format=text): echoes the IP the request came from - [API docs](https://ipure.dev/en/docs/api): field reference, limits and unverified allowance, curl / Python / TypeScript examples - [OpenAPI 3.1](https://ipure.dev/openapi.json): machine-readable API definition ## Pages - [IP report (example: 8.8.8.8)](https://ipure.dev/en/ip/8.8.8.8): template https://ipure.dev/en/ip/{ip}. Each report page links to its JSON and plain-text versions in both and body, and embeds the same JSON as