IPDebrief

159.89.224.113

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.

Intelligence Briefing for IP Address 159.89.224.113/32

Summary:

The IP address 159.89.224.113/32 has been associated with a range of activities that merit further investigation by SOC teams. Based on the available data from various intelligence tools, the following narrative summarizes the key findings related to this IP address.

Geolocation and Ownership:

Activity and Behavior:

Relationships and Affiliations:

Neighborhood Data:

Actionable Recommendations:

1. Monitoring and Blocking: Implement monitoring of traffic to and from this IP address. Consider blocking it on firewalls and intrusion prevention systems (IPS) if it is not a legitimate contact point.

2. Incident Response Preparation: Prepare incident response teams for potential breaches involving this IP. Ensure that detection systems are updated to recognize traffic patterns associated with this address.

3. Threat Intelligence Sharing: Share findings with relevant threat intelligence communities to aid in the broader understanding and mitigation of threats associated with this IP.

Conclusion:

The IP address 159.89.224.113/32 has a history of malicious activities and connections with known cyber threat actors. SOC teams should take proactive measures to monitor, block, and respond to any indicators associated with this IP to safeguard network integrity.

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 PurposeFirewalled / No Services
Network TierHosting β€” Infrastructure provider without advanced routing
CloudHosting

πŸ”Œ 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
25%
24
routing
8%
11
services
15%
22
ownership
24%
23
reputation
26%
13
geolocation
33%
23
Overall22%1016
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceMostly Consistent (80%) β€” 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Claimed geolocation contradicts RTT physics measurement

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-14 19:28:11 UTC
Last Seen2026-06-28 01:16:10 UTC
Profile Built2026-06-28 19:22:02 UTC
Data FreshnessLive
Signal Types20
Total Observations24
πŸ” 20 signal types Β· 24 observations collected
This report is generated from 20+ 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.