IPDebrief

206.189.189.87

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

Classification: Cloud Infrastructure Host – Low Risk

Date: 2026-06-25

Analyst: IPDebrief Intelligence

---

EXECUTIVE SUMMARY

IP 206.189.189.87 is a DigitalOcean cloud compute instance located in North Bergen, NJ, US. The IP presents as a single-service host with minimal threat indicators. Overall risk score of 25 classifies this as low-risk, suitable for standard monitoring without immediate blocking action.

---

OWNERSHIP & INFRASTRUCTURE

---

NETWORK SERVICES

Open Ports:

Analysis: Single SSH banner detected. No web services (HTTP/HTTPS) or database ports exposed. Configuration is consistent with a bastion host or administrative access endpoint.

---

THREAT INDICATORS

---

NEIGHBORHOOD ANALYSIS

The /24 subnet shows no correlated abuse activity, suggesting this is an isolated cloud instance rather than part of a compromised infrastructure.

---

OBSERVATION HISTORY

Total Observations: 21 signals

Recent Activity (2026-06-25):

Temporal Analysis:

---

RELATIONSHIP GRAPH

Connections: 37 relationships

---

RECOMMENDED ACTIONS

Current Risk Level: LOW

Recommended Firewall Policy: ALLOW with monitoring

Actionable Rules:

```bash

# iptables/nftables (monitor SSH traffic only)

iptables -A INPUT -p tcp --dport 22 -s 206.189.189.0/24 -j LOG --log-prefix "DO-SH-"

# If SSH access is not authorized, block

iptables -A INPUT -p tcp --dport 22 -s 206.189.189.87 -j DROP

```

Monitoring Recommendations:

1. Monitor DNSBL status for the 1 listing (potential false positive)

2. Track SSH connection attempts for unauthorized access

3. No immediate blocking required based on current risk profile

---

ANALYST NOTES

This IP represents standard DigitalOcean cloud infrastructure with no active threat indicators. The single SSH banner suggests administrative access capability. The low abuse density in the /24 subnet and absence of threat siblings indicate this is likely legitimate cloud hosting rather than malicious infrastructure. Continue standard monitoring but no escalation required at this time.

Status: Monitor – No Action Required

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionNJ
CityNorth Bergen
Timezoneβ€”
Latitude40.80
Longitude-74.02

🏒 Ownership & Registration

OrganizationDigitalOcean, LLC
ASNAS14061
Network Nameβ€”
CIDR Blockβ€”
RIRARIN
Countryβ€”
Abuse ContactAvailable via RDAP

🌐 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

InfrastructureInfrastructure / Datacenter
Service PurposeSingle-Service Host
Network TierHosting β€” Infrastructure provider without advanced routing
CloudHosting

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
22sshtcp
Closed Ports25, 80, 443, 3389, 8080, 8443 (1 open / 7 scanned)
Serverβ€”
HTTP Titleβ€”
SSH VersionSSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.16

πŸ” 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
22%
24
routing
8%
11
services
20%
22
ownership
20%
23
reputation
24%
13
geolocation
23%
22
Overall19%1015
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-08 23:18:26 UTC
Last Seen2026-06-27 14:31:29 UTC
Profile Built2026-06-28 08:38:00 UTC
Data FreshnessLive
Signal Types21
Total Observations26
πŸ” 21 signal types Β· 26 observations collected
This report is generated from 21+ 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.