## IP Intelligence Briefing: 31.57.216.39/32
Classification: Moderate Risk / High-Abuse Subnet
Overview: IP 31.57.216.39 presents a moderate risk profile (score: 40) associated with a high-abuse density subnet (31.57.216.0/24, abuse density: 0.8333). The IP is associated with ASN 197769 (Abuse) and geolocated to the United Arab Emirates (Dubai region). The IP operates as a web server with SSH access enabled.
Threat Indicators: No confirmed threat indicators identified. The IP is not flagged as a known attacker, spam source, or Tor exit node. The IP is listed on 1 of 8 DNSBLs. No correlation to known campaigns detected.
Network Infrastructure:
- ASN: 197769 (Abuse)
- BGP Path: 37100 โ 34779 โ 51396 โ 197769
- Route Stability: Stable
- DNSSEC: Valid
- Delegation Age: 20 days
Services & Ports:
- Port 80 (HTTP): Open
- Port 443 (HTTPS): Open
- Port 22 (SSH): Open (SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.15)
Subnet Analysis (31.57.216.0/24):
The /24 subnet exhibits elevated abuse characteristics:
- Total Siblings: 12
- Active Siblings: 4
- Threat Siblings: 10
- Abuse Density: 0.8333 (High)
- Inherited Risk Score: 25
- Neighbor Risk Distribution: 10 medium-risk IPs (score 40), 1 low-risk IP (score 25)
Most neighboring IPs in the subnet show risk scores of 40, indicating systemic abuse within the /24 block.
Relationship Graph:
All 15 detected relationships link to "VPSDedicatedLLC," suggesting the IP is part of a dedicated VPS hosting environment.
Observation History:
24 total observations recorded. Recent signal activity includes:
- June 18, 2026: Classification of "high_abuse" with abuse density 0.8333 recorded
- Multiple routing and service observations from June 2026
Recommended Actions:
No specific firewall rules or blocking recommendations generated based on current risk profile. Due to the high-abuse subnet classification (0.8333 density), consider:
1. Monitor closely for outbound malicious activity
2. Implement rate limiting on inbound connections
3. Review SSH access if not required for legitimate operations
4. Block at perimeter if this IP or subnet correlates with observed threats in your environment
Intelligence Confidence: Moderate โ IP lacks direct threat indicators but exists within a high-abuse subnet environment requiring ongoing observation.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
๐ข Ownership & Registration
| Organization | Abuse |
| ASN | AS197769 |
| Network Name | โ |
| CIDR Block | 31.57.216.0/24 |
| RIR | RIPE |
| Country | โ |
| 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 | Tier 3 โ Basic operator with some routing infrastructure |
๐ 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 | 37% | 2 | 5 |
| routing | 27% | 2 | 3 |
| services | 26% | 2 | 3 |
| ownership | 30% | 3 | 4 |
| reputation | 26% | 1 | 3 |
| geolocation | 21% | 2 | 2 |
| Overall | 28% | 12 | 20 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
๐ Observation Timeline ๐ Live
| First Seen | 2026-05-07 23:04:15 UTC |
| Last Seen | 2026-06-23 10:04:46 UTC |
| Profile Built | 2026-06-23 10:16:07 UTC |
| Data Freshness | Live |
| Signal Types | 24 |
| Total Observations | 26 |
Full dossier details are available via our API.