IP abuse report128.14.239.38
128.14.239.38 is an IPv4 address located in Taipei, Taiwan. It belongs to a network operated by UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED (AS135377). The address is listed by 4 of the threat-intelligence sources we track and carries a confidence score of 90/100. No community reports have been filed for it yet.
Provider notified This IP was reported to its network operator UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED · 2026-09-23 · IPDB-AR-000069 Awaiting reply Show detailsHide
- DetectedScore 92/100
- Notice sent2026-09-23 00:47
- Delivereducloud.cn
- Operator response Waiting · 1 month ago
The IP-DB Abuse Desk sent an abuse notice with supporting evidence to UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED's registered abuse contact on 2026-09-23 00:47: unoc@ucloud.cn
IP Information
- ISP / Organization
- UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED
- ASN
- AS135377 UCLOUD-HK-AS-AP
- ASN Domain
- ucloud.cn
- IP Range
- 128.14.239.0/24
- Regional Registry
- ARIN
- Connection Type
- Hosting / Datacenter
- Country
- Taiwan (TW)
- Region / State
- Taiwan
- City
- Taipei
- Time Zone
- Unknown
- Abuse contact
- unoc@ucloud.cn The abuse mailbox this network lists with its regional registry. Report traffic from this IP here, with logs and timestamps.
City is an estimate. The country is reliable; the city varies by provider.
Approximate location
City level- Coordinates
- 25.03, 121.56
- Network
- AS135377 UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED
The point is the city centre given by IP geolocation databases, not a street address. The circle shows the area of uncertainty.
Network Neighbourhood
128.14.239.0/243 of the 256 addresses in 128.14.239.0/24 are listed by our sources (1.2%).
Only a small part of the block is listed, which is more consistent with an isolated incident than with the network itself.
An address is not guiltier for having a few listed neighbours, which is why this stays out of the confidence score entirely while the block is mostly clean. It contributes at most 20 points, and only once a substantial share of the block is listed — that ceiling is deliberate: neighbours alone can raise an address to "low" and no further.
Threat Evidence
Last 30 days: how many feeds listed this address each day, and the community reports filed.
What this address is listed for: feed categories count sources, community categories count reports.
Where community reports were filed from. Only the reporter's country is shown, never their address.
When each feed first and last carried this address, over the last 30 days.
Blacklist Matches
4In our pool since: 2026-08-28 11:17 (2 months ago) · Last confirmed: 2026-11-20 03:49
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| FireHOL Level 3 Aggregator | 128.14.239.38/31 | 2026-11-19 21:57 | 2026-11-20 04:184 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Data-Shield IPv4 Blocklist | Single address | 2026-11-07 19:33 | 2026-11-20 04:193 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| CINS Army List | Single address | 2026-11-20 04:17 | 2026-11-20 04:176 minutes ago |
| ThreatView High Confidence | Single address | 2026-11-20 02:47 | 2026-11-20 04:185 minutes ago |
“Confirmed” is the moment the address was still on that source at its most recent fetch — the feeds are replaced wholesale on every refresh. Per-source “first seen” only began being recorded on 30 August 2026, so for listings older than that this column shows the start of record-keeping. The address-level history is the “in our pool since” value above.
Catch addresses like this on your own server
Sensor opens realistic decoy services — FortiGate, GlobalProtect, Exchange, NetScaler and more — on your server's unused ports. Every address that touches them is logged with evidence, and your firewall, fail2ban and Shield pull the same list to block it.
- Realistic decoys for VPN gateways, mail, web panels and databases
- Names exploit attempts by their CVE signature
- One-command install; runs unprivileged and never touches your real services
While a Sensor reports, your daily API quota rises to 30,000 lookups.
- 14:02:07 ssh:22 128.14.239.38 login attempt root / ••••••
- 14:02:10 globalprotect:443 128.14.239.38 exploit attempt CVE-2024-3400
- 14:02:13 owa:4443 128.14.239.38 password spray Exchange OWA
- 14:02:16 netscaler:8443 128.14.239.38 Citrix Bleed scan CVE-2023-4966
- 14:02:20 ✓ evidence logged → added to your blocklist
Community Reports 0
Report This IPNo community reports yet for this IP.
Report This IPListing History
1The pool is a live picture: an address listed today leaves it when the sources drop it. This record outlives that removal — “listed on 12 August, delisted on 3 September” is truer than either a permanent accusation or a blank page. Events are kept for 400 days.
Frequently asked questions about 128.14.239.38
Is 128.14.239.38 safe?
No. 128.14.239.38 scores 90/100 with strong, recent evidence of abuse (4 sources). Blocking it at your firewall is advisable.
Who owns 128.14.239.38?
128.14.239.38 is announced by AS135377 and operated by UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED. It sits in the 128.14.239.0/24 block registered with ARIN.
Where is 128.14.239.38 located?
Geolocation places 128.14.239.38 in Taipei, Taiwan. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.
Is 128.14.239.38 on a blacklist?
Yes. 128.14.239.38 is currently listed by 4 threat sources: CINS Army List, ThreatView High Confidence, Data-Shield IPv4 Blocklist, FireHOL Level 3.
How do I report abuse from 128.14.239.38?
Send your log lines to the network's abuse contact, unoc@ucloud.cn, and file a report on IP-DB so others can see it too.
Run this check via the API
The same score and evidence are available as JSON, free with an API key.
API documentation →curl -H "Key: YOUR_API_KEY" https://ip-db.com/api/v1/check/128.14.239.38