IPure IP purity check

IP purity report

103.172.81.131

68/ 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-22 12:58 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 · Yau Tsim Mong District · Mong Kok
IP type
Mobile network
Native / broadcast
Native IP
Network
AS146961 Nexet Limited
Reverse DNS
none
Devices seen in subnet
28

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

67

Borderline

Main issue: Proxy 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

75

Good fit

Main issue: Proxy 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

76

Good fit

Main issue: Proxy 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

70

Good fit

Main issue: Proxy IP

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

Email sending

SMTP · marketing email

43

Not recommended

Main issue: Blocklist hit: s5h.net

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

    Proxy IP

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

  • −12

    Blocklist hit: s5h.net

    Listed by s5h.net

  • −10

    1 open ports

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

  • −5

    No rDNS record

    No PTR record; IPs allocated by established carriers usually have one

  • +5

    IP type: Mobile network

    Mobile IPs are heavily shared but are generally treated as real users

  • +5

    Native IP

    Registered and used in the same country, allocated directly by a local carrier

Reputation

Blocklists and abuse history

Listed on 1 of 6 blocklists checked: s5h.net. 2 list(s) could not be queried this time.

  • abuseipdb abuse confidence 0%

Open ports observed: 22

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
    218ms
  • team-cymru
    118ms
  • ip-api.com
    132ms
  • proxycheck.io
    198ms
  • abuseipdb
    190ms
  • cloud-ranges
    19ms
  • tor-exits
    19ms
  • rdns
    680ms
  • shodan-internetdb
    234ms
  • ipwho.is
    154ms
  • dnsbl
    668ms

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