IPDebrief

206.189.134.35

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.134.35/32

Classification: LOW RISK | Provider: DigitalOcean, LLC | Jurisdiction: India (Bengaluru)

---

## EXECUTIVE SUMMARY

Target IP 206.189.134.35/32 presents a low-risk threat profile with a risk score of 25. The address is associated with DigitalOcean cloud infrastructure and operates in Bengaluru, India. While the IP is currently classified as low-risk, it shows DNSBL listing activity and exhibits some historical threat correlation signals. No active malicious campaigns or known attacker indicators were observed.

---

## NETWORK OWNERSHIP & INFRASTRUCTURE

AttributeValue
**Organization**DigitalOcean, LLC (ASN 14061)
**Geolocation**Bengaluru, Karnataka, India (IN)
**Infrastructure Type**CloudCompute
**Network Role**Single-Service Host
**ISP/Provider**DigitalOcean

The IP is provisioned on DigitalOcean's cloud platform within AS14061. The network prefix originates from the 206.189.128.0/20 block. Route stability analysis indicates the prefix has experienced route changes within the past 30 days.

---

## THREAT ASSESSMENT

Current Risk Profile:

Services Exposed:

No TLS certificates, HTTP services, or email authentication records (SPF/DMARC) were observed for this address.

---

## OBSERVATION HISTORY ANALYSIS

The IP has been observed across 21 signal events spanning the monitoring period. Key historical indicators include:

Historical data indicates transient threat correlation with 14 pulse matches in earlier observations, though current status shows de-escalation of threat signals.

---

## SUBNET NEIGHBORHOOD ANALYSIS

Subnet: 206.189.134.0/24

Notable Neighbor:

The /24 subnet demonstrates minimal abuse concentration with no high-risk or medium-risk neighbors identified.

---

## RELATIONSHIP GRAPH

The IP maintains 14 relationship links, predominantly "Same Network" associations to the DIGITALOCEAN-206-189-0-0 network prefix. No interconnectivity with external organizations, hostnames, or certificate authorities was identified.

---

## RECOMMENDED ACTIONS

Firewall/Security Configuration:

```bash

# Minimal blocking recommended - low risk profile

# Consider monitoring if threat correlation increases

# Allow SSH with rate limiting

iptables -A INPUT -p tcp --dport 22 -m recent --name ssh_limit --update --seconds 60 --hitcount 5 -j DROP

iptables -A INPUT -p tcp --dport 22 -j ACCEPT

# Log and monitor DNSBL activity

iptables -A INPUT -p tcp --dport 53 -j LOG --log-prefix "DNSBL_CHECK: "

```

SOC Monitoring Priorities:

1. Monitor for escalation in DNSBL listings

2. Track SSH connection patterns for brute force attempts

3. Correlate with DigitalOcean abuse feeds for network-wide campaigns

4. Review if route instability correlates with security incidents

---

## CONCLUSION

IP 206.189.134.35/32 is a legitimate cloud infrastructure endpoint on DigitalOcean with low-risk characteristics. While DNSBL listing activity warrants monitoring, the overall threat profile does not indicate active malicious use. SOC analysts should maintain routine observation rather than immediate blocking, with escalation triggers for increased threat correlation or DNSBL proliferation.

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

๐ŸŒ Geolocation

Country๐Ÿ‡ฎ๐Ÿ‡ณ India
RegionKA
CityBengaluru
Timezoneโ€”
Latitude12.98
Longitude77.59

๐Ÿข 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
25%
24
routing
8%
11
services
15%
22
ownership
20%
23
reputation
24%
13
geolocation
33%
23
Overall21%1016
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-05-19 03:35:49 UTC
Last Seen2026-06-28 08:24:13 UTC
Profile Built2026-06-29 02:28:22 UTC
Data FreshnessLive
Signal Types19
Total Observations23
๐Ÿ” 19 signal types ยท 23 observations collected
This report is generated from 19+ 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.