IPDebrief

39.181.37.144

IP Intelligence Dossier
Your IP: 216.73.216.123
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

IP Intelligence Briefing: 39.181.37.144

Date: 2026-06-09

---

**1. Overview**

---

**2. Ownership & Infrastructure**

---

**3. Threat & Risk Observations**

- Flagged in 8 DNSBLs (high severity in 1).

- No recent abuse reports or spam activity.

- Route stability: Unstable (routeChanges30d = 0, isRouteStable = false).

- RPKI valid, no route hijack detected.

- 13 observations since 2026-06-02.

- Last notable event: DNSBL listing (confidence 0.85).

---

**4. Network Relationships**

- 39.181.37.145: Moderate risk (50/100).

- 39.181.37.173: Low risk (25/100).

- 39.181.37.180: Moderate risk (50/100).

- 39.181.37.182: Minimal risk (0/100).

---

**5. Actionable Intelligence**

- Monitor for unexpected traffic patterns or DNSBL re-listings.

- Verify if the IP is part of a larger network compromise (e.g., compromised China Mobile subnet).

- Consider blocking DNSBL-listed IPs in the subnet (e.g., 39.181.37.145).

- Temporarily block 39.181.37.144/24 to investigate potential lateral movement.

- Whitelist China Mobile’s ASN (56041) if the IP is part of legitimate infrastructure.

---

Conclusion:

The IP is owned by a major Chinese ISP and shows no direct malicious activity. However, its association with DNSBL listings and unstable routing warrants closer monitoring. SOC teams should prioritize validating the IP’s role in the network and investigate potential upstream compromises.

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.

🌍 Geolocation

CountryπŸ‡¨πŸ‡³ China
RegionJinrong Ave., Xicheng District, Beijing,
City29
Timezoneβ€”
Latitude34.77
Longitude113.72

🏒 Ownership & Registration

OrganizationIRT-CHINAMOBILE-CN
ASNAS56041
Network NameCMNET
CIDR Block39.128.0.0/10
RIRAPNIC
CountryCN
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)

πŸ” DNS Hygiene

Hygiene Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

☁️ Network Classification

InfrastructureMobile
Service PurposeFirewalled / No Services
Network TierUnknown β€” Insufficient routing data to classify
Mobile

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Closed Ports22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned)
Serverβ€”
HTTP Titleβ€”

πŸ” TLS Certificate

πŸ”’
No certificate
Issued by β€”
N/A
SANsNone
Valid Fromβ€”
Valid Untilβ€”

🎯 Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
13%
11
routing
13%
11
services
13%
11
ownership
27%
23
reputation
0%
00
geolocation
13%
11
Overall13%67
Coverage: 5/6 dimensions Β· Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-22 09:13:07 UTC
Last Seen2026-06-09 20:41:29 UTC
Profile Built2026-06-09 20:56:52 UTC
Data FreshnessLive
Signal Types16
Total Observations16
πŸ” 16 signal types Β· 16 observations collected
This report is generated from 16+ 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.
{ } JSON API πŸ”§ Actions API πŸ“§ Enterprise Access

ℹ️ 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.