IPDebrief

173.234.225.154

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.

# IPDEBRIEF INTELLIGENCE BRIEFING

Target IP: 173.234.225.154/32

Date: 2026-06-19

Classification: Moderate Risk (Score: 50)

---

## EXECUTIVE SUMMARY

IP 173.234.225.154 is a moderate-risk address (Risk Score: 50) belonging to Leaseweb USA, Inc. (ASN 394380) in Dallas, TX. The IP is classified as a colocation hosting facility under the Choopa/GameServers provider classification. While no active threat indicators are present, the subnet exhibits high abuse density (0.8438) with 216 of 256 sibling IPs flagged as threats. No open services are detected; the IP appears to be firewalled with no active services.

---

## OWNERSHIP & INFRASTRUCTURE

AttributeValue
ASN394380 (LEASEWEB-USA-DAL)
OrganizationLeaseweb USA, Inc.
LocationDallas, TX, US
Infrastructure TypeColocation Hosting
ClassificationChoopa/GameServers
Registration2010-02-12 (ARIN)
CIDR Block173.234.225.0/24

Network Classification: Provider infrastructure with hosting capabilities. No cloud, CDN, VPN, proxy, or Tor characteristics detected.

---

## THREAT ASSESSMENT

Current Risk Profile:

Threat Indicators: None currently active. No known campaigns or correlated IPs detected.

---

## NEIGHBORHOOD ANALYSIS

Subnet: 173.234.225.0/24

Abuse Density: 0.8438 (High)

Total Siblings: 256

Active Siblings: 184

Threat Siblings: 216

Inherited Risk Score: 33

Risk Distribution:

The subnet demonstrates consistent medium-risk classification across all analyzed neighbors, indicating this is an abuse-prone hosting environment. The high abuse density suggests elevated risk when accepting traffic from this /24.

---

## SERVICE ANALYSIS

Services Detected: None

Open Ports: None

TLS Certificate: None

HTTP Title: None

Service Purpose: Firewalled / No Services

The target IP is not actively serving applications or hosting services. This is typical for infrastructure IPs that may be used for management, monitoring, or administrative functions.

---

## OBSERVATION HISTORY

Total Observations: 43 signals

Recent Activity:

Temporal Analysis: No ownership changes detected. Threat observation count remains at zero. The IP maintains stable routing with zero route changes in the past 30 days.

---

## RELATIONSHIP GRAPH

Total Relationships: 115

Primary Relationship Type: Same Network (LU-79)

Multiple network relationships exist within the same /24 subnet. No external organizational or certificate relationships were identified in the relationship graph.

---

## RECOMMENDED ACTIONS

Based on the moderate-risk profile and high-abuse subnet context, the following defensive measures are recommended:

Recommended Action: Block/DROP

Firewall Rules:

---

## ANALYST NOTES

1. Subnet Context: The 173.234.225.0/24 subnet shows elevated abuse density. Consider implementing broader subnet-level filtering policies for this /24 if threat volume warrants it.

2. Infrastructure Classification: As a colocation hosting facility, this IP may be legitimately used by hosting customers. However, the high abuse density suggests increased scrutiny is warranted.

3. Service State: No active services detected. If inbound connections are expected, verify the intended use case. If none, the IP may be dormant or used for passive functions.

4. Risk Evolution: Historical data shows consistent risk levels with no escalation pattern. The IP is not showing signs of becoming more malicious over time.

5. Mitigation Priority: Given the subnet's abuse density, implement the recommended blocking rules

---

SOC Analyst Considerations:

1. Subnet Context: The 173.234.225.0/24 subnet shows elevated abuse density. Consider implementing broader subnet-level filtering policies for this /24 if threat volume warrants it.

2. Infrastructure Classification: As a colocation hosting facility, this IP may be legitimately used by hosting customers. However, the high abuse density suggests increased scrutiny is warranted.

3. Service State: No active services detected. If inbound connections are expected, verify the intended use case. If none, the IP may be dormant or used for passive functions.

4. Risk Evolution: Historical data shows consistent risk levels with no escalation pattern. The IP is not showing signs of becoming more malicious over time.

5. Mitigation Priority: Given the subnet's abuse density, implement the recommended blocking rules with monitoring for false positives.

6. Alerting Threshold: Set up monitoring for any new threat indicators emerging from this IP. Current absence of known campaigns or attack signatures is notable but does not eliminate risk entirely.

7. Correlation Requirements: No correlated IPs or CERT matches identified. If this IP begins generating suspicious traffic patterns, investigate potential lateral movement or command-and-control activity.

8. Geographic Validation: ICMP validation failed due to ICMP blocking. Geographic coordinates show 7,997.4 km distance from validation point. Consider additional validation if location accuracy is required for incident response.

END OF INTELLIGENCE BRIEFING

Report Generated: 2026-06-19

Source: IPDebrief Automated Analysis

Classification: Threat Intelligence - Internal Use

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionTX
CityDallas
Timezoneβ€”
Latitude32.78
Longitude-96.80

🏒 Ownership & Registration

OrganizationLeaseweb USA, Inc.
ASNAS394380
Network Nameβ€”
CIDR Block173.234.225.0/24
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 TierTier 3 β€” Basic operator with some routing infrastructure
Hosting

πŸ”Œ 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
47%
25
routing
58%
210
services
12%
22
ownership
29%
34
reputation
33%
13
geolocation
30%
23
Overall35%1227
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:05:02 UTC
Last Seen2026-06-27 10:15:44 UTC
Profile Built2026-06-28 04:21:22 UTC
Data FreshnessLive
Signal Types25
Total Observations59
πŸ” 25 signal types Β· 59 observations collected
This report is generated from 25+ 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.