IPDebrief

173.234.227.58

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.

Threat Intelligence Briefing: IP 173.234.227.58/32

Observation History and Network Profile:

Neighborhood Data:

Relationships and Threat Indicators:

Actionable Recommendations for SOC Analysts:

1. Monitor Traffic: Implement continuous monitoring of traffic originating from and destined to this IP address. Look for patterns indicative of command and control (C2) activity or data exfiltration.

2. Block or Filter Traffic: Consider blocking or filtering traffic to/from this IP address if it is not essential for business operations. Prioritize blocking access to known malicious domains associated with this IP.

3. Alert Configuration: Configure alerts for any unusual activity patterns, such as spikes in traffic or connections to previously flagged domains, to facilitate rapid response.

4. Collaborate with Threat Intelligence Sources: Engage with external threat intelligence providers for updates on any new associations or threat developments related to this IP address.

5. Review Web Hosting Environment: If this IP is part of your organization's web hosting environment, conduct a thorough security review to ensure that no malicious content is hosted and that all services are properly secured.

This intelligence briefing provides a comprehensive overview of the observed activities and potential risks associated with IP 173.234.227.58/32, enabling SOC teams to make informed decisions regarding their defensive strategies.

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
26%
24
routing
43%
17
services
12%
22
ownership
24%
23
reputation
31%
13
geolocation
26%
23
Overall27%1022
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:04 UTC
Last Seen2026-06-27 11:25:35 UTC
Profile Built2026-06-28 05:31:11 UTC
Data FreshnessLive
Signal Types19
Total Observations51
πŸ” 19 signal types Β· 51 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.