IP Intelligence Briefing: 51.161.37.251
Date: 2026-06-14
---
**1. Core Profile**
- Risk Score: 25 (Low Risk)
- Ownership: Owned by Dmytro, Ahrefs Pte Ltd (OVH ASN 16276).
- Geolocation: Montreal, Quebec, Canada (ARIN-regulated).
- Network Role: Hosting provider (firewalled / no services exposed).
- Threat Indicators: No malicious activity detected (no blacklists, Tor, or spam sources).
---
**2. Observation History**
- Recent Activity:
- DNS resolution for `ahrefs.net` (CAA records validated).
- Geolocation inferred via Cymru country database (CA, Montreal).
- Operator score: Minimal (0.2174).
- Stability: No recent route changes; BGP prefix stable.
---
**3. Relationships**
- Network: Part of OVH-CUST-281059684 subnet (51.161.37.0/24).
- DNS: Resolves to `proxy-ca005-san251.ahrefs.net` (PTR record).
- Certificates: No TLS certificates detected.
- Hosting: Linked to Ahrefs, a legitimate SEO tool provider.
---
**4. Neighborhood Analysis**
- Subnet: 51.161.37.0/24.
- Abuse Density: 28.99% (moderate risk).
- Neighbors:
- 61 active IPs (69 flagged as risky).
- 100 total IPs in subnet (21 low-risk, 79 medium-risk).
- Recommendation: Monitor subnet for lateral movement or compromised hosts.
---
**5. Threat Context**
- No Direct Threats: IP shows no malicious indicators (no malware, phishing, or C2 activity).
- Subnet Risks: High abuse density suggests potential for peer-to-peer threats.
- Behavioral Flags: No honeypot hits or enumeration attempts.
---
**6. Actionable Insights**
- SOC Analyst Actions:
- Validate DNS configurations for `ahrefs.net` to ensure no spoofing.
- Monitor subnet for unusual traffic patterns (e.g., outbound connections to risky neighbors).
- Consider isolating this IP if it serves sensitive services, given the subnetβs moderate risk.
- Firewall Rules:
- Allow traffic only on required ports (no open ports detected).
- Block traffic to/from high-risk subnet neighbors if not authorized.
---
Conclusion: 51.161.37.251 is a legitimate hosting IP under Ahrefs, with no direct malicious activity. However, its subnet contains a significant portion of risky IPs, warranting closer monitoring.
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-281059684 |
| CIDR Block | 51.161.37.0/24 |
| RIR | ARIN |
| Country | Singapore |
| Abuse Contact | β |
π DNS Intelligence
| PTR | proxy-ca005-san251.ahrefs.net |
| Forward Confirmed | No β PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | proxy-ca005-san251.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 | |||
| 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 | 31% | 2 | 4 |
| routing | 13% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 19% | 2 | 2 |
| reputation | 31% | 1 | 3 |
| geolocation | 30% | 2 | 3 |
| Overall | 22% | 10 | 15 |
| 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:25 UTC |
| Last Seen | 2026-06-27 06:15:32 UTC |
| Profile Built | 2026-06-28 00:19:30 UTC |
| Data Freshness | Live |
| Signal Types | 22 |
| Total Observations | 28 |
Full dossier details are available via our API.