IP Purity Check

Your address is checked automatically. Enter any public IP to see its score, what shaped it, and which sources could not answer.

IP purity is a shorthand for how an IP address looks to the lists and databases that decide whether its traffic is welcome: DNS blacklists, the Tor exit list, and network-type databases. This tool scores any public IPv4 or IPv6 address from those signals and shows every factor behind the score — including the ones that could not be checked. A flag here is a hint from a database, never a verdict: even 8.8.8.8, Google Public DNS, trips the proxy and hosting flags. The companion article why your IP address gets flagged explains why ordinary addresses end up on lists, and what you can and cannot do about it. For a deeper blacklist view, use the DNS Blacklist Checker; to see what websites learn from your browser as well as your address, try the Browser Fingerprint Test.

Last updated:

🔒 The checked IP goes to our checker and, server-side, to ip-api.com for location and type flags. Results are cached for one hour. Nothing else is stored, and no account is needed.

What happens to the address you check

The address you enter is sent to our checker, which asks DNS blacklists, the Tor exit list and — server-side only — ip-api.com for location and type flags. Results are cached for one hour, on the checker and at the edge, so a repeat check of the same address reuses the cached report. Nothing else about you is stored: no account, no history, no identifier beyond the rate limit. Your own address is learned only when you load this page or press “Check my IP”, via the same whoami endpoint the Browser Fingerprint Test uses.

What this score does NOT prove

A low score is not proof of abuse. Addresses are shared: CGNAT pools, VPN exits, cloud ranges and recycled datacenter blocks all put strangers behind one address, and a listing may describe a previous tenant, not the current one. The score describes the address, never the person using it.

A high score is not proof of cleanliness. It means none of the signals this tool checks flagged the address, at this moment, from the sources that answered. Other lists exist, lists change constantly, and a source that did not answer deducts nothing — the degraded banner says so plainly when that happens.

No single signal is proof of anything on its own. A proxy or hosting flag is one database’s classification, a blacklist listing is one operator’s decision, and a missing PTR record is common on ordinary addresses. Read the factor table, not just the number.

How the score is built

Every check starts at 100 and loses points only for signals that actually fired: a DNS blacklist listing costs 20 for the first list and 10 for each additional one (capped at 40), a Tor exit listing costs 30, a proxy flag 20, a hosting flag 15, a mobile flag 5, and a missing PTR record 5. Signals that could not be checked — a source that timed out, or a check that does not apply to IPv6 — cost nothing and are labelled unknown, so a partial check never looks cleaner or dirtier than the evidence supports.

The four bands are deliberately coarse: 80–100 is high, 60–79 moderate, 40–59 low, and 0–39 poor. A finer scale would pretend to a precision these databases do not have. If you run a service and an address scores low, the useful next step is the factor table: a blacklist listing has a removal process with the list operator, while a hosting flag usually just means the traffic comes from a datacenter — the article why your IP address gets flagged walks through each case.

Frequently asked questions

Why does 8.8.8.8 score less than 100?

Because the network database flags Google Public DNS as both a proxy and hosting — it is an anycast service, and those flags describe the kind of infrastructure behind the address, not wrongdoing. That is exactly why this page calls flags hints: a well-known, legitimate address trips two of them. The factor table shows which flags fired and what each one cost.

My own IP scored low. What should I do?

First read the factor table. If a DNS blacklist lists your address, the listing usually belongs to the address range or a previous user of it — the list operator’s removal page is the route, and a new address from your ISP, for example by reconnecting, often resolves it. If only proxy or hosting flags fired, there is usually nothing to fix: those describe the network, and most services accept them. The article why your IP address gets flagged covers each case in detail.

Why can I not check a private address like 192.168.1.1?

Private, loopback and other reserved addresses are not reachable on the public internet, so no public list or database has anything to say about them — a score would be invented. The checker refuses them before any lookup, and this page refuses them before any request. Only public, globally routable IPv4 and IPv6 addresses can be checked.