101.13.2.183
IP Intelligence Briefing: 101.13.2.183
Date: 2026-06-17
---
**1. IP Profile**
- Risk Score: 70 (High Risk)
- Owner: Johnny Wang (TAIWANMOBILE-NET, APNIC)
- Geolocation: Taipei, Taiwan (23.7°N, 120.96°E)
- Network Role: Firewalled / No Services (no open ports, TLS, or HTTP detected)
- BGP: Prefix `101.13.0.0/22`, origin ASN 24158 (TAIWANMOBILE-NET)
- DNSSEC: Valid
- Threat Indicators: No active threats, spam, or known attacker associations
---
**2. Observation History**
- Recent Activity (June 17, 2026):
- Listed in 3/8 threat intelligence feeds (confidence: 85%).
- Geolocation validated via multi-signal inference (latitude: 23.7, longitude: 120.96).
- Subnet Analysis:
- Subnet `101.13.2.183/24` has 4 total IPs, 2 active, 1 flagged as risky.
- Abuse density: 25% (mostly clean).
- Geolocation Limitations:
- ICMP blocked, preventing RTT validation. Estimated distance from probe: 9,416.5 km.
---
**3. Network Relationships**
- Shared Network: TAIWANMOBILE-NET (APNIC)
- Subnet Peers:
- 101.13.2.182 (Risk Score: 70), 101.13.2.234 (25), 101.13.2.240 (55).
- Control Plane:
- RPKI state: Unknown. IRR consistency: Matched. Route stability: Unstable.
---
**4. Neighborhood Analysis**
- Subnet Abuse Density: 25% (1/4 IPs flagged).
- Neighbor Risk Distribution:
- 1 high-risk IP (70), 1 medium-risk IP (55), 1 low-risk IP (25).
- Subnet Classification: "Mostly Clean" with inherited risk score of 2.
---
**5. Recommendations**
- Monitor Subnet: Track neighbors (especially 101.13.2.182) for suspicious activity.
- Geolocation Verification: Use alternative methods to validate IP location due to ICMP blocking.
- Provider Context: Note TAIWANMOBILE-NET’s role in mobile networks; ensure no misattribution of traffic.
- Threat Feeds: Recheck listings in 3/8 feeds (e.g., DNSBLs) for potential false positives.
---
End of Briefing
*Generated via IPDebrief intelligence tools. All data reflects observations as of 2026-06-17.*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Johnny Wang |
| ASN | AS24158 |
| Network Name | TAIWANMOBILE-NET |
| CIDR Block | 101.8.0.0/13 |
| RIR | APNIC |
| Country | TW |
| 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 | Web Server |
| Network Tier | Tier 3 — Basic operator with some routing infrastructure |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| Closed Ports | 22, 25, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | lighttpd/1.4.30 |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | 2021-08-19T19:59:29+00:00 |
| Valid Until | 2031-08-17T19:59:29+00:00 |
| TLS Protocol | Tls12 |
| Cipher Suite | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 3650 days |
| Serial Number | 00AF099DE2B0C4BDCC |
| Thumbprint | D0AAF5A46B8FACE2FBAD41F734D9C7AEF0CB6F08 |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 32% | 2 | 3 |
| routing | 22% | 3 | 3 |
| services | 15% | 2 | 2 |
| ownership | 27% | 2 | 3 |
| reputation | 17% | 1 | 2 |
| geolocation | 32% | 2 | 3 |
| Overall | 24% | 12 | 16 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (65%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-07 23:03:24 UTC |
| Last Seen | 2026-06-25 01:47:02 UTC |
| Profile Built | 2026-06-22 05:37:19 UTC |
| Data Freshness | Live |
| Signal Types | 23 |
| Total Observations | 25 |
Full dossier details are available via our API.