IP purity report
64.83.42.161
80/ 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-26 13:02 UTC. This describes IP-level risk only; platforms' internal risk data is not visible to us.
- VPN exit
Profile
What this IP is
- Country / region
- Japan · Tokyo · Tokyo
- IP type
- Business broadband
- Native / broadcast
- Native IP
- Network
- AS979 NTT America, Inc
- 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.
AI services
ChatGPT · Claude · Gemini
Borderline
Main issue: Known VPN exit
Least tolerant of data center and proxy exits: more likely to get degraded service, verification prompts or account limits. Spam history does not matter here
Social sign-up
X · Discord · Telegram · Reddit
Borderline
Main issue: Known VPN exit
Sign-up is the strictest checkpoint: data center / proxy exits are more likely to be asked for phone verification or refused, and IPs with bulk-registration history are blocked far more often
Streaming / short video
TikTok · Netflix · YouTube
Borderline
Main issue: Known VPN exit
Native IP and low sharing matter most: a broadcast IP reads as a region mismatch, and shared exits get throttled
Gaming platforms
Steam · PSN · Epic · Nintendo
Borderline
Main issue: Known VPN exit
Region locks, regional pricing and gifting all follow the IP's location, so broadcast IPs tend to be treated as cross-region; data center exits carry a high risk of restrictions
Cross-border e-commerce
Amazon · eBay · Shopee
Borderline
Main issue: Known VPN exit
Linked-account store closures are driven first by shared IPs, and only then by data center ranges
Email sending
SMTP · marketing email
Good fit
Main issue: Known VPN exit
Blocklists make or break deliverability, while sending from a data center IP is normal and is not penalised
Evidence
Why it got this score
- −20
Known VPN exit
Only 1 data source flags it as a VPN; the evidence is limited, so it counts at half weight
- What it means
- Commercial risk databases mark this address as a VPN server exit. Platforms see "someone on a VPN", not you.
- Which uses care
- Cares most: AI services, Social sign-up, Streaming / short video, Gaming platforms, Cross-border e-commerce
- Why it is weighted this way
- Only one source says so, and a single database can be wrong (public DNS resolvers have been mislabeled), so it counts at half weight. If a second source follows in a few days, this item doubles.
- Can it be fixed
- Self-hosted proxies on VPS ranges are often labeled block-wide; changing the IP is the only fix. Commercial VPN exits are labeled by design.
- −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
IP type: Business broadband
Business broadband is broadly trusted, though a small share are proxy exits
- What it means
- A business broadband address: generally trusted, though some corporate exits are used as proxies.
- 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
- A small deduction meaning "slightly less certain than residential".
- Can it be fixed
- An inherent attribute of the IP or its range; nothing a user can change short of a different IP.
- +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.
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%
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
- rdap458ms
- team-cymru59ms
- ip-api.com67ms
- proxycheck.io125ms
- abuseipdb129ms
- cloud-ranges10ms
- tor-exits10ms
- rdns581ms
- shodan-internetdb179ms
- ipwho.is84ms
- dnsbl225ms
Machine-readable versions of this report: JSON · plain text · 中文报告