IPDebrief

180.76.170.245

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: 180.76.170.245

Date: 2026-06-02

---

**Overview**

---

**Key Findings**

1. Ownership & Network Context:

- Belongs to Baidu Noc (Beijing Baidu Netcom Science and Technology Co., Ltd.), registered under APNIC.

- Subnet 180.76.170.245/24 has 2 active IPs, with 1 sibling flagged at moderate risk (65). Subnet abuse density is low (0.5).

2. Observation History:

- Last 30 days: 15 observations, primarily geolocation and network metadata.

- No spikes in threat signals; consistent benign activity.

3. Relationships:

- Linked to Baidu across multiple signals (network, ownership).

- No connections to Tor, CDN, or cloud infrastructure.

4. Behavioral & Technical Data:

- No open ports, TLS certificates, or HTTP services detected.

- DNSSEC valid, no CAA records, and 3 DNSBL listings (low impact).

- BGP prefix 180.76.128.0/18 shows stable routing with no recent changes.

---

**Threat Assessment**

---

**Recommended Actions**

1. Monitor Subnet: Track activity on 180.76.170.0/24 for unusual traffic patterns.

2. Validate Ownership: Confirm Baidu’s control over the IP to rule out spoofing or misattribution.

3. Check Neighbor IPs: Investigate the high-risk neighbor (180.76.170.111) for potential关联 threats.

4. Maintain Baseline: Use IPDebrief’s history tool to detect future anomalies.

---

Note: This IP is part of a legitimate organization’s infrastructure but should be monitored due to public exposure and subnet risk density.

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

🌍 Geolocation

CountryπŸ‡¨πŸ‡³ China
Regionβ€”
Cityβ€”
Timezoneβ€”
Latitude34.77
Longitude113.72

🏒 Ownership & Registration

OrganizationBaidu Noc
ASNAS38365
Network NameBaidu
CIDR Block180.76.0.0/16
RIRAPNIC
CountryCN
Abuse Contactβ€”

🌐 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

InfrastructureUnknown
Service PurposeFirewalled / No Services
Network TierUnknown β€” Insufficient routing data to classify
No specific classification

πŸ”Œ 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
29%
24
routing
25%
11
services
15%
22
ownership
19%
22
reputation
24%
13
geolocation
21%
22
Overall22%1014
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-07 23:03:58 UTC
Last Seen2026-06-22 23:11:53 UTC
Profile Built2026-06-22 23:25:31 UTC
Data FreshnessLive
Signal Types16
Total Observations20
πŸ” 16 signal types Β· 20 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.