IPDebrief

173.239.214.96

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

*Generated from IPDebrief analysis*

---

**Core Profile**

---

**Observation History**

- Stable ownership (no changes detected).

- No DNS or BGP anomalies.

- No scans, enumerations, or WAF violations.

---

**Network Relationships**

- Subnet: `173.239.214.0/24` (registered to "LOGICWEB")

- No direct associations with known campaigns, domains, or certificates.

---

**Subnet Neighborhood**

- 15 IPs with medium risk (score 40)

- 29 IPs with low risk (score 25)

- No high-risk IPs detected

---

**Actionable Insights**

1. No Immediate Threat: The IP itself is low risk and appears to be a legitimate, firewalled server.

2. Monitor Subnet Neighbors: While the subnet has no abuse, 15 IPs show medium risk. Investigate these for potential lateral movement or shared infrastructure risks.

3. Verify Ownership: The private registration (ASN 62240) suggests a business or cloud provider. Confirm with Clouvider if further validation is needed.

4. No Security Actions Required: No firewall rules or WAF policies are recommended for this IP.

---

Conclusion: 173.239.214.96 is a low-risk, legitimate IP with no malicious indicators. Focus on monitoring its subnet for broader network health.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionNJ
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
19%
22
routing
25%
11
services
13%
11
ownership
19%
22
reputation
13%
12
geolocation
13%
11
Overall17%89
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-14 13:23:54 UTC
Last Seen2026-06-07 05:47:35 UTC
Profile Built2026-06-07 05:55:55 UTC
Data FreshnessLive
Signal Types17
Total Observations17
πŸ” 17 signal types Β· 17 observations collected
This report is generated from 17+ 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.