IPDebrief

173.234.226.210

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

## Executive Summary

IP 173.234.226.210 is classified as a Moderate Risk address (risk score: 50) hosted on a colocation hosting platform. The IP belongs to Leaseweb USA, Inc. (ASN: 394380) in Dallas, TX. While the IP itself shows no active threat indicators, it operates within a high-abuse-density subnet (173.234.226.0/24) with an abuse density of 0.7344 and 188 threat-identified siblings. The address is currently firewalled with no open services detected.

---

## Profile Details

Ownership & Registration

Geolocation

Control Plane

---

## Threat Indicators

IndicatorStatus
Risk Score50 (Moderate)
Blacklist Count2
DNSBL Listed2 of 8 lists
Is Known AttackerNo
Is Tor ExitNo
Is ProxyNo
Is Spam SourceNo
Reputation SourcesNone identified
Threat FeedsNone

Key Observations

---

## Network Neighborhood Analysis

Subnet: 173.234.226.0/24

MetricValue
Abuse Density0.7344
ClassificationHigh Abuse
Inherited Risk29
Total Siblings256
Active Siblings236
Threat Siblings188

Risk Distribution: 100 medium-risk IPs, 0 high-risk IPs

The subnet exhibits elevated abuse activity, with 188 out of 256 sibling IPs flagged as threats. This suggests the hosting infrastructure is commonly exploited for malicious purposes.

---

## Historical Analysis

Total Observations: 54

Recent signal activity indicates:

No persistent malicious activity observed, but historical DNSBL presence warrants attention.

---

## Relationship Graph

Total Relationships: 197

---

## Services & DNS

CategoryStatus
Open PortsNone detected
Hosted Domains0
Email Auth (SPF/DMARC)Not configured
TLS CertificateNone
HTTP ServicesNone

Note: Services appear firewalled or inactive.

---

## Recommended Actions

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

Firewall Rules

iptables:

```

iptables -A INPUT -s 173.234.226.210 -j DROP

```

nftables:

```

nft add rule inet filter input ip saddr 173.234.226.210 drop

```

nginx:

```

deny 173.234.226.210;

```

Cloudflare WAF:

```json

{

"description": "Block 173.234.226.210 β€” IPDebrief risk score 50",

"action": "block",

"filter": {

"expression": "ip.src eq 173.234.226.210"

}

}

```

AWS WAF:

```json

{

"Addresses": ["173.234.226.210/32"],

"Description": "IPDebrief risk 50"

}

```

---

## Intelligence Assessment

This IP represents a low-to-moderate threat suitable for defensive blocking. Key factors supporting this assessment:

1. Hosting Infrastructure: IP operates on a colocation platform commonly used for both legitimate and malicious purposes

2. Abuse Environment: High-abuse subnet with significant threat sibling activity

3. Clean Current Profile: No active attacker indicators or known campaigns

4. Historical DNSBL Presence: Prior reputation issues suggest previous abuse or misconfiguration

Recommended Action: Implement block rules while monitoring for legitimate service requirements. Consider broader subnet-level filtering (173.234.226.0/24) if the organization experiences related attack patterns from the subnet.

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.226.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 Score40% (Fair)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAAPresent

☁️ 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
28%
24
routing
56%
210
services
17%
23
ownership
22%
34
reputation
28%
13
geolocation
26%
23
Overall30%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:03 UTC
Last Seen2026-06-27 11:08:08 UTC
Profile Built2026-06-28 05:14:07 UTC
Data FreshnessLive
Signal Types26
Total Observations61
πŸ” 26 signal types Β· 61 observations collected
This report is generated from 26+ 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.