IPDebrief

173.234.225.6

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

Date: 2026-06-19

Classification: Moderate Risk - High Abuse Neighborhood Context

## Executive Summary

IP 173.234.225.6 operates within a high-abuse density colocation hosting environment in Dallas, TX. While the IP itself shows moderate risk (score: 50), the /24 subnet exhibits concerning abuse patterns with 84.8% of active siblings classified as threats. SOC teams should monitor traffic from this IP for potential lateral movement or compromised host activity within the hosting infrastructure.

## Ownership & Geolocation

## Threat Assessment

## Neighborhood Analysis (173.234.225.0/24)

The subnet demonstrates elevated abuse characteristics:

## Network Behavior

## Observation History

39 observations recorded over the analysis period. Recent signals indicate:

## Recommended Security Actions

Based on risk profile and neighborhood context, the following firewall rules are recommended:

iptables:

```bash

iptables -A INPUT -s 173.234.225.6 -j DROP

```

nftables:

```bash

nft add rule inet filter input ip saddr 173.234.225.6 drop

```

nginx:

```nginx

deny 173.234.225.6;

```

pfSense:

```

173.234.225.6/32

```

Cloudflare WAF:

```json

{

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

"action": "block",

"filter": {

"expression": "ip.src eq 173.234.225.6"

}

}

```

AWS WAF:

```json

{

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

"Description": "IPDebrief risk 50"

}

```

## Intelligence Notes

The colocation hosting nature of this IP explains the moderate risk scoreβ€”many IPs in this environment may be legitimately hosted services. However, the high abuse density in the /24 subnet suggests this provider hosts significant malicious traffic. SOC analysts should:

1. Monitor for suspicious traffic patterns from this subnet

2. Consider blocking at network perimeter if false positives are manageable

3. Investigate any connection attempts during off-hours

4. Correlate with other indicators of compromise if alerts trigger

Disclaimer: These recommendations are probabilistic and should be combined with other signals before taking action.

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 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
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
29%
24
routing
17%
11
services
15%
22
ownership
24%
23
reputation
31%
13
geolocation
30%
23
Overall24%1016
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:01 UTC
Last Seen2026-06-27 09:50:52 UTC
Profile Built2026-06-28 03:57:08 UTC
Data FreshnessLive
Signal Types19
Total Observations42
πŸ” 19 signal types Β· 42 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.