IP purity report
66.249.88.165
72/ 100
Fair
confidence: high
Usable; platforms with strict risk controls may occasionally show a CAPTCHA.
Based on signals observed from public and partner data sources at 2026-09-29 09:41 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 · California · Mountain View
- IP type
- Hosting / data center
- Native / broadcast
- Native IP
- Network
- AS15169 Google LLC
- Reverse DNS
- google-proxy-66-249-88-165.google.com
- Devices seen in subnet
- 1500
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.
- −20
rDNS looks like a proxy
Reverse hostname google-proxy-66-249-88-165.google.com contains proxy/VPN keywords
- What it means
- The reverse hostname of this IP contains words like vpn or proxy: the carrier itself labels it a proxy exit.
- Which uses care
- Cares most: Email sending
- Why it is weighted this way
- A self-description by the operator is more trustworthy than a third-party guess, hence a sizable deduction.
- Can it be fixed
- Reverse DNS is set by the IP's owner; users cannot change it.
- −6
Heavily shared exit
1500 devices observed in the same subnet; higher risk of guilt by association
- What it means
- Many devices share this exit. Whatever others do on it gets attributed to you as well.
- Which uses care
- Cares most: Social sign-up, Streaming / short video, Cross-border e-commerce
- Why it is weighted this way
- Cross-border e-commerce and social sign-up care most: shared IPs are the leading cause of linked-account bans.
- Can it be fixed
- Move to a dedicated or low-share exit; sharing levels vary widely between plans from the same vendor.
- +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 8 blocklists checked (Spamhaus ZEN, SpamCop, PSBL, blocklist.de, UCEPROTECT L1, s5h.net, DroneBL, SpamRats).
- abuseipdb abuse confidence 0%, 18 reports in 90 days
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
- rdap221ms
- team-cymru98ms
- ip-api.com96ms
- proxycheck.io170ms
- abuseipdb201ms
- cloud-ranges17ms
- tor-exits17ms
- rdns894ms
- shodan-internetdb202ms
- dnsbl889ms
Machine-readable versions of this report: JSON · plain text · 中文报告