IPure IP purity check

IP purity report

43.199.29.225

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-22 09:15 UTC. This describes IP-level risk only; platforms' internal risk data is not visible to us.

Profile

What this IP is

Country / region
Hong Kong · Central and Western District · Hong Kong
IP type
Hosting / data center
Native / broadcast
Broadcast IP
Network
AS16509 AWS EC2 (ap-east-1)
Reverse DNS
ec2-43-199-29-225.ap-east-1.compute.amazonaws.com
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

—

Region not supported

ChatGPT / Claude / Gemini are not offered in this region and it cannot connect directly; a clean IP in a supported region is needed

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

Unusable

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

0

Unusable

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

0

Unusable

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

0

Unusable

Main issue: Honeypot node

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

Email sending

SMTP · marketing email

0

Unusable

Main issue: Honeypot node

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

Evidence

Why it got this score

  • −40

    Honeypot node

    Flagged as a honeypot; its traffic gets close attention from security vendors

  • −25

    IP type: Hosting / data center

    Hosting / data center IPs are the main source of automated traffic

  • −20

    Known VPN exit

    Only 1 data source flags it as a VPN; the evidence is limited, so it counts at half weight

  • −20

    1550 known vulnerabilities

    Unpatched machines are easily compromised and turned into proxy exits: CVE-2011-4354, CVE-2007-4660, CVE-2007-3998 and more

  • −15

    Broadcast IP

    Range registered in US but used in HK (announced across borders)

  • −12

    Blocklist hit: DroneBL

    Listed by DroneBL

  • −10

    2145 open ports

    Includes admin ports 22, 23, 3389, 5900, 5901: clear evidence of a server rather than home broadband

  • −8

    Cloud provider range (AWS)

    Public cloud IPs can be rented cheaply by anyone, so they rate below self-run data centers

  • −6

    rDNS looks like a server

    Reverse hostname ec2-43-199-29-225.ap-east-1.compute.amazonaws.com matches server naming

  • +4

    Very low observed sharing

    Only 2 devices observed in the same subnet

Reputation

Blocklists and abuse history

Listed on 1 of 8 blocklists checked: DroneBL.

  • abuseipdb abuse confidence 0%

Open ports observed: 11, 13, 15, 17, 19, 20, 21, 22, 23, 25, 26, 37

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
    69ms
  • team-cymru
    58ms
  • ip-api.com
    35ms
  • proxycheck.io
    108ms
  • abuseipdb
    232ms
  • cloud-ranges
    3ms
  • tor-exits
    3ms
  • rdns
    180ms
  • shodan-internetdb
    129ms
  • ipwho.is
    32ms
  • dnsbl
    226ms

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