112.124.67.212
IP INTELLIGENCE BRIEFING
Target: 112.124.67.212/32
Classification: Low Risk / Clean
Date: 2026-07-29
---
EXECUTIVE SUMMARY
The target IP address 112.124.67.212 is classified as low risk with an overall risk score of 25/100. No active threat indicators, malware distribution, or malicious activity have been observed. The address belongs to a clean subnet with minimal abuse density.
---
TECHNICAL PROFILE
- Ownership: ALISOFT (ASN 37963, RIR: APNIC)
- Organization: security trouble
- Location: Hangzhou, Zhejiang Province, China (30.29°N, 120.17°E)
- Network Block: 112.124.0.0/14
- Service Status: Firewalled / No Services Detected
- Open Ports: None identified
- TLS Certificates: None
- Hosted Domains: 0
---
THREAT ASSESSMENT
- Risk Score: 25 (Low Risk)
- Abuse Confidence Score: Not applicable
- Known Attacker: No
- Spam Source: No
- Tor Exit Node: No
- Blacklist Count: 0 active listings
- DNSBL Status: Listed on 1 of 8 evaluated lists (minor concern)
- Threat Persistence: 0 days observed
- Campaign Correlation: None detected
---
NETWORK CONTEXT
- Subnet Classification: Clean (112.124.67.0/24)
- Abuse Density: 0%
- Threat Siblings: 0
- Active Siblings: 0
- Total Subnet IPs Analyzed: 2
- Neighboring IPs: 1 (112.124.67.154, risk score: 0)
- Route Stability: Unstable (false)
- BGP Prefix: 112.124.0.0/17
---
RELATIONSHIP GRAPH
- Direct Associations: 2 relationships identified
- Network Affiliation: ALISOFT (repeated entries)
- Organizational Links: None beyond network affiliation
- Hostname/Certificate Links: None detected
---
OBSERVATION HISTORY
- Total Signals Observed: 12
- Most Recent: 2026-07-29 23:19:41 UTC
- Signal Confidence: 0.40 (subnet classification), 0.50 (geo validation), 0.70-0.95 (org/ASN data)
- Data Quality: Organization and ASN signals show high confidence (0.90-0.95)
- Validation Status: ICMP probes blocked (ICMP validation unavailable)
---
RECOMMENDATION
NO IMMEDIATE ACTION REQUIRED. The IP address presents a low-risk profile with no evidence of malicious activity. The single DNSBL listing is minor and does not warrant blocking. Standard monitoring applies. If the IP is not legitimately expected in your traffic flow, consider reviewing the DNSBL listing for context.
Priority: LOW
Recommended Action: Monitor / No Action
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | security trouble |
| ASN | AS37963 |
| Network Name | ALISOFT |
| CIDR Block | 112.124.0.0/14 |
| RIR | APNIC |
| Country | CN |
| 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 | 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 | 25% | 1 | 1 |
| routing | 25% | 1 | 1 |
| services | 25% | 1 | 1 |
| ownership | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 0% | 0 | 0 |
| Overall | 12% | 3 | 3 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-24 14:25:37 UTC |
| Last Seen | 2026-07-29 23:17:44 UTC |
| Profile Built | 2026-07-29 23:31:10 UTC |
| Data Freshness | Live |
| Signal Types | 18 |
| Total Observations | 18 |
Full dossier details are available via our API.