# 116.179.32.215 — IP Intelligence Summary

116.179.32.215 is an IPv4 address operated by IRT-UNICOM-CN (AS4837), geolocated to Beijing 100140, China. It belongs to a mobile network with reverse DNS name baiduspider-116-179-32-215.crawl.baidu.com. As of October 7, 2026, IPDebrief rates it Low Risk (25/100); no anonymizing service was detected.

- Canonical page: https://ipdebrief.com/116.179.32.215
- Last updated: 2026-10-07

## Ownership

- Organization: IRT-UNICOM-CN
- Network name: UNICOM
- Allocated block: 116.128.0.0/10
- ASN: AS4837 (https://ipdebrief.com/asn/4837)
- Regional registry: APNIC

## Location

- City: Beijing 100140
- Region: P.R.China
- Country: China
- Time zone: —

## Network classification

- Infrastructure type: —
- Datacenter / hosting: no
- Residential: no
- Mobile: yes
- Anycast: no
- Tor exit node: no
- VPN: no
- Proxy: no

## Risk assessment

- Assessment: Low Risk (25/100)
- Blocklist listings: 0
- Suspicious activity indicators: no
- Spam source: no

## Reverse DNS

- baiduspider-116-179-32-215.crawl.baidu.com
- Forward-confirmed: yes

## Analyst narrative

**IP INTELLIGENCE BRIEFING**

**IP Address:** 116.179.32.215/32

**Date:** 2026-07-24

**Classification:** Low Risk

**EXECUTIVE SUMMARY**

Target IP 116.179.32.215 is a mobile carrier infrastructure address assigned to China Unicom (ASN 4837, IRT-UNICOM-CN) with current risk score of 0. The IP is geolocated to Beijing, China, operates as a firewalled mobile carrier endpoint with no active services, and shows minimal threat indicators. No immediate blocking or mitigation actions recommended based on current risk profile.

**OWNERSHIP & NETWORK CLASSIFICATION**

\- **ASN:** AS4837 (China Unicom / china unicom china169 backbone)

\- **Organization:** IRT-UNICOM-CN

\- **CIDR Block:** 116.128.0.0/10

\- **Network Type:** Mobile Carrier (China Unicom, LTE/5G technology)

\- **Geolocation:** Beijing, P.R. China (34.77°N, 113.72°E)

\- **Registration:** APNIC RIR

**THREAT POSTURE**

\- **Overall Risk Score:** 0 (Low Risk)

\- **Blacklist Status:** 0 entries

\- **Known Attacker:** No

\- **Tor Exit Node:** No

\- **Spam Source:** No

\- **Threat Persistence:** Not persistently malicious

\- **Threat Observation Count:** 0

**NETWORK SERVICES & DNS**

\- **Open Ports:** None detected (Firewalled / No Services)

\- **PTR Hostnames:** None

\- **Forward Resolution:** 0 records

\- **DNS Records:** No hosted domains, no SPF/DMARC records

\- **TLS Certificates:** None

**HISTORICAL SIGNAL ANALYSIS**

Six historical observations recorded on 2026-07-24. Analysis reveals:

\- ASN and geographic data consistent across observations

\- One signal (alienvault-otx) indicated potential threats with 14 pulse references, though overall risk scoring remained at 0

\- Ownership data stable with abuse contact available via RDAP

\- No significant changes in network classification or threat indicators

**NETWORK NEIGHBORHOOD ANALYSIS**

Subnet 116.179.32.0/24 analyzed:

\- **Total Neighbors:** 100 IPs

\- **Risk Distribution:** 0 High, 40 Medium, 50 Low

\- **Abuse Density:** 0 (minimal)

\- **Classification:** Provider infrastructure

Multiple neighboring IPs show risk score of 50 and authority score of 60, indicating moderate subnet activity typical of mobile carrier ranges.

**RELATIONSHIP MAPPING**

Single relationship identified:

\- **Network Affiliation:** UNICOM (Same Network)

\- No hostname, certificate, or organizational relationships detected

**RECOMMENDED ACTIONS**

\- **Firewall Rules:** None required (risk score 0)

\- **Threat Intelligence:** Continue monitoring; no immediate action

\- **SOC Guidance:** Treat as legitimate carrier infrastructure. No blocking or alerting necessary based on current profile.

**ASSESSMENT**

IP 116.179.32.215 represents standard mobile carrier infrastructure with minimal threat indicators. The zero risk score, absence of blacklist entries, and lack of active services classify this as a benign provider endpoint. Historical signals indicate occasional threat associations in the broader mobile carrier ecosystem, but the specific IP shows no active malicious behavior. SOC analysts may log for reference but should not flag for investigation without additional context.

## Nearby addresses

- 116.179.32.12 (https://ipdebrief.com/116.179.32.12)
- 116.179.32.13 (https://ipdebrief.com/116.179.32.13)
- 116.179.32.14 (https://ipdebrief.com/116.179.32.14)
- 116.179.32.15 (https://ipdebrief.com/116.179.32.15)
- 116.179.32.16 (https://ipdebrief.com/116.179.32.16)
- 116.179.32.17 (https://ipdebrief.com/116.179.32.17)
- 116.179.32.18 (https://ipdebrief.com/116.179.32.18)
- 116.179.32.19 (https://ipdebrief.com/116.179.32.19)
- 116.179.32.20 (https://ipdebrief.com/116.179.32.20)
- 116.179.32.21 (https://ipdebrief.com/116.179.32.21)
- 116.179.32.22 (https://ipdebrief.com/116.179.32.22)
- 116.179.32.23 (https://ipdebrief.com/116.179.32.23)

---

Source: IPDebrief, "116.179.32.215 IP intelligence", https://ipdebrief.com/116.179.32.215, updated 2026-10-07. Assessments are probabilistic.