54.39.210.168
IP Intelligence Briefing: 54.39.210.168
Date: 2026-06-14
---
**1. Core Profile**
- Risk Score: 40 (Moderate Risk)
- Ownership:
- ISP: OVH (ASN 16276)
- Organization: Dmytro, Ahrefs Pte Ltd
- Network: OVH-CUST-281059686
- Geolocation:
- Country: Canada (QC, Beauharnois)
- Plausibility: Low (RTT anomaly detected: 24ms vs. expected 112.6ms for 5,629km)
- Threat Indicators:
- No malicious activity detected (no indicators, blacklists, or campaigns).
- Network Role:
- Cloud Compute (OVH infrastructure, no residential/mobile/mobile).
---
**2. Observation History**
- Recent Activity (Last 30 Days):
- 18 observations, with 14 showing consistent "CloudCompute" classification.
- Geo Validation Violation: RTT of 24ms contradicts distance (5,629km), suggesting spoofing or misconfigured routing.
- Stability: Subnet (54.39.210.0/24) shows high abuse density (0.56), with 143/253 IPs flagged as threats.
---
**3. Relationships**
- Network Affiliation:
- Linked to OVH-CUST-281059686 (same network as 143 abusive IPs).
- DNS:
- Reverse DNS: `proxy-ca007-san168.ahrefs.net` (likely internal Ahrefs infrastructure).
- Certificates/TLS:
- No TLS certificates or open ports detected.
---
**4. Neighborhood Analysis**
- Subnet: 54.39.210.0/24
- Abuse Density: 56.52% (high-risk subnet).
- Neighbor Risk:
- 140 active IPs in subnet; 143 flagged as threats.
- Inherited Risk: 22 (likely due to subnet-level abuse).
---
**5. Threat Assessment**
- Direct Risk: Low (no malicious indicators).
- Indirect Risk: High (resides in a subnet with widespread abuse).
- Geolocation Anomalies: Potential spoofing or misconfigured routing.
---
**6. Recommended Actions**
1. Monitor Subnet: Track activity in 54.39.210.0/24 due to high abuse density.
2. Verify Geolocation: Investigate RTT anomaly to confirm spoofing or misconfigured routing.
3. Check DNS: Validate reverse DNS (`proxy-ca007-san168.ahrefs.net`) for internal infrastructure legitimacy.
4. Segment Traffic: Consider isolating the subnet if it hosts sensitive services.
Note: This IP appears legitimate as part of Ahrefs' cloud infrastructure but is in a high-risk subnet. Prioritize monitoring for lateral movement or abuse patterns.
---
Source: IPDebrief Threat Intelligence Platform
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Dmytro, Ahrefs Pte Ltd |
| ASN | AS16276 |
| Network Name | OVH-CUST-281059686 |
| CIDR Block | 54.39.210.0/24 |
| RIR | ARIN |
| Country | Singapore |
| Abuse Contact | — |
🌐 DNS Intelligence
| PTR | proxy-ca007-san168.ahrefs.net |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | proxy-ca007-san168.ahrefs.net |
🔐 DNS Hygiene
| Hygiene Score | 40% (Fair) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Present |
☁️ 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 | 35% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 8% | 1 | 1 |
| ownership | 19% | 2 | 2 |
| reputation | 31% | 1 | 3 |
| geolocation | 35% | 2 | 3 |
| Overall | 24% | 9 | 13 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-07 23:04:29 UTC |
| Last Seen | 2026-06-27 08:31:43 UTC |
| Profile Built | 2026-06-28 02:38:31 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 25 |
Full dossier details are available via our API.