IPure IP purity check

IP purity report

137.220.194.110

20/ 100

Very high risk

confidence: high

Reputation is burned; almost every platform will block it.

Based on signals observed from public and partner data sources at 2026-09-27 04:06 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
Native IP
Network
AS152194 Rackip Consultancy Pte. LTD
Reverse DNS
mail.cunjin.net
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

45

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

37

Not recommended

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

54

Borderline

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

53

Borderline

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

34

Not recommended

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

0

Best avoided

Main issue: Blocklist hit: Spamhaus ZEN

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

Evidence

Why it got this score

  • −45

    Blocklist hit: Spamhaus ZEN

    SBL — known spam source; SBL DROP — recommended to drop the whole range

    What it means
    A Spamhaus listing means this IP was confirmed sending spam, or the machine is compromised and being used as a relay.
    Which uses care
    Cares most: Email sending; Barely looks at it: AI services, Social sign-up, Streaming / short video, Gaming platforms
    Why it is weighted this way
    This is behavioural evidence, not a profile guess, so it is a hard cap and fatal for email. It carries little weight for scenarios that ignore mail reputation, such as AI services.
    Can it be fixed
    Fix the cause first (shut down the compromised service, remove malware), then request removal from Spamhaus; usually resolved within days.
  • −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.
  • −10

    7 open ports

    Includes admin ports 22: clear evidence of a server rather than home broadband

    What it means
    Scanners see ports open on this IP. With admin ports such as 22 or 3389 it is almost certainly a server, not a home router.
    Which uses care
    Barely looks at it: AI services
    Why it is weighted this way
    Mainly corroboration that "this is a server", which the datacenter item already charged for, so only a few points here; AI-type scenarios weight it at 0.3 to avoid charging the same fact three times.
    Can it be fixed
    Close or restrict ports that do not need public access (firewall, non-default port, fail2ban); scanners update within days, then re-check. One of the few items you can change yourself.
  • −4

    4 known vulnerabilities

    Mostly matched from software version banners; it shows the machine is unmaintained, and platform risk systems do not look at this directly: CVE-2025-23419, CVE-2021-3618, CVE-2023-44487 and more

    What it means
    Scanners matched the version banners of exposed services to published CVE numbers. Most are just version matches, not confirmed exploitable holes.
    Which uses care
    Barely looks at it: AI services
    Why it is weighted this way
    It shows the machine is unmaintained, another sign of "server"; platform risk systems never count CVEs on an IP. Capped at 8 points (20 before 2026-09-26, which pushed ordinary VPS into "very high risk" for one fact charged three times).
    Can it be fixed
    Update the system and the services exposed to the internet (sshd above all); scanners update within days, then re-check.
  • −1

    Abuse reports (abuseipdb)

    Confidence 1%, 1 reports in the last 90 days

    What it means
    Someone reported this IP to an abuse database (AbuseIPDB), typically for SSH brute force, port scanning or comment spam. The reporter may have seen a program on this machine, or a previous tenant.
    Which uses care
    Cares most: Social sign-up, Email sending
    Why it is weighted this way
    Counted at half the database's confidence. Sign-up scenarios care most: IPs with bulk-registration or credential-stuffing history are their first priority to block.
    Can it be fixed
    Reports age out; with no new reports for 90 days the score drops. If your machine is the one scanning, check for implanted software first.
  • +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

Listed on 1 of 8 blocklists checked: Spamhaus ZEN.

  • abuseipdb abuse confidence 1%, 1 reports in 90 days

Open ports observed: 22, 80, 110, 143, 465, 993, 995

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
    467ms
  • team-cymru
    59ms
  • ip-api.com
    81ms
  • proxycheck.io
    162ms
  • abuseipdb
    468ms
  • cloud-ranges
    10ms
  • tor-exits
    10ms
  • rdns
    928ms
  • shodan-internetdb
    180ms
  • ipwho.is
    91ms
  • dnsbl
    205ms

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