106.13.109.25
IP Intelligence Briefing: 106.13.109.25
Date: 2026-06-17
---
**1. Core Profile**
- Risk Score: 25 (Low Risk)
- Ownership: Baidu Noc (ASN 38365, APNIC)
- Geolocation: Beijing, China (CIDR 106.12.0.0/15)
- Network Role: Firewalled system with no services exposed (no open ports, TLS/HTTP inactive).
- Threat Indicators: No malicious activity detected (no blacklists, campaigns, or DNS threats).
---
**2. Observation History**
- Recent Activity (June 17, 2026):
- Listed in 3/8 threat feeds (high severity) with 85% confidence, though no direct malicious actions confirmed.
- DNSSEC validation reported as valid, but 1 DNSBL listing (potential spam/abuse risk).
- No persistent malicious behavior or network enumeration detected.
---
**3. Relationships**
- Linked Entities:
- Baidu Noc (same network).
- No external malicious domains, organizations, or certificates associated.
---
**4. Neighborhood Analysis**
- Subnet: 106.13.109.25/24
- Abuse Density: 0% (clean subnet).
- Neighbors: No active or risky sibling IPs detected.
---
**5. Actionable Insights**
- No immediate threat from this IP; it appears to be a legitimate Baidu infrastructure asset.
- Monitor DNSBL listings to ensure compliance and avoid potential spam associations.
- Verify DNSSEC configurations to mitigate spoofing risks, given the DNS validation signal.
- Maintain network segmentation to isolate internal systems like this one from public-facing assets.
Conclusion: 106.13.109.25 is a low-risk IP associated with Baidu’s network. No malicious activity observed, but routine monitoring is recommended for DNS and routing health.
---
*Generated using IPDebrief threat intelligence tools.*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Baidu Noc |
| ASN | AS38365 |
| Network Name | Baidu |
| CIDR Block | 106.12.0.0/15 |
| RIR | APNIC |
| Country | CN |
| Abuse Contact | — |
🌐 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 | Firewalled / No Services |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 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 | 31% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 8% | 1 | 1 |
| ownership | 19% | 2 | 2 |
| reputation | 21% | 1 | 3 |
| geolocation | 21% | 2 | 2 |
| Overall | 19% | 9 | 12 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-07 23:03:28 UTC |
| Last Seen | 2026-06-24 13:36:23 UTC |
| Profile Built | 2026-06-22 08:27:56 UTC |
| Data Freshness | Live |
| Signal Types | 16 |
| Total Observations | 17 |
Full dossier details are available via our API.