IPure IP purity check

IP purity report

82.41.133.246

63/ 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-28 05:34 UTC. This describes IP-level risk only; platforms' internal risk data is not visible to us.

Profile

What this IP is

Country / region
Taiwan · Taipei City · Taipei
IP type
Business broadband
Native / broadcast
Broadcast IP
Network
AS213169 Catixs Ltd
Reverse DNS
newc-21-b2-v4wan-167773-cust1525.vm8.cable.virginm.net
Devices seen in subnet
67

Suitability

What it is good for

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

AI services

ChatGPT · Claude · Gemini

80

Good fit

Main issue: Broadcast IP

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

78

Good fit

Main issue: Broadcast IP

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

57

Borderline

Main issue: Broadcast IP

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

63

Borderline

Main issue: Broadcast IP

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

69

Borderline

Main issue: Broadcast IP

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

Email sending

SMTP · marketing email

62

Borderline

Main issue: Blocklist hit: DroneBL

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

Evidence

Why it got this score

  • −15

    Broadcast IP

    Range registered in GB but used in TW (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.
  • −12

    Blocklist hit: DroneBL

    Listed by DroneBL

    What it means
    This IP is on a public blocklist. Most lists record addresses that sent spam or took part in scanning or attacks.
    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
    A single aggregate list is moderate evidence, so about a dozen points; the email scenario more than doubles it because receiving servers query these lists directly.
    Can it be fixed
    Every list has a removal process, provided the cause is gone; some delist automatically after a quiet period.
  • −10

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

    Shared exit

    67 devices observed in the same subnet

    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.
  • +6

    rDNS looks residential

    Reverse hostname newc-21-b2-v4wan-167773-cust1525.vm8.cable.virginm.net matches residential broadband naming

    What it means
    The reverse hostname follows residential naming (prefixes like dyn, pppoe, cust).
    Which uses care
    Cares most: Email sending
    Why it is weighted this way
    A bonus: the carrier's naming indirectly confirms an access network.
    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: DroneBL.

  • abuseipdb abuse confidence 0%

Open ports observed: 22, 10050

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
    388ms
  • team-cymru
    92ms
  • ip-api.com
    161ms
  • proxycheck.io
    219ms
  • abuseipdb
    247ms
  • cloud-ranges
    13ms
  • tor-exits
    13ms
  • rdns
    573ms
  • shodan-internetdb
    246ms
  • ipwho.is
    167ms
  • dnsbl
    202ms

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