IPure IP purity check

IP purity report

43.130.26.3

0/ 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-26 18:54 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 · Santa Clara
IP type
Hosting / data center
Native / broadcast
Native IP
Network
AS132203 Tencent Cloud Computing
Reverse DNS
none
Devices seen in subnet
2

Suitability

What it is good for

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

AI services

ChatGPT · Claude · Gemini

0

Best avoided

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

0

Best avoided

Main issue: Abuse reports (abuseipdb)

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

0

Best avoided

Main issue: Abuse reports (abuseipdb)

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

0

Best avoided

Main issue: Abuse reports (abuseipdb)

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

0

Best avoided

Main issue: Abuse reports (abuseipdb)

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

  • −50

    Abuse reports (abuseipdb)

    Confidence 100%, 590 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.
  • −45

    Blocklist hit: Spamhaus ZEN

    XBL — compromised host / open proxy; PBL — range judged dynamic by Spamhaus

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

    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 2 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.
  • +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 2 of 8 blocklists checked: Spamhaus ZEN, DroneBL.

  • abuseipdb abuse confidence 100%, 590 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

  • rdap
    239ms
  • team-cymru
    68ms
  • ip-api.com
    72ms
  • proxycheck.io
    107ms
  • abuseipdb
    527ms
  • cloud-ranges
    9ms
  • tor-exits
    9ms
  • rdns
    1222ms
  • shodan-internetdb
    147ms
  • ipwho.is
    73ms
  • dnsbl
    216ms

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