165.227.200.17📋 Copy

IP Intelligence Briefing for 165.227.200.17/32

*Generated via IPDebrief Tools*

---

**1. Core Profile**

• Risk Assessment:

- Risk Score: 25 (Low Risk)

- Provider Score: 0 (No provider risk)

- Authority Score: 0 (No authoritative risk)

- Stability: Stable (no recent route changes)

- Threat Indicators: None detected (no malware, spam, or known attacker associations).

• Ownership:

- AS: AS14061 (DigitalOcean, LLC)

- Geolocation: North Bergen, NJ, US (ARIN-registered).

- Network Role: Cloud infrastructure (DigitalOcean-hosted virtual machines).

• Network Classification:

- Type: Firewalled / No Services (no open ports or TLS services detected).

- Subnet: 165.227.200.17/24 (abuse density: 1/100, classified as "mostly_clean").

---

**2. Observation History**

• Recent Activity:

- Observed on June 5–14, 2026, with consistent geolocation and network stability.

- No spikes in threat signals or DNS anomalies.

- DNS Resolution: Resolves to `prod-boron-nyc1-64.do.binaryedge.ninja` (DigitalOcean domain).

• Behavioral Trends:

- No enumeration attempts, honeypot hits, or WAF violations detected.

- BGP Stability: Route stable for 30 days; no ASN changes.

---

**3. Relationships & Network Context**

• Connected Entities:

- Linked to DIGITALOCEAN-165-227-0-0 (same /20 subnet).

- Neighbors:

- 165.227.200.104 (risk score: 25, low risk).

- Subnet abuse density: 1/100 (mostly clean).

• DNS & Email:

- SPF Record: Valid (no DMARC or DKIM).

- Email Reputation: No malicious sender scores.

---

**4. Threat & Security Context**

• Threat Indicators:

- No DNSBL listings, malware campaigns, or malicious certificates.

- TOR/VPN/Proxy: Not detected.

• Security Actions:

- Recommended: Monitor for unexpected outbound traffic or service enumeration.

- Firewall Rules: No immediate blocking required; align with cloud provider’s security policies.

---

**5. Summary**

The IP 165.227.200.17 is part of DigitalOcean’s cloud infrastructure, with no malicious activity detected. It is geolocated in New Jersey, US, and resides in a subnet with low abuse density. While it is a cloud-hosted IP, there is no evidence of misuse. SOC teams should focus on monitoring for deviations from expected cloud behavior, particularly if this IP is associated with unexpected services or traffic patterns. No immediate mitigation is required.

*Tools: ipdebrief_profile, ipdebrief_history, ipdebrief_relationships, ipdebrief_neighbors.*

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