IP 103.41.5.141 was classified as Low Risk with a risk score of 25. Ownership was attributed to IRT-JUNIUYUN-CN (ASN 138415) within the APNIC RIR, geolocated to Hong Kong. No threat indicators were recorded; the IP maintained a zero blacklist count and had no associations with known attacker campaigns. Network activity revealed a Single-Service Host profile with an open SSH service on port 22 (OpenSSH_10.0p2 Debian). DNS analysis confirmed no forward or reverse resolutions and zero hosted domains. Although route stability status was flagged as false, no route changes were observed over the preceding 30 days. Based on the low-risk classification and lack of malicious indicators, the asset is recommended for standard monitoring without immediate blocking.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | IRT-JUNIUYUN-CN |
| ASN | AS138415 |
| Network Name | JUNIUYUN-CN |
| CIDR Block | 103.41.4.0/22 |
| RIR | APNIC |
| Country | HK |
| 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 | Banner detected |
| Closed Ports | 25, 80, 443, 3389, 8080, 8443 (1 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS138415 |
| Network Prefix | 103.41.4.0/22 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 21% | 2 | 4 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 34% | 2 | 6 |
| reputation | 8% | 1 | 2 |
| geolocation | 23% | 2 | 4 |
| Overall | 18% | 10 | 19 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-20 18:35:06 UTC |
| Last Seen | 2026-09-05 12:45:46 UTC |
| Profile Built | 2026-09-05 12:54:56 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 34 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 103.41.5.141
Who owns the IP address 103.41.5.141?
103.41.5.141 is registered to IRT-JUNIUYUN-CN. The address falls within the 103.41.4.0/22 network block. Registration is held at APNIC.
Where is 103.41.5.141 located?
Geolocation data places 103.41.5.141 in Hong Kong, HK, Hong Kong. The local time zone is Asia/Hong_Kong. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 103.41.5.141 malicious or safe?
103.41.5.141 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.
What ports are open on 103.41.5.141?
Responsive ports observed on 103.41.5.141 include 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.