142.44.233.187
IP Intelligence Briefing: 142.44.233.187
*Generated via IPDebrief tools: Profile, History, Relationships, Neighbors*
---
**1. IP Profile**
- Risk Score: 25 (Low Risk)
- Ownership: Registered to Ahrefs Pte Ltd (OVH ASN 16276).
- Geolocation:
- Country: Canada (CA)
- City: Singapore (discrepancy noted; geolocation may be inaccurate).
- Network Role: CloudCompute infrastructure (OVH-hosted, no public services detected).
- Threat Indicators: No malicious activity detected (no indicators, blacklists, or campaigns).
---
**2. Observation History**
- Latest Activity: June 8, 2026.
- Key Observations:
- DNS association with `proxy-ca003-san187.ahrefs.net` (ahrefs.net domain).
- Subnet abuse density: 0.4683 (moderate risk).
- No open ports or TLS certificates detected during scans.
- Geolocation consistency: Plausible (3000 km accuracy radius).
---
**3. Relationships**
- Network Affiliation:
- Same subnet (`142.44.233.0/24`), shared with OVH-CUST-281059682.
- DNS Links:
- PTR record resolves to `proxy-ca003-san187.ahrefs.net` (likely a private proxy or load balancer).
- No Threat Associations: No linked malicious domains, campaigns, or certificates.
---
**4. Neighborhood Analysis**
- Subnet: `142.44.233.0/24` (252 total IPs).
- Risk Distribution:
- High Risk: 0 IPs
- Medium Risk: 78 IPs
- Low Risk: 22 IPs
- Abuse Density: 46.83% (moderate risk; 118 threat-suspected siblings).
- Notable Neighbors:
- IPs with risk scores > 40 (e.g., 142.44.233.0, 142.44.233.3).
---
**5. Recommendations**
- Monitor Subnet: The subnet contains a mix of low/medium-risk IPs; investigate high-risk neighbors for potential compromises.
- Verify DNS Configuration: Confirm legitimacy of `proxy-ca003-san187.ahrefs.net` and ensure DNSSEC is enabled.
- Check Access Controls: Ensure cloud instance (OVH) is secured with strict IAM policies and firewall rules.
- Geolocation Discrepancy: Investigate why the IP reports a city in Singapore despite being registered to a Canadian entity.
---
Conclusion: The IP is part of a legitimate cloud infrastructure (Ahrefs) with no direct malicious activity. However, its subnet contains a moderate risk of abuse, warranting further 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-281059682 |
| CIDR Block | 142.44.233.0/24 |
| RIR | ARIN |
| Country | Singapore |
| Abuse Contact | — |
🌐 DNS Intelligence
| PTR | proxy-ca003-san187.ahrefs.net |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | proxy-ca003-san187.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 | 26% | 2 | 4 |
| routing | 13% | 1 | 1 |
| services | 15% | 2 | 2 |
| ownership | 15% | 2 | 2 |
| reputation | 28% | 1 | 3 |
| geolocation | 25% | 2 | 2 |
| Overall | 21% | 10 | 14 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-19 03:34:57 UTC |
| Last Seen | 2026-06-28 08:12:30 UTC |
| Profile Built | 2026-06-29 02:18:06 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 23 |
Full dossier details are available via our API.