IPDebrief

161.115.234.250

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

*Generated for SOC Analysts*

---

**1. Core Profile**

---

**2. Neighborhood Analysis**

- 16 of 29 sibling IPs flagged as threats.

- Active siblings: 4 (2 high-risk, 2 medium-risk).

- Action Required: Monitor subnet for lateral movement or compromised hosts.

---

**3. Temporal Observations**

- Geo validation failed (ICMP blocked).

- No persistent threats detected over 30 days.

- Subnet abuse density has remained stable at 55%.

---

**4. Relationships & Context**

- Provider: Flux Telecom, LLC (AS6079).

- No DNS, certificates, or hostnames linked.

- BGP prefix: 161.115.232.0/21.

- DNSSEC valid, CAA records present.

---

**5. Recommendations**

1. Subnet Monitoring:

- Prioritize monitoring 161.115.234.0/24 due to high abuse density.

- Investigate 16 high-risk neighbors for potential compromise.

2. Geolocation Verification:

- Validate IP's physical location via alternative methods (e.g., traceroute, DNS probes).

3. Network Segmentation:

- Consider isolating residential subnets to limit lateral spread.

4. Provider Engagement:

- Collaborate with Flux Telecom to address subnet abuse.

---

Conclusion: While the IP itself is residential and not directly malicious, its subnet exhibits significant abuse activity. SOC teams should focus on subnet-level monitoring and collaboration with the ISP to mitigate potential risks.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionCA
CityLos Angeles
TimezoneAmerica/Los_Angeles
Latitude33.96
Longitude-118.39

🏒 Ownership & Registration

OrganizationFlux Telecom, LLC
ASNAS6079
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 Score40% (Fair)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAAPresent

☁️ Network Classification

InfrastructureResidential
Service PurposeResidential Endpoint
Network TierEnd-User β€” Residential ISP endpoint
Residential

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
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
27%
22
routing
19%
12
services
19%
12
ownership
33%
23
reputation
13%
12
geolocation
22%
11
Overall22%812
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-14 19:28:11 UTC
Last Seen2026-06-07 07:48:20 UTC
Profile Built2026-05-30 23:03:55 UTC
Data FreshnessLive
Signal Types18
Total Observations20
πŸ” 18 signal types Β· 20 observations collected
This report is generated from 18+ 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.