IPDebrief

173.239.214.27

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.

INTELLECT BRIEFING: IP 173.239.214.27/32

Classification: Low Risk | Threat Level: Minimal

---

1. IP Profile & Ownership

IP address 173.239.214.27 is registered to LOGICWEB (ASN 62240), a private customer organization within the 173.239.214.0/24 CIDR block. Geographic location is registered to Ashburn, Virginia, US. The IP maintains a risk score of 25, classified as Low Risk. No active threat indicators, blacklist listings, or known campaign associations were detected.

2. Network Classification

The IP is not categorized as cloud, CDN, VPN, proxy, Tor, hosting, mobile, or residential infrastructure. Service profile indicates "Firewalled / No Services" with no open ports, TLS certificates, or email authentication records (SPF/DMARC absent). The control plane shows DNSSEC validation enabled, minimal operator score (0.1304), and route stability flagged as false.

3. Historical Observations

Analysis of 16 historical observations reveals:

4. Neighborhood Analysis (173.239.214.0/24)

The /24 subnet contains 45 sibling IPs with the following distribution:

Notable neighbors include 173.239.214.6, 173.239.214.8, 173.239.214.12, and 173.239.214.19 (all risk score 40). Inherited risk score from neighborhood: 19.

5. Relationships

Network relationships indicate all 16 detected associations point to LOGICWEB network infrastructure. No external organizational or hostname relationships beyond the network designation were identified.

---

SOC ACTIONS & RECOMMENDATIONS

1. Block Status: No blocking required. Low-risk profile with no active threat indicators.

2. Firewall Rules: No specific firewall rules generated due to minimal risk profile.

3. Monitoring: Monitor for changes in service profile (open ports, TLS certificates) or blacklist status changes.

4. Geolocation: Verify actual location via traffic analysis; RTT violations suggest potential proxy usage or misconfiguration.

5. Subnet Context: While the subnet shows mixed abuse density (0.4889), this specific IP shows no malicious activity. Contextual analysis recommended for any suspicious traffic originating from sibling IPs.

Priority: LOW β€” No immediate action required.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionVA
CityAshburn
Timezoneβ€”
Latitude40.52
Longitude-74.42

🏒 Ownership & Registration

OrganizationPrivate Customer
ASNAS62240
Network NameLOGICWEB
CIDR Block173.239.214.0/24
RIRARIN
CountryUnited States
Abuse Contactβ€”

🌐 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

InfrastructureUnknown
Service PurposeFirewalled / No Services
Network TierUnknown β€” Insufficient routing data to classify
No specific classification

πŸ”Œ 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
24%
22
routing
13%
11
services
8%
11
ownership
19%
22
reputation
17%
12
geolocation
37%
23
Overall20%911
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceMostly Consistent (80%) β€” 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Claimed geolocation contradicts RTT physics measurement

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-07 23:03:55 UTC
Last Seen2026-06-22 21:31:03 UTC
Profile Built2026-06-22 21:42:02 UTC
Data FreshnessLive
Signal Types21
Total Observations23
πŸ” 21 signal types Β· 23 observations collected
This report is generated from 21+ 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.