IPure IP purity check

IP purity report

216.236.27.14

44/ 100

High risk

confidence: high

Most platforms will add verification or block outright; consider replacing it.

Based on signals observed from public and partner data sources at 2026-09-18 09:21 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 · Kowloon · Hong Kong
IP type
Hosting / data center
Native / broadcast
Native IP
Network
AS1405 Caelus Technology LLC
Reverse DNS
none
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

—

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

18

Best avoided

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

34

Not recommended

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

32

Not recommended

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

30

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

46

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

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

    Proxy IP

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

    What it means
    A source marks this address as a proxy exit without saying whether it is a VPN, a datacenter proxy or something else.
    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, so it counts at half weight.
    Can it be fixed
    These labels are usually applied to whole ranges and are hard to clear by behaviour; moving to an unlabeled range is the practical fix.
  • −12

    Blocklist hit: s5h.net

    Listed by s5h.net

    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

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

    Spamhaus ZEN: residential range declaration

    PBL — range judged dynamic by Spamhaus

    What it means
    Spamhaus PBL declares this range as dynamic residential space that should not send mail directly. Not a stain: it is evidence of home broadband.
    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
    Counted as a bonus because it indirectly confirms a real 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: s5h.net.

  • 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
    593ms
  • team-cymru
    69ms
  • ip-api.com
    69ms
  • proxycheck.io
    155ms
  • abuseipdb
    111ms
  • cloud-ranges
    8ms
  • tor-exits
    8ms
  • rdns
    629ms
  • shodan-internetdb
    372ms
  • ipwho.is
    106ms
  • dnsbl
    243ms

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