IP purity report
2001:4860:7:f0e::6e
93/ 100
Clean
confidence: high
Good reputation; at the IP level it rarely draws extra verification.
Based on signals observed from public and partner data sources at 2026-09-28 01:34 UTC. This describes IP-level risk only; platforms' internal risk data is not visible to us.
Profile
What this IP is
- Country / region
- United States · District of Columbia · Washington
- IP type
- Hosting / data center
- Native / broadcast
- Native IP
- Network
- AS15169 Google Chrome Prefetch Proxy
- Reverse DNS
- none
- Devices seen in subnet
- no data
Suitability
What it is good for
Each use case weighs the evidence differently; these are not one overall score.
Per-use-case suitability does not apply
This is an official address of a well-known public service, not a network exit that users can browse from, so there is nothing to log in or sign up from. The purity score only describes its network reputation.
Evidence
Why it got this score
- −25
IP type: Hosting / data center
Hosting / data center IPs are the main source of automated traffic
- What it means
- This IP sits in a hosting / datacenter range. Platforms assume real people browse from home or a phone, and machines live in datacenters.
- Which uses care
- Cares most: AI services, Social sign-up, Gaming platforms, Cross-border e-commerce; Barely looks at it: Email sending
- Why it is weighted this way
- The most basic signal there is: scrapers, bulk sign-ups and fake traffic overwhelmingly come from datacenters, so risk systems discount the whole range. It says nothing about what you did, only that you share the range.
- Can it be fixed
- The range type cannot be changed. What helps is not stacking other issues on top: stay off blocklists, close unneeded ports, avoid crowded exits.
- −5
No rDNS record
No PTR record; IPs allocated by established carriers usually have one
- What it means
- This IP has no reverse hostname (PTR record). Addresses allocated by established carriers usually have one.
- Which uses care
- Cares most: Email sending
- Why it is weighted this way
- A few points only: a missing PTR is a weak "unknown origin" signal, not a stain. Email cares more, since receiving servers check it.
- Can it be fixed
- Most hosts let you set a PTR in the control panel; set it to a sensible hostname.
- +3
No open ports
Network scans have not observed any open service on this IP
- What it means
- Network scanners have not observed any open service on this IP.
- Which uses care
- Barely looks at it: AI services
- Why it is weighted this way
- A small bonus: a small attack surface means fewer chances of ending up in scanner and abuse databases. Not evidence of home broadband; a well-firewalled server looks the same.
- Can it be fixed
- An inherent attribute of the IP or its range; nothing a user can change short of a different IP.
- +5
Native IP
Registered and used in the same country, allocated directly by a local carrier
- What it means
- Registered and used in the same country, allocated directly by a local carrier: a "native IP".
- Which uses care
- Cares most: Streaming / short video, Gaming platforms; Barely looks at it: Email sending
- Why it is weighted this way
- A bonus: region-based checks will not trip.
- Can it be fixed
- An inherent attribute of the IP or its range; nothing a user can change short of a different IP.
- +15
Whitelisted IP
Listed as an official address of a well-known service or crawler
- What it means
- This address is listed as the official IP of a well-known service or search engine.
- Which uses care
- All six uses treat it about the same, at the same weight as the overall score.
- Why it is weighted this way
- A bonus, and it also means this is nobody's egress, so scenario assessment does not apply.
- Can it be fixed
- An inherent attribute of the IP or its range; nothing a user can change short of a different IP.
Reputation
Blocklists and abuse history
Not listed on any of the 3 blocklists checked (Spamhaus ZEN, blocklist.de, DroneBL).
- abuseipdb abuse confidence 0%
Limits
What an IP check cannot tell you
- 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.
Sources
Data sources and responses
- rdap95ms
- team-cymru105ms
- ip-api.com51ms
- proxycheck.io94ms
- abuseipdb139ms
- cloud-ranges5ms
- tor-exits5ms
- rdns1221ms
- shodan-internetdb142ms
- ipwho.is77ms
- dnsbl218ms
Machine-readable versions of this report: JSON · plain text · 中文报告