what detects you on ipinfo.io

NOT SCORED, the verdict rule carries no information (KAN-432 / PA-SCORE-16). VERIFIED LIVE 2026-07-29: the untokened `https://ipinfo.io/json` body is `{ip, city, region, country, loc, org, postal, timezone, readme}`, no `hosting` key, no privacy block, on any response. So `notContains "\"hosting\""` is unconditionally TRUE and every tool passes for reasons unrelated to its egress IP: the ledger reads 525/540 (97.2 %), 16 of 17 tools at 100 %, the lone exception being `curl-impersonate`, which fails by not fetching rather than by being flagged. A column everything passes carries no information, and this one was HALF the proxy grid, so `scored` is removed until a token is wired. The rule is kept rather than deleted so the target still yields its SIGNALS, which are real proxy-axis data. REPLACE the verdict when a token exists: human = privacy.proxy==false && privacy.hosting==false. SIGNALS (WP3.10, verified live through the fleet proxy 2026-07-24): the untokened response still carries ip/org/hostname/country/timezone, which is real proxy-axis data. Caveat (2026-07-29): that direct fetch returned NO `hostname`, so `rdnsHostname` may be a standing absence on egresses without reverse-DNS rather than a measurement. `rdnsHostname` is the strongest residential tell available without a token. A consumer ISP returns reverse-DNS like `fl-67-235-197-72.dhcp.embarqhsd.net`, which a datacenter range does not. `timezone` is classed `coherence`, not `network`: its value is whether the egress timezone AGREES with the browser locale/tz the fingerprint presents, which is the server-coherence layer's whole question.