103.14.33.129
## Threat Intelligence Briefing: 103.14.33.129/32
Executive Summary
IP 103.14.33.129 presents as a Moderate Risk (Score: 40) single-service host operating within a /24 subnet showing minimal operator footprint. The address exhibits DNSBL listings (2 of 8 lists) and maintains route instability, warranting defensive monitoring.
Network Classification & Infrastructure
- ASN: 135377 | BGP Prefix: 103.14.33.0/24
- Operator Score: 0.1304 (Minimal)
- Network Role: Single-Service Host
- Route Stability: Unstable (0 route changes in 30d)
- DNSSEC: Valid
Service Fingerprint
- Open Port: 22/TCP (SSH)
- SSH Banner: SSH-2.0-OpenSSH_7.4
- HTTP/TLS: None detected
- Forward Resolution: Confirmed
Threat Indicators
- DNSBL Listings: 2 of 8 total blacklists
- Known Attacker: No
- Tor Exit Node: No
- Spam Source: No
- Campaign Correlation: None detected
Neighborhood Context
Subnet 103.14.33.0/24 contains 2 medium-risk neighbors:
- 103.14.33.174: Risk Score 50
- 103.14.33.183: Risk Score 40
- Abuse Density: 0
Temporal Analysis
- Observations: 7 historical records
- Threat Observation Count: 0
- Persistence Days: 0
- Ownership Changes: 0
- Recent Signal: Operator score 0.1304 observed 2026-07-30
Intelligence Assessment
The IP lacks traditional threat signatures (no active campaigns, no known attacker status) but exhibits reputation concerns through DNSBL presence. The single-SSH-service profile with OpenSSH 7.4 suggests potential legacy infrastructure or compromised host. Neighboring IPs in the /24 share similar medium-risk profiles, indicating coordinated or related deployment patterns.
Recommended Actions
1. Monitor inbound SSH traffic for brute force activity
2. Block or rate-limit port 22 at perimeter if risk tolerance is low
3. Correlate with 103.14.33.174 and 103.14.33.183 for campaign intelligence
4. Review DNSBL listings to determine blocklist sources and severity
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Benny Huang |
| ASN | AS135377 |
| Network Name | UCloud-HK-002 |
| CIDR Block | 103.14.33.0/24 |
| RIR | APNIC |
| Country | CN |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
🔐 DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Single-Service Host |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 22 | ssh | tcp | |
| Closed Ports | 25, 80, 443, 3389, 8080, 8443 (1 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
| SSH Version | SSH-2.0-OpenSSH_7.4 |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 25% | 1 | 1 |
| routing | 25% | 1 | 1 |
| services | 35% | 2 | 2 |
| ownership | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 0% | 0 | 0 |
| Overall | 14% | 4 | 4 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-26 21:27:25 UTC |
| Last Seen | 2026-08-13 06:43:19 UTC |
| Profile Built | 2026-07-30 09:08:16 UTC |
| Data Freshness | Live |
| Signal Types | 16 |
| Total Observations | 16 |
Full dossier details are available via our API.