IPDebrief

173.239.214.151

IP Intelligence Dossier
Your IP: 216.73.216.5
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

# IP Intelligence Briefing: 173.239.214.151/32

Classification: Low Risk (Score: 20/100)

Date: Current Analysis

Target: 173.239.214.151

## Executive Summary

The IP address 173.239.214.151 belongs to LOGICWEB (Private Customer) under ASN 62240, registered in Edison, New Jersey. The IP presents a low-risk profile with no active threat indicators. The address is firewalled with no open services detected, suggesting either legitimate infrastructure or a decommissioned resource. No actionable threats were identified during this assessment.

## Network Profile

AttributeValue
**IP Address**173.239.214.151/32
**ASN**62240 (LOGICWEB)
**Organization**Private Customer
**Country**United States (US)
**Region**New Jersey (Edison)
**CIDR Block**173.239.214.0/24
**Risk Score**20 (Low)
**Abuse Confidence**None reported
**Classification**Firewalled / No Services

## Threat Assessment

Active Threat Indicators: None

Service Exposure: None

## Neighborhood Analysis (173.239.214.0/24)

MetricValue
**Subnet Classification**Mostly Clean
**Abuse Density**10.14%
**Total Siblings**148
**Active Siblings**89
**Threat Siblings**15
**Risk Distribution**High: 0, Medium: 15, Low: 85

The /24 subnet shows minimal abuse activity. Of 100 sampled neighbors, 85% scored low risk and 15% scored medium risk. No high-risk neighbors were detected. The target IP shares the same network with 15 threat-identified siblings, though these are not directly correlated.

## Observations & History

Signal Count: 13 observations recorded

Persistence: No persistent malicious activity detected

Ownership Stability: No ownership changes observed

Recent signal observations indicate:

## Geolocation Validation

Status: ⚠️ Anomaly Detected

*Note: The geolocation data indicates a plausible location mismatch, suggesting either proxying, misconfiguration, or inaccurate RIR registration.*

## Relationship Graph

All identified relationships (5 total) point to LOGICWEB network assets. No external entity relationships (hostnames, organizations, certificates) were discovered, indicating isolated network operation.

## Recommended Actions

ActionPriority
**No blocking recommended**Low
**Monitor for service activation**Medium
**Verify geolocation accuracy**Low
**Standard allow-listing**Low

Firewall Rules: None required at this time.

## Intelligence Narrative

IP 173.239.214.151 is classified as low-risk infrastructure operated by LOGICWEB. The absence of open services and threat indicators suggests the IP is either properly secured legitimate infrastructure or has been taken offline. The geolocation validation anomaly warrants periodic re-assessment but does not indicate active malicious activity. The subnet environment (173.239.214.0/24) demonstrates minimal abuse density with 15 threat siblings out of 148 total addresses, placing the target in a relatively clean neighborhood.

Confidence Level: High (Low-risk classification supported by multiple data sources)

Action Required: None at this time. Continue standard monitoring.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionNew Jersey
CityEdison
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
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
25%
11
routing
25%
11
services
25%
11
ownership
25%
11
reputation
0%
00
geolocation
25%
11
Overall20%55
Coverage: 5/6 dimensions Β· Data sufficiency: partial
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-07-27 15:46:21 UTC
Last Seen2026-07-30 12:50:42 UTC
Profile Built2026-07-30 13:04:33 UTC
Data FreshnessLive
Signal Types16
Total Observations16
πŸ” 16 signal types Β· 16 observations collected
This report is generated from 16+ 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.