IPASK Checker Methodology Status Compare

IPASK in numbers

Counters from our own logs. They are not audited by a third party — we publish them because the alternative is telling you nothing.

Usage

55
checks served (60d)
9,483
page views (60d)
55
checks, last 7 days
1
paid orders

Checks = requests to /api/v1/lookup and /api/v1/verify, from server access logs. Batch rows are counted per request.

Networks checked most (30 days)

ASNNetworkChecksFlagged
AS13335Cloudflare440
AS20473Vultr2121
AS7922Comcast200
AS15169Google Cloud1111
AS60729Zwiebelfreunde33
AS8068Microsoft Azure11
AS16509AWS11
AS45102Alibaba Cloud11

“Flagged” means the check produced a caution or avoid verdict (hosting, CDN, VPN, Tor).

Most visited pages (7 days)

PathViews
/812
/ip/<ip>/706
/sitemap.xml142
/zh/119
/de/110
/ja/109
/pricing/87
/ru/77

Accuracy audit

Average match against reference sets: 100% (5 checks, last run 2026-11-01).

These are consistency checks against public reference data, not marketplace outcomes. Methodology.

Outcome signals (90 days)

1 reports · 1 worked · 0 rejected.

PlatformWorkedRejectedRate
amazon10100%

Self-reported and self-selected: people who answer are not a random sample. Treat it as a signal, not a measurement.

Corrections

0 verdict disputes received. We re-check each one by hand; corrections are recorded in the changelog.

If a verdict looks wrong, report it — no account needed.