202.137.155.17
IP Intelligence Dossier
Your IP: 216.73.216.123
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
Intelligence Briefing: IP 202.137.155.17/32
Overview:
- Risk Profile: Moderate risk (55/100). No active threats or malicious indicators detected.
- Ownership: Assigned to chindavone BOUNNHAVONG (LAOTELECOM) under APNIC. ASN 9873.
- Geolocation: Vientiane, Vientiane Prefecture, Laos (17.96°N, 102.6°E).
- Network Role: Firewalled host with no open services or TLS certificates.
Threat Indicators:
- No spam, attacker, or Tor exit node associations.
- No DNSBL listings or known malicious campaigns.
Observation History (30-Day Timeline):
- Latest Activity: Geolocation confirmed in Vientiane (2026-05-29).
- Subnet Abuse Density: 1/100 (low risk).
- Ownership Stability: No recent changes.
Relationships:
- Linked to LAOTELECOM (same network).
- No associated domains, certificates, or hostnames.
Neighborhood Analysis:
- Subnet: 202.137.155.17/24.
- Neighbors: 0 active IPs in subnet (possibly a single-host subnet or limited data).
- Abuse Density: 0% (clean).
Actionable Insights:
- No immediate mitigation required. Monitor for geolocation drift or unexpected service exposure.
- Verify ISP (LAOTELECOM) policies for potential network-level risks.
- No firewall rules or security actions recommended for this IP.
Conclusion:
The IP is associated with a Laotian ISP and shows no malicious behavior. Moderate risk stems from its network context, but no active threats are present. SOC teams should maintain baseline monitoring.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | chindavone BOUNNHAVONG |
| ASN | AS9873 |
| Network Name | LAOTELECOM |
| CIDR Block | 202.137.128.0/20 |
| RIR | APNIC |
| Country | LA |
| 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 | Multi-Service Host |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 22 | ssh | tcp | |
| Closed Ports | 25, 443, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
| SSH Version | SSH-2.0-dropbear_2013.62 ? ?74QC?J ?%$???curve25519-sha256@libssh.org,ecdh-sha2-nistp521,ecdh-sha2- |
🔐 TLS Certificate
No certificate
Issued by —
N/A
| SANs | None |
| Valid From | — |
| Valid Until | — |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 24% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 26% | 2 | 3 |
| ownership | 24% | 2 | 3 |
| reputation | 19% | 1 | 3 |
| geolocation | 13% | 1 | 1 |
| Overall | 20% | 9 | 14 |
Coverage: 6/6 dimensions · Data sufficiency: sufficient
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-11 15:04:52 UTC |
| Last Seen | 2026-06-26 10:35:58 UTC |
| Profile Built | 2026-06-26 10:47:56 UTC |
| Data Freshness | Live |
| Signal Types | 17 |
| Total Observations | 22 |
🔍 17 signal types · 22 observations collected
This report is generated from 17+ independent intelligence signals including
ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds,
behavioral fingerprinting, and more.
Full dossier details are available via our API.
Full dossier details are available via our API.
ℹ️ About This Report
All data shown is publicly available network metadata — IP addresses do not reliably identify individuals.
Assessments are probabilistic and should not be used as sole basis for access control decisions.
To report an issue or request data review, contact admin@ipdebrief.com.