87.54.18.18
IP Intelligence Briefing: 87.54.18.18/32
*Generated via IPDebrief tools: profile, history, relationships, and neighborhood analysis*
---
**1. IP Profile**
- Risk Score: 70 (High Risk)
- Ownership: Owned by TDK-MNT (ASN 3292), registered to COMPUTER-PROBLEMER-NET in the US.
- Geolocation: Listed as New York, US (latitude/longitude unspecified).
- Threat Indicators: No direct malicious activity detected (no indicators, blacklists, or campaigns).
- Network Role: Firewalled / No Services; no cloud, CDN, or residential flags.
- DNS: No PTR records or domain associations.
- Routing: BGP prefix 87.48.0.0/13, route stability flagged as unstable.
- DNSSEC: Valid, but minimal operator score (0.13).
---
**2. Observation History**
- Latest Signals (June 8, 2026):
- Geolocation: Inferred as Denmark (DK) with 52% confidence (latitude 56.26, longitude 9.5).
- Network Abuse: Subnet 87.54.18.18/24 has 25% abuse density (1 threat sibling in 4 total).
- ASN: TDC - TDC Holding A/S (ASN 3292).
- DNSSEC: Minimal risk score (0.15).
- Overall Confidence: Low (15%) due to sparse data across dimensions.
---
**3. Relationships**
- Linked Entities:
- Same network: COMPUTER-PROBLEMER-NET (repeated in relationships).
- No direct connections to organizations, domains, or certificates.
---
**4. Neighborhood Analysis**
- Subnet: 87.54.18.18/24 (3 total sibling IPs).
- Risk Distribution:
- 3 medium-risk neighbors (scores: 40–55).
- No high-risk IPs.
- Abuse Density: 0% (subnet classified as "mostly clean").
---
**5. Actionable Insights**
- Geolocation Discrepancy: IP reported as US-NY but inferred as Denmark. Verify location accuracy or potential spoofing.
- Neighbor Risk: While subnet is "mostly clean," 1 of 4 siblings is flagged as a threat. Monitor traffic patterns and consider blocking the subnet.
- Routing Stability: Unstable BGP route (routeChanges30d = 0, isRouteStable = false). Investigate potential network instability.
- DNSSEC Validity: DNSSEC is valid, but minimal operator score suggests potential configuration weaknesses.
---
Recommendations:
- Monitor traffic to/from this subnet for anomalies.
- Investigate the geolocation discrepancy and potential spoofing.
- Block or restrict access to the subnet due to mixed neighbor risk.
- Validate DNSSEC configuration and ensure routing stability.
*End of Briefing*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | TDK-MNT |
| ASN | AS3292 |
| Network Name | COMPUTER-PROBLEMER-NET |
| CIDR Block | 87.54.18.0/24 |
| RIR | RIPE |
| Country | DK |
| Abuse Contact | Available via RDAP |
🌐 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 | 13% | 1 | 1 |
| routing | 13% | 1 | 1 |
| services | 13% | 1 | 1 |
| ownership | 35% | 2 | 3 |
| reputation | 0% | 0 | 0 |
| geolocation | 13% | 1 | 1 |
| Overall | 15% | 6 | 7 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Aging
| First Seen | 2026-05-19 15:39:38 UTC |
| Last Seen | 2026-06-19 11:34:22 UTC |
| Profile Built | 2026-06-17 13:01:44 UTC |
| Data Freshness | Aging |
| Signal Types | 17 |
| Total Observations | 17 |
Full dossier details are available via our API.