1.14.70.12
IP Intelligence Dossier
Your IP: 216.73.216.123
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
IP Intelligence Briefing: 1.14.70.12
Date: 2026-06-10
**Profile Summary**
- Risk Score: 25 (Low Risk)
- Ownership: Registered to TencentCloud (AS45090) under James Tian in China.
- Geolocation: Chengdu, Sichuan, China (30.67°N, 104.07°E).
- Network Role: Firewalled with no open services; classified as infrastructure (no CDN, VPN, or hosting indicators).
- Threat Indicators: No malicious activity detected (no malware, phishing, or C2 indicators).
**Observation History**
- DNSBL Listings: Listed in 1 of 8 DNSBLs (confidence 85%), but no high-severity threats.
- BGP Data: Part of TencentCloud’s ASN 45090, with a stable route (no recent changes).
- Operator Score: Minimal risk (0.13), suggesting legitimate network operations.
**Relationships**
- Linked exclusively to TencentCloud network, indicating no external connectivity or peer relationships.
- No associated hostnames, certificates, or organizations.
**Neighborhood Analysis**
- Subnet: 1.14.70.12/24.
- Neighbor Count: 0 active IPs in the subnet (possible isolated host or incomplete data).
- Abuse Density: 0% (no malicious activity in the subnet).
**Recommendations**
- Monitor: Track DNSBL status and BGP route stability for anomalies.
- No Action Required: No immediate mitigation needed due to low risk and no malicious indicators.
- Investigate: Verify if the isolated subnet (1.14.70.12/24) is intentional or a data gap.
Conclusion: 1.14.70.12 is a low-risk IP associated with TencentCloud’s infrastructure. No signs of malicious activity; ongoing monitoring is advised.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | James Tian |
| ASN | AS45090 |
| Network Name | TencentCloud |
| CIDR Block | 1.12.0.0/14 |
| 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
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 | 13% | 1 | 1 |
| routing | 13% | 1 | 1 |
| services | 13% | 1 | 1 |
| ownership | 21% | 2 | 2 |
| reputation | 0% | 0 | 0 |
| geolocation | 13% | 1 | 1 |
| Overall | 12% | 6 | 6 |
Coverage: 5/6 dimensions · Data sufficiency: partial
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-23 18:27:50 UTC |
| Last Seen | 2026-06-10 09:20:43 UTC |
| Profile Built | 2026-06-10 09:53:14 UTC |
| Data Freshness | Live |
| Signal Types | 14 |
| Total Observations | 14 |
🔍 14 signal types · 14 observations collected
This report is generated from 14+ 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.