IP Intelligence Briefing: 173.239.214.8
*Generated via IPDebrief tools: Profile, History, Relationships, Neighbors*
---
**1. Risk Profile**
- Overall Risk: Moderate (Risk Score: 40/100)
- Ownership: Private customer (ASN 62240, ARIN-registered) under network name *LOGICWEB*.
- Geolocation: Ashburn, VA, US (consistent over 45 days).
- Network Role: Firewalled / No Services (no open ports, no TLS/HTTP services detected).
- Threat Indicators: No malicious activity, spam, or known attacker associations.
---
**2. Historical Observations (Last 45 Days)**
- Risk Stability: Risk score has remained constant at 40.
- Geolocation Consistency: No deviations in location data.
- Network Stability: No changes in ownership or network role.
- Threat Persistence: No persistent malicious activity or campaign ties.
---
**3. Network Relationships**
- Subnet: 173.239.214.0/24 (part of *LOGICWEB* network).
- Neighbors: 44 IPs in the subnet, with abuse density 0%.
- Risk Distribution: 14 medium-risk IPs (25β40), 30 low-risk IPs (<25).
- Notable Neighbors:
- 173.239.214.6, 173.239.214.10, 173.239.214.12, 173.239.214.20, and 173.239.214.24 (all medium risk).
- Subnet Classification: No evidence of abuse or malicious activity.
---
**4. Security Actions**
- Recommended Mitigations:
- Monitor the *LOGICWEB* subnet for anomalies (low-risk but ensure no unexpected behavior).
- Maintain current firewall rules; no immediate blocking required.
- Verify DNSSEC validity and ensure no misconfigurations in the subnet.
---
**5. Summary**
The IP 173.239.214.8 is part of a private, moderately risky network with no active threats. While the subnet contains some medium-risk neighbors, the IP itself shows no malicious indicators. SOC teams should focus on maintaining baseline security posture and monitoring for unexpected changes in the subnet.
Next Steps:
- Validate DNSSEC and network segmentation policies.
- Continuously monitor for new threats in the *LOGICWEB* subnet.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | Private Customer |
| ASN | AS62240 |
| Network Name | LOGICWEB |
| CIDR Block | 173.239.214.0/24 |
| RIR | ARIN |
| Country | United States |
| Abuse Contact | β |
π DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No β PTR hostname does not resolve back to this IP (weak signal) |
π DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
βοΈ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Firewalled / No Services |
| Network Tier | Unknown β Insufficient routing data to classify |
π Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Server | β |
| HTTP Title | β |
π TLS Certificate
| SANs | None |
| Valid From | β |
| Valid Until | β |
π― Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 18% | 2 | 2 |
| routing | 13% | 1 | 1 |
| services | 8% | 1 | 1 |
| ownership | 19% | 2 | 2 |
| reputation | 17% | 1 | 2 |
| geolocation | 37% | 2 | 3 |
| Overall | 19% | 9 | 11 |
| Data Coherence | Mostly Consistent (80%) β 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-05-07 23:03:55 UTC |
| Last Seen | 2026-06-22 21:29:55 UTC |
| Profile Built | 2026-06-22 21:42:02 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 23 |
Full dossier details are available via our API.