IPure IP purity check

IP purity report

82.41.50.70

67/ 100

Suspicious

confidence: high

Mediocre reputation; not recommended for long-term use with important accounts.

Based on signals observed from public and partner data sources at 2026-09-26 06:55 UTC. This describes IP-level risk only; platforms' internal risk data is not visible to us.

Profile

What this IP is

Country / region
Japan · Tokyo · Tokyo
IP type
Hosting / data center
Native / broadcast
Broadcast IP
Network
AS61112 Akile LTD
Reverse DNS
mail.abrd50-75.enqer.in.necym.com
Devices seen in subnet
1

Suitability

What it is good for

Each use case weighs the evidence differently; these are not one overall score.

AI services

ChatGPT · Claude · Gemini

49

Not recommended

Main issue: IP type: Hosting / data center

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

57

Borderline

Main issue: IP type: Hosting / data center

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

44

Not recommended

Main issue: IP type: Hosting / data center

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

42

Not recommended

Main issue: IP type: Hosting / data center

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

55

Borderline

Main issue: IP type: Hosting / data center

Linked-account store closures are driven first by shared IPs, and only then by data center ranges

Email sending

SMTP · marketing email

92

Excellent fit

No notable obstacle found for this use case

Blocklists make or break deliverability, while sending from a data center IP is normal and is not penalised

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.
  • −15

    Broadcast IP

    Range registered in CN but used in JP (announced across borders)

    What it means
    The country the range is registered in differs from where it is actually used. Common when an international host uses a range registered in country A inside country B, or when a proxy vendor leases ranges.
    Which uses care
    Cares most: Streaming / short video, Gaming platforms; Barely looks at it: Email sending
    Why it is weighted this way
    Region-sensitive platforms (streaming, region-locked gaming) care most: they cross-check several geo databases and treat a mismatch as "wrong region". Little effect on scenarios that ignore region.
    Can it be fixed
    This is a registration attribute of the range and cannot be changed by the user. Platforms use different geo databases, so some may not notice at all.
  • +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.
  • +4

    Very low observed sharing

    Only 1 devices observed in the same subnet

    What it means
    Only a few devices were observed in the same subnet. Your behaviour mostly represents you alone.
    Which uses care
    Cares most: Social sign-up, Streaming / short video, Cross-border e-commerce
    Why it is weighted this way
    A small bonus. This is an observation, not proof of true exclusivity.
    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 6 blocklists checked (Spamhaus ZEN, SpamCop, PSBL, blocklist.de, UCEPROTECT L1, s5h.net, DroneBL, SpamRats). 2 list(s) could not be queried this time.

  • 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

  • rdap
    748ms
  • team-cymru
    147ms
  • ip-api.com
    169ms
  • proxycheck.io
    563ms
  • abuseipdb
    547ms
  • cloud-ranges
    10ms
  • tor-exits
    10ms
  • rdns
    924ms
  • shodan-internetdb
    467ms
  • ipwho.is
    610ms
  • dnsbl
    920ms

Machine-readable versions of this report: JSON · plain text · 中文报告