IPDebrief

176.65.139.216

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

IP Intelligence Briefing: 176.65.139.216

Date: 2026-06-11

---

**1. Core Profile**

- Primary: New York, US (IPDebrief geolocation).

- Conflicting signal: Luxembourg (LU) detected in observations (potential false positive or misattribution).

---

**2. Observation History**

- On 2026-06-11, a geolocation signal falsely labeled Luxembourg (LU) was recorded.

- Traceroute to the IP showed 21 hops, with Comcast as a transit provider.

- DNSSEC validation is active, but no DNS-related threats observed.

---

**3. Network Relationships**

- Same network: PFCLOUD-NET (ASN 214472).

- No direct ties to known malicious organizations or subnets.

- BGP prefix: 176.65.139.0/24.

- RPKI state: Not specified; IRR consistency unknown.

---

**4. Neighborhood Analysis**

- High Risk: 1 IP (e.g., 176.65.139.7, 176.65.139.25).

- Medium Risk: 16 IPs.

- Low Risk: 42 IPs.

---

**5. Actionable Insights**

- Monitor Geolocation Anomalies: Investigate the Luxembourg signal for potential spoofing or misattribution.

- Scan Neighbors: Focus on high-risk neighbors (e.g., 176.65.139.7) for potential lateral movement or botnet activity.

- Verify Ownership: Confirm MNT-ZEXOTEK’s legitimacy and check for any recent ownership changes.

- Firewall Rules: Consider blocking high-risk neighbors or implementing rate limiting for the subnet.

---

Conclusion: This IP is currently low risk with no direct malicious indicators. However, the conflicting geolocation data and presence of high-risk neighbors warrant further monitoring.

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

🌍 Geolocation

CountryπŸ‡³πŸ‡± Netherlands
RegionUS-NY
CityNew York
TimezoneEurope/Amsterdam
Latitude51.68
Longitude7.70

🏒 Ownership & Registration

OrganizationMNT-ZEXOTEK
ASNAS214472
Network NamePFCLOUD-NET
CIDR Block176.65.139.0/24
RIRRIPE
CountryNL
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 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
13%
11
routing
13%
11
services
13%
11
ownership
27%
23
reputation
0%
00
geolocation
13%
11
Overall13%67
Coverage: 5/6 dimensions Β· Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-26 00:49:55 UTC
Last Seen2026-06-26 18:10:48 UTC
Profile Built2026-06-11 01:53:57 UTC
Data FreshnessLive
Signal Types16
Total Observations17
πŸ” 16 signal types Β· 17 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.