167.172.171.218
IPDebrief Threat Intelligence Briefing
Target IP: 167.172.171.218/32
---
**1. Core Profile**
- Risk Score: Moderate (50/100)
- Provider: DigitalOcean (AS14061)
- Geolocation:
- Country: US (discrepancy noted: city listed as Frankfurt, Germany, but country code is US)
- Region: HE (Hessen, Germany)
- City: Frankfurt am Main
- Network Role: CloudCompute (DigitalOcean VM)
- Threat Indicators: No active threats, spam, or known attacker activity.
- DNS: No PTR records, no email auth (SPF/DKIM), and no hosted domains.
---
**2. Observation History (Last 30 Days)**
- Network Classification: Stable (no route changes).
- Geolocation Consensus: Confirmed via 2 sources (AlienVault OTX).
- DNSBL Listings:
- Listed on 2/8 DNSBLs (e.g., Spamhaus, OpenBL).
- No high-severity threats detected.
- Behavioral Signals:
- No honeypot hits, enumeration attempts, or WAF violations.
- Traceroute shows 30 hops, with 17 timeouts (likely cloud infrastructure).
---
**3. Relationships & Network Context**
- Subnet: 167.172.171.218/24
- Subnet Abuse Density: 0% (clean).
- Neighbors: No active sibling IPs in the subnet.
- Provider Linkage: Strong association with DigitalOcean (AS14061).
- Threat Correlation: No linked campaigns or certificates.
---
**4. Actionable Insights**
- Risk Mitigation:
- Monitor for unexpected outbound traffic (e.g., C2, data exfiltration).
- Verify geolocation accuracy (US vs. Frankfurt discrepancy).
- Network Segmentation:
- Isolate cloud instances from internal networks to limit lateral movement.
- DNSBL Monitoring:
- Investigate why the IP is listed on 2 DNSBLs; confirm legitimacy.
- Cloud Provider Checks:
- Confirm DigitalOcean VM compliance with security policies.
---
Conclusion:
This IP is a DigitalOcean cloud instance with no direct malicious activity. However, its DNSBL listings and geolocation discrepancy warrant further investigation. SOC teams should monitor for anomalous behavior and ensure alignment with cloud provider security practices.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | digitalocean |
| ASN | AS14061 |
| Network Name | DigitalOcean |
| CIDR Block | 167.172.0.0/16 |
| RIR | ARIN |
| Country | US |
| 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 | Infrastructure / Datacenter |
| Service Purpose | Firewalled / No Services |
| Network Tier | Hosting — Infrastructure provider without advanced routing |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| 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 | 27% | 2 | 4 |
| routing | 13% | 1 | 1 |
| services | 19% | 2 | 2 |
| ownership | 27% | 2 | 3 |
| reputation | 22% | 1 | 3 |
| geolocation | 27% | 2 | 2 |
| Overall | 22% | 10 | 15 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-30 10:58:19 UTC |
| Last Seen | 2026-06-29 07:33:08 UTC |
| Profile Built | 2026-06-29 07:35:48 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 20 |
Full dossier details are available via our API.