# IP Intelligence Briefing: 167.172.64.83/32
## Executive Summary
IP 167.172.64.83 is a low-risk DigitalOcean cloud compute resource located in Singapore. The IP presents minimal threat indicators and operates within a generally clean subnet with moderate abuse density. No immediate defensive action required.
## Risk Assessment
- Overall Risk Score: 25/100 (Low Risk)
- Provider: DigitalOcean (ASN: 14061)
- Network: 167.172.0.0/16
- Geolocation: Singapore (SG)
- Infrastructure Type: Cloud Compute (isCloud: true)
- Classification: Firewalled / No Services
## Technical Profile
- Open Ports: None detected
- DNS Resolution: PTR records absent, forward resolution failed
- DNSSEC: Valid
- Route Stability: Unstable (isRouteStable: false)
- Traceroute: 13 hops with 4 timeouts; transit networks include Comcast and Lumen
- DNSBL Status: Listed on 1 of 8 total blacklists (low severity)
## Threat Indicators
- Known Attacker: No
- Tor Exit Node: No
- Spam Source: No
- Blacklist Count: 0 active threat feeds
- Known Campaigns: None identified
- Control Plane Origin: 167.172.64.0/20 (BGP prefix)
## Neighborhood Analysis (167.172.64.0/24)
- Abuse Density: 0.5 (moderate)
- Subnet Classification: Mostly clean
- Total Siblings: 2
- Active Siblings: 1
- Threat Siblings: 1
- Notable Neighbor: 167.172.64.25 (risk score: 15, authority score: 50)
## Historical Observations
- Total Observations: 14 signals recorded
- Recent Activity: June 22, 2026
- Consensus: Subnet abuse density 0.5; classification "mostly_clean"
- Ownership Stability: No changes detected
- Threat Persistence: 0 days observed
## Relationships
- Three relationships identified, all categorizing the IP within the DigitalOcean network infrastructure
- No associations with external organizations or hostnames
## Recommended Actions
No specific firewall rules or blocking recommendations generated at this time. The IP presents low-risk characteristics consistent with legitimate cloud infrastructure usage.
Suggested Monitoring Approach:
- Continue passive observation
- No immediate blocking required
- Monitor for emerging threat indicators
- Review neighborhood sibling 167.172.64.25 if suspicious activity detected from that address
---
*Report generated via IPDebrief Intelligence Platform. Data sourced from real-time network observations and threat intelligence feeds.*
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 | |||
| 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 | 0% | 0 | 0 |
| routing | 0% | 0 | 0 |
| services | 0% | 0 | 0 |
| ownership | 25% | 1 | 2 |
| reputation | 0% | 0 | 0 |
| geolocation | 0% | 0 | 0 |
| Overall | 4% | 1 | 2 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-06-18 23:27:07 UTC |
| Last Seen | 2026-06-22 02:51:46 UTC |
| Profile Built | 2026-06-22 03:00:06 UTC |
| Data Freshness | Live |
| Signal Types | 16 |
| Total Observations | 16 |
Full dossier details are available via our API.